Viewing 10 posts - 1 through 10 (of 10 total)
Thats great.
I would just like to note one thing about this solution. You can potentially lose the data that you want to save if your batch fails following the table...
March 26, 2008 at 4:39 pm
This suggestion assumes that the volume of data which you wish to retain is reasonably small.
1. Set simple recovery mode on the host database.
2. Run sp_rename to rename the original...
March 26, 2008 at 12:34 pm
You could get answers by simply submitting the statement as a workload to the SQL Server Engine Tuning Advisor. The advisor isn't all that good at advising on more complex...
March 26, 2008 at 12:00 pm
Yes, there have been improvements to the management of tempdb in ss 2k5 (most cache). However, on high volume system cache does not resolve the conflict of allocations on the...
March 25, 2008 at 10:04 am
If you manage to get some free time on your prod platform you may want to try the following...
1. set your ss affinity to use just 4 CPUs.
2. shutdown the...
March 25, 2008 at 8:58 am
No problem.
Note: Waits...
Now that you are using more processors you should also adjust your tempdb file layout for maximum performance. Tempdb pages are allocated and indexed using the first 4gb...
March 24, 2008 at 1:32 pm
You should have at least one processor core freed up for the OS by deselecting it from your CPU and I/O affinity.
Asside from your config you may want to address...
March 24, 2008 at 12:37 pm
"lock pages in memory" privileges are set within the "Local Security Policy" mmc snapin. Within the snapin you will find this setting in the "User Rights Assignment" node of the...
March 24, 2008 at 11:39 am
Depending upon your actual ss memory usage you could be negatively impacting the OS's ability to service resource (CPU, MEMORY, I/O) requests. I would reduce the max memory in ss...
March 24, 2008 at 10:41 am
Viewing 10 posts - 1 through 10 (of 10 total)