I think this is a pretty simple and perhaps stupid question. I've established log shipping between two SQL Server 2008 servers using the GUI (i.e. the SQL Server Management Studio). It's been running fine -- but now I want to change the number of days the copied files are retained on the secondary server. Is it simply a matter of going back to the GUI and change it there. Is it smart enough just to make that simple change or is the GUI only used to create the initial log shipping configuration?
Is it possible to set up a distribution list in the GAL such that no one can see the members of the group?
How can I increase the limit of worker threads from the default 10 for SQL Server 2005 SqlAgent? I have 9 jobs that run almost continuously and that leaves only one available thread for the rest of the scheduled jobs. Oftentimes, when no thread is available, I will see the jobs in "Waiting for worker thread" state. I'd like to increase the number to about 12 (which should do the trick for me). Any idea where this is set?
I have a third party application running on Windows Server 2003 SP2 that is getting an "Insufficient Server Resources" error. It just started exhibiting this behavior for no apparent reason. I ran ProcMon to see where it is happening. In each case, it happens to be reading a file on another file server. ProcMon shows the name of the file and the error "Insufficient Server Resources" at the same time as the application pops up it's own error message box that says essentially the same thing.
The ProcMon stack trace seems to indicate that the error emanates from fltmgr.sys (the Microsoft File System Filter Manager). The stack trace also contains calls into rdbss.sys and ntkrnlpa.exe. Neither the system event log nor the application event log show any errors.
I did find this hotfix -- but it seems to address a blue-screen crash which we're not seeing. Any ideas?
Additional Info: The other server (the file server) is also Windows 2003 SP2. The third party application is Concordance -- which I'm automating via COM. One critical point that I left out is that the application runs fine accessing this and other files on this server for a period and then generates this error. If I dismiss the dialog box, the driving application can continue to invoke Concordance (which in turn reads these files) for a while and the pattern repeats. It runs for a while and bombs out with the insufficient server resource error. But once I dismiss the dialog, it is as if the server no longer has a problem until, of course, it recurs. I've monitored memory and handles with Process Explorer during the period before the error pops up and nothing obvious is being depleted.
I know there is a small utility program to do this, but my memory fails me. I often want to find the location of an executable that is somewhere on my windows path -- I just don't know where. I know it is on my path because I can run it regardless of my current directory. Can someone refresh my recollection? :-)