Viewing 15 posts - 76 through 90 (of 1,790 total)
chris-320654 (6/18/2012)
CPU-Z (and task manager) confirms that hyperthreading is enabled with 24 threads available to the OS.
I'd be curious how things perform with hyperthreading disabled.
If IO is 2x to...
June 18, 2012 at 7:34 am
I would certainly encourage a look at CPU-Z and compare the settings on the old server with the new, hyperthreading being one of them. Additionally, you mentioned faster disk but...
June 15, 2012 at 7:22 am
SQLKnowItAll (6/6/2012)
David Benoit (6/6/2012)
Being that you have 128 GB of memory I am assuming that this is 64-Bit but just to be sure, is it?
I believe it must be, that...
June 6, 2012 at 3:05 pm
Being that you have 128 GB of memory I am assuming that this is 64-Bit but just to be sure, is it?
June 6, 2012 at 2:59 pm
Have you run the DBCC against the production database then? Just trying to make sure that I understand the last post correctly.
June 4, 2012 at 8:10 am
Do you have a SnapManager backup? If so, you could restore that in another location and see if that is without the error by running DBCC against it. I'm guessing...
June 1, 2012 at 7:19 am
Lynn Pettis (5/22/2012)
Unfortunately, common sense isn't common. 😉
...and that would be our job to make sure that the "common sense" principles are upheld. 😛 Not always easy though.
May 22, 2012 at 9:02 am
SQL Kiwi (5/22/2012)
Jeff Moden (5/22/2012)
May 22, 2012 at 8:07 am
A bit intrigued here as well. You are not replicating delete statements. Any chance that you are reusing the primary keys on the publisher and hence getting duplicates at the...
May 3, 2012 at 11:58 am
Your boss should really re-read the statement from MS. They definitely recommend letting memory be dynamically managed but I'm sure if you were to contact product support they would tell...
April 27, 2012 at 2:26 pm
I would recommend enabling logging on the snapshot agent to see what that reveals. I'm pretty sure that will provide some clarity.
http://support.microsoft.com/kb/312292
Let me know what you find.
April 27, 2012 at 12:56 pm
Remove these from the script and start again. These are all connection events and really aren't necessary for this.
exec sp_trace_setevent @TraceID, 14, 1, @on
exec sp_trace_setevent @TraceID, 14, 9, @on
exec...
April 27, 2012 at 12:31 pm
dwilliscp (4/27/2012)
So my boss is correct.. the recommended state (by MS) is to let SQL Server get what ever memory it can from...
April 27, 2012 at 7:50 am
dwilliscp (4/27/2012)
April 27, 2012 at 7:39 am
opc.three's recommendations definitely need to be applied first and see how things go from there. Once that is done I'm guessing that you will not lock up as "hard" as...
April 27, 2012 at 7:15 am
Viewing 15 posts - 76 through 90 (of 1,790 total)