Viewing 15 posts - 691 through 705 (of 2,436 total)
If you want to track your deadlock information add the following to your SQL Server startup parameters:
-T1204
-T3605
This way basic deadlock information is logged to the SQl Server errorlog.
June 11, 2007 at 8:53 am
What credentials is the SQL Agent using ?
What credentials is the SQL Job using ?
What credentials is the EM using ?
June 11, 2007 at 8:24 am
It is an unfortunate situation. Vendor software coded poorly - they did not understand security, nor did they care. You are pretty much stuck with what folks have already stated....
June 7, 2007 at 9:41 am
Another way to skin the cat. This onea bit more portable between versions:
select name from sysdatabases
where name not in ('master','model','msdb','tempdb','pubs','Northwind')
and DATABASEPROPERTYEX(name,'status')='ONLINE'
June 6, 2007 at 10:56 am
There should not be any issues nire a restart. However, backup the master database first !!!
Here is the general outline you'll need:
exec sp-configure 'allow updates',1
reconfigure with override
begin tran
select what you...
June 5, 2007 at 11:19 am
The only way to remove those stray rows is to edit the system table itself. If you are comfortable with SQL and mucking witth the system tables it is a...
June 5, 2007 at 10:55 am
Here is a handy reference for the system tables to start you off:
http://www.microsoft.com/sql/prodinfo/previousversions/systables.mspx
June 5, 2007 at 10:07 am
Is this a single or multiple CPU server ? If it is a single then upgrade immediately. If it has 2 CPUs see if you can go to 4 CPUs....
June 5, 2007 at 9:44 am
I am one of those clean screen folks but I just do not have the problem more than once with anybody. I just simply tell them not to. if they...
June 5, 2007 at 9:28 am
Viewing 15 posts - 691 through 705 (of 2,436 total)