Viewing 15 posts - 41,731 through 41,745 (of 49,562 total)
To offer any real help, I need to see the deadlock graph.
Without that, I can give you generic advice - make sure all your queries are written a optimally as...
January 15, 2009 at 3:16 am
SQL does a good job of caching frequently used data in memory, if there's sufficient memory available. If the tables in that database are used often, they will be in...
January 15, 2009 at 12:51 am
Why do you need to shrink the log?
Please read through this - Managing Transaction Logs[/url]
Minaz Amin (2/27/2007)
2. Shrink it.
3 Create a maintenanace plan to do the...
January 15, 2009 at 12:03 am
Switch traceflag 1222 on. That will result in a deadlock graph been written to the error log every time a deadlock occurs. Post the result of that graph here.
DBCC TRACEON(1222,-1)
January 15, 2009 at 12:02 am
Ouch.
Firstly, there's a hardware error. You may want to check and even replace the drives. Personally I wouldn't be ahppy about putting a database back on shaky hardware.
There's a single...
January 14, 2009 at 11:57 pm
The error events. Exception, errorlog, user error message, attention. There may be some others worth checking.
How long are you planning running profiler for?
January 14, 2009 at 11:55 pm
The message saying the connection was forcefully closed usually means that either the connection was explicitly killed by someone, or the query hit a high severity error and was disconnected.
Both...
January 14, 2009 at 1:51 pm
SQL will cache frequently used data. If the database is often used, the data will be in memory.
Pintable is still usable on SQL 2005, but it does nothing.
January 14, 2009 at 1:42 pm
Before you go truncating your transaction log on a regular basis, please note that truncating the log is not a good maintenance practice.
January 14, 2009 at 1:40 pm
Grant Fritchey (1/14/2009)
Some consultant somewhere is going to make a mint.
Pity it won't be me.
It took me all of 20 sec or so to find that on google,...
January 14, 2009 at 1:37 pm
Bob Hovious (1/14/2009)
January 14, 2009 at 1:15 pm
I believe it is required in the latest SQL standard. (correct me if I'm wrong, I haven't actually read the standards docs)
One of the reasons that it will be required...
January 14, 2009 at 1:13 pm
Joseph (1/14/2009)
What if I run some kind of audit that requires the snapshot to represent a specific date and time?
Don't let the disk run out of space. In addition, make...
January 14, 2009 at 1:05 pm
Just don't call that directly from within a trigger. I detailed all the reasons earlier in this thread.
January 14, 2009 at 1:02 pm
Sandra Skaar (1/14/2009)
Total Drives (C, E, and F):Disk Writes/Sec: 10.74
Disk Reads/Sec: .067
Not so interested in the reads/sec. What does the avg sec/read and avg sec/write look like?
January 14, 2009 at 12:53 pm
Viewing 15 posts - 41,731 through 41,745 (of 49,562 total)