Thanks for all of you help guys, this is exactly what Iwas looking for

Later jimmY

Work like you don't need the money.

Love like you've never been hurt.

And Dance like no one...

Thanks for you help guys, I used BOL as well as the tech. spec's from Microsoft's web sight to make my decision.

jimmY

Work like you don't need the money.

Love like you've...

Currently we are having a problem with blocks, so, we created a holding table and populated that table with what database, user, command, blocking spid, blockde spid, database id, wait...

The ISNULL(@kill , '') will replace the null value in @kill with a single space, this is needed because anything plus a null value results in a null.

jimmY

Work like you...

Confirm that your ODBC connection is valid, also, confirm that the user 'Helpdesk_ABC' is a user in the 'tech' database and has proper permission to complete that persons needed tasks.

jimmY

Work...

To give someone the capability to run scheduled tasks created a role in themsdb database and gave it these permissions, all in the msdb database. No, the only thing is...

I don't think that you can specify the backup filename when using a maintenance plan, what you could do is right click on the database and select all tasks|backup database...

I tried it with SQL Authentication, but the scheduler overides it with what it it running as. Also, due to security audits I am not allowed to have the other...

It may cause a deadlock, but couldn't you open another QA window and run a select count(*) based on what has ben updated. Just make sure to use the...

Sounds like your log file may be corrupted, have you tried sp_detach_db, then completly delete the log file, and run sp_attach_single_file_db?

jimmY

Work like you don't need the money.

Love like you've never...

Allen_Cui - the local instance is SQL 2000 on windows 2000 profesional, and the remote is SQL 7 on NT4.0, both machine are running in mixed authentication mode.

martinvg - I...

Yes, it does mean every user will be kicked out of the database. The reson behind this is that SQL Server needs to have complete control over the db before...

Since the login problem started happeneing when you failed the cluster over, I would check to make sure all of the client ODBC connection are going against the proper cluster...

My Bad, I ment to say need to check for SQL Server up and running, but thanks i to complete that check as well.

So far, I am thinking...

Are you talking about Linking to multiple servers and running a stored procedure on each server, then yes you would have to have the procedure on all remote SQL Servers....