If so, why and how much more than 256 have you set or recommend to set
without causing too much of a performance degradation ? I am thinking 384
for our environment due to the fact that we have a lot of transactions/sec
and at times we run out of worker threads as we cannot connect to SQLHi Hassan
I suggest that you increment this value in stages until you stop getting the
error! You can then monitor the effect that the give value has on your system.
John
"Hassan" wrote:
> If so, why and how much more than 256 have you set or recommend to set
> without causing too much of a performance degradation ? I am thinking 384
> for our environment due to the fact that we have a lot of transactions/sec
> and at times we run out of worker threads as we cannot connect to SQL
>
>|||Check out Ken Henderson's blog on max worker threads:
http://blogs.msdn.com/khen1234/archive/2005/11/07/489778.aspx
Be especially careful because if the underlying issue is that your server is
undersized for the workload, you will make matters much worse by trying to
do more. You might be better off doing some query tuning upgrading
hardware.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <Hassan@.hotmail.com> wrote in message
news:u3qbSYkkGHA.1000@.TK2MSFTNGP04.phx.gbl...
> If so, why and how much more than 256 have you set or recommend to set
> without causing too much of a performance degradation ? I am thinking 384
> for our environment due to the fact that we have a lot of transactions/sec
> and at times we run out of worker threads as we cannot connect to SQL
>
Showing posts with label recommend. Show all posts
Showing posts with label recommend. Show all posts
Wednesday, March 7, 2012
Tuesday, February 14, 2012
Do you recommend storing images directly into the DB?
The images each are in Jpeg format (black and white, with some grey scale). File size wise, wouldnt be huge < 50 KB.
There wont be too many people using the system.
Would it be tedious to maintain? Many people recommend storing the path to the graphic instead.
Please advise. Thanks.98% of all articles or opinions I've seen reccomend storing them outside the DB. SQL is not a good storage mechanism for files.
HTH|||Originally posted by fused
The images each are in Jpeg format (black and white, with some grey scale). File size wise, wouldnt be huge < 50 KB.
There wont be too many people using the system.
Would it be tedious to maintain? Many people recommend storing the path to the graphic instead.
Please advise. Thanks.
We have a proffesianally built imaging system that stores all the images on the disk and just references them from the database.
I agree that they should be left outside the DB.|||Originally posted by jimpen
We have a proffesianally built imaging system that stores all the images on the disk and just references them from the database.
I agree that they should be left outside the DB.
Right now, we are planning a project to store some images. What's the scripting language that you use? Any advice? Thanks.
So you guys have a file server that has permission given to everyone? And when you upload the pic, the picture is moved to the shared file server? And a path is inserted into the sql server?
Please advise.|||I have an ASP app that does this sort of thing. I read through the directories, and display the file names as hyperlinks without even using a db connection. This method works really well if you can get the user to name the files in such a way that the links on the page look ok...which is normally not an easy task, but it's worked pretty well for me...But this is an IntrAnet app. , not a web app..|||We use ASP.Net with C# on Windows IIS. You know the IP of the computer, create a sub directory (eg /Images) and use a component that looks in this directory (we use Borland C# Builder but Visual Studio will have this probably as well). To let users upload their images, you can use ASPUpload (www.aspupload.com)|||Originally posted by fused
Right now, we are planning a project to store some images. What's the scripting language that you use? Any advice? Thanks.
So you guys have a file server that has permission given to everyone? And when you upload the pic, the picture is moved to the shared file server? And a path is inserted into the sql server?
Please advise.
Ours is provided by a VAR of http://www.imagesoft.com/.
Read permissions are given by group as well as write. We have different sections that are available to different groups depending on what they need/are allowed to see.
There wont be too many people using the system.
Would it be tedious to maintain? Many people recommend storing the path to the graphic instead.
Please advise. Thanks.98% of all articles or opinions I've seen reccomend storing them outside the DB. SQL is not a good storage mechanism for files.
HTH|||Originally posted by fused
The images each are in Jpeg format (black and white, with some grey scale). File size wise, wouldnt be huge < 50 KB.
There wont be too many people using the system.
Would it be tedious to maintain? Many people recommend storing the path to the graphic instead.
Please advise. Thanks.
We have a proffesianally built imaging system that stores all the images on the disk and just references them from the database.
I agree that they should be left outside the DB.|||Originally posted by jimpen
We have a proffesianally built imaging system that stores all the images on the disk and just references them from the database.
I agree that they should be left outside the DB.
Right now, we are planning a project to store some images. What's the scripting language that you use? Any advice? Thanks.
So you guys have a file server that has permission given to everyone? And when you upload the pic, the picture is moved to the shared file server? And a path is inserted into the sql server?
Please advise.|||I have an ASP app that does this sort of thing. I read through the directories, and display the file names as hyperlinks without even using a db connection. This method works really well if you can get the user to name the files in such a way that the links on the page look ok...which is normally not an easy task, but it's worked pretty well for me...But this is an IntrAnet app. , not a web app..|||We use ASP.Net with C# on Windows IIS. You know the IP of the computer, create a sub directory (eg /Images) and use a component that looks in this directory (we use Borland C# Builder but Visual Studio will have this probably as well). To let users upload their images, you can use ASPUpload (www.aspupload.com)|||Originally posted by fused
Right now, we are planning a project to store some images. What's the scripting language that you use? Any advice? Thanks.
So you guys have a file server that has permission given to everyone? And when you upload the pic, the picture is moved to the shared file server? And a path is inserted into the sql server?
Please advise.
Ours is provided by a VAR of http://www.imagesoft.com/.
Read permissions are given by group as well as write. We have different sections that are available to different groups depending on what they need/are allowed to see.
Subscribe to:
Posts (Atom)