I suppose now I must analyze your code. 😉

The lock is on a key. I believe this would only be a problem for a procedure that wants to...

Never had one either, so this pure theory.

Backup the active transaction log is a good idea. It depends on the page that is torn whether it will succeed, but...

In my case: Only once, just after installation.

I just assume that checking the backup logs should be sufficient.

Should I be ashamed now?

But every few months I get a request for...

Ludo,

Is this a problem? The insert is blocking the sp_space_used procedure. I suppose it is no problem if this procedure has to wait. The other way round,...

I have to confess I never did this on columns level and I get a syntax error (Line 3: Incorrect syntax near 'COLLATE') for the create statement in a SQL_Latin1_General_CP1_CI_AS...

What is te error message?

Oh, if you cannot browse it has probably something to do with the 1434 port. In that case just enter the instance name.

I would guess you have to update the statistics

I guess you are right that it is a permission problem. Did you check the permissions of the windows user that runs the SQLServer agent?

I know only a few things:

The input buf lines give you the first 255 characters of the statement. I hope you can figure out the rest of the statement...

We had the same problem for many queries.

Setting the compatibility to 70 solved it. Not a nice solution, but it worked.

I thought it had something to do...

You need a sort order / collation that is accent-insensitive. During SQLServer setup it is a very easy option. In SQLServer 2000 you can also select a non-default...

if _SMDBA_ is the user dbo, it would be :

select * from dbo.incident

Run DBCC checkdb or better use the maintenance plan to run it every night.

osql will do fine

Run it on the command line.

osql -? will give options.

If your login user has sufficient permissions on SQLServer the following should work:

osql -E -d database-name -i script-name...

I never heard about a suspend mode.

In case you meant suspect status, use sp_resetstatus database-name

But you really should find out what is the cause from the sqlserver logs before you...