SELECT @@SERVERNAME should do it.

John

Your insert statement is acquiring a lock on your table, which isn't released because the transaction hasn't been committed or rolled back.  That's why you get a timeout when your...

I think you can use a trigger.  If there's an insert or delete, you'll want to audit that, because a whole row will have been affected.  If there's an update,...

You can't do anything like that with SQL authentication in SQL Server 2000.  Your only options are to use Windows authentication or to upgrade to SQL Server 2005.

John

Fun and games!  I'm afraid you're also going to have to drop any foreign key constraints that reference your primary key, and recreate them afterwards.

John

So please show us what you've tried so far and we'll see how we can help.  We're not going to give you the answer on a plate, though.

John

So you want to change your primary key index from clustered to non-clustered?  I don't think you can - a clustered index has a totally different structure from a non-clustered...

Is this a homework question?

John

Kris

You might lose a little in efficiency, but what you'd gain is knowing that the integrity of your data is intact.  What happens if someone has more than three favourite...

It shouldn't do.  If it fails over it's because there's a problem with one of the cluster resources... you should ask the sysadmin to investigate this.

John

Imke

If your SQL Server cluster resource fails over in the middle of the backup, then the backup is bound to fail, since the resource will go offline momentarily.  Why is...

No need to ask the same question more than once.  Answered here:

http://www.sqlservercentral.com/forums/post.aspx?forumid=5&messageid=394583

You need to create a user in each database the login needs access to, then make that user a member of the necessary role (eg ddl_admin).

John

Kris

Since each user can have more than one favourite food, and each food can be favoured by more than one user, you need to create a junction table.  Try something...

Graeme

You say you have many such triggers.  Do any of them have DELETE statements in?  It looks as if one of them might be inserting a large number of rows...