Viewing 6 posts - 1 through 6 (of 6 total)
From a query window run the following SQL:
SELECT * FROM MASTER..SYSMESSAGES
This will give you a list of the SQL server generated messages.
Also it's worth going into Enterprise manager go to...
June 19, 2002 at 4:58 am
You can set up an Alert via SQL Server Agent to monitor for Error number 18264 (Successful DB Dump). Also from here you set the alert to e-mail any addresses...
June 19, 2002 at 3:56 am
Kashif,
My apologies Antares686 is correct in saying you can set collation at DB level, I missed the fact your working with SQL2k. Tend to have my head stuck in SQL...
May 1, 2002 at 6:42 am
Unfortuantly you will have to re-install SQL Server with correct collation. If you have any databases you wish to retain then you will also have to think how your going...
May 1, 2002 at 3:50 am
If the database is only used for read only and from the information you have supplied my personal approach would be the following.
Have the option 'Truncate log on checkpoint' and...
May 1, 2002 at 3:43 am
NOLOCK only applies to the SELECT statement. Is it possible you may have an INSERT, UPDATE or DELETE statement in your SP which is causing the tablelock.
Rick.
April 30, 2002 at 4:43 am
Viewing 6 posts - 1 through 6 (of 6 total)