Viewing 15 posts - 44,386 through 44,400 (of 49,571 total)
Duplicate post. No replies to this thread please. Direct replies to:
http://www.sqlservercentral.com/Forums/Topic572937-146-1.aspx
September 20, 2008 at 2:27 am
Have a look at database mirroring. It looks, from your requirements, that it would be a closer fit than replication
September 20, 2008 at 2:25 am
MANU (9/19/2008)
Try comparing physical and logical reads on both system by turning on statistics for I/O.SET statistics io on
MJ
And statistics time. I'd like to see where the time difference appears.
if...
September 20, 2008 at 2:21 am
webrunner (9/19/2008)
(Someone might unwittingly think the tempdb is just a backup and may delete it accidentally.)
If SQL's running, the files can't be deleted as SQL will have them...
September 19, 2008 at 3:26 pm
Jeffrey Williams (9/19/2008)
Just a guess, but I think you'll find that the difference in the execution plans is due to your production system escalating to a parallel plan.
I'm thinking much...
September 19, 2008 at 3:25 pm
If you run a select under the default isolation level (read committed), the lock taken will prevent any changes to the table while the select is running (insert, update, delete),...
September 19, 2008 at 3:18 pm
What's the fragmentation on that index and the clustered index like?
September 19, 2008 at 3:18 pm
You may want to contact customer support on this. It sounds like a bug.
September 19, 2008 at 2:29 pm
avipenina (9/19/2008)
both server was restart so the execution plan on both are from scratch.
Doesn't mean they'll be the same. Please look at the exec plan on the two servers and...
September 19, 2008 at 2:28 pm
Inside SQL Server 2005: The storage engine goes into a fair bit of detail on the storage engine.
The Guru's guide to SQl Architecture and internals has a lot of info...
September 19, 2008 at 9:30 am
SQL triggers fire once per operation, not once per row. SQL doesn't have row-triggers.
Cursors in a trigger are a near-guarantee of poor performance and potential deadlocks. Triggers should be written...
September 19, 2008 at 9:24 am
And make sure that the SQL service and SQL Agent are shut down.
September 19, 2008 at 9:20 am
Shark Energy (9/19/2008)
Is it just me or was some of the advice in this topic very very risky?
It's not just you. Some were more than 'very risky'
September 19, 2008 at 9:15 am
Odd. That message indicates a forced disconnect (a kill command, or an error of severity 20 or higher) or a network glitch.
A kill or severe error should show up...
September 19, 2008 at 9:14 am
Run perfmon and monitor from there. I normally just run it directly from the run dialog or command line.
For the databases counters you should see something like the attached...
September 19, 2008 at 9:13 am
Viewing 15 posts - 44,386 through 44,400 (of 49,571 total)