New answers tagged sql-server-2005
As far as SQL Server is concerned, whenever results are going out the door, it's ASYNC_NETWORK_IO whether it's shared memory or TCP/IP.
Can you please look at SQL Server errorlog and see if you could find some relevant information on both Principal and mirror. Generally if SQL Server CPU utilization goes high above 50 % there can be failover. This is specifically caused by heavy load on SQL Server this is documented in Below Microsoft Web resource See 'recommendation for Configuring partner ...
My employer wants to keep the data, but not in a database, and wants to be able to restore it to that database if the need arises. If you want the data to be restored later, then best is to Script out schema of the tables that you wish to drop and save it as a sql script. BCP out the data (without using -n switch as -n is for native format which is ...
Not sure why your boss doesn't want to keep a backup of the DB on hand in the case of need of future restore, but I guess he has his reasons. The nice thing about exporting this data out to text files is that you could always import them back into databases that aren't necessarily SQL Server in the future - as well as read them with text editors in a pinch. ...
I would save the tables that you don't need as an SQL script - to be zipped afterwards. There's a freebie tool which does this here.
I finnaly found something : Reboot the server ! I absolutely have no idea why. Thanks @wBob for your help.
You might try scripting it out to see if you get a different behaviour. This simple example runs in under a minute on my local SQL 2005 instance: USE master GO SET NOCOUNT ON GO IF EXISTS ( SELECT * FROM sys.databases WHERE name = 'fullTextDemo3' ) BEGIN ALTER DATABASE fullTextDemo3 SET SINGLE_USER WITH ROLLBACK IMMEDIATE DROP DATABASE ...
Sounds like you want to consider READ COMMITTED SNAPSHOT ISOLATION, which uses tempdb to provide a point-in-time version of the data and prevents writers from blocking readers and vice-versa (as long as it's ok that readers do not see the most current version of the row). With a table that large and having this much of an impact by concurrent write ...
Top 50 recent answers are included