When you execute the procedure as sa, you use the windows credentials of the service account, which in a lot of cases is a local administrator on the server.

If...

By default the public role has Execute permission on this procedure. I just checked it on 3 servers I recently installed.

So everybody should be able to use it.

If for...

May I ask why you would want such a table?

Try this:

SELECT * FROM [Servername\InstanceName].database.dbo.table

nitin.doshi (5/26/2009)

---

Instead of using profiler trace, using event notification we can store records for required events in a table. Laster, using SSRS a report can be developed which displays changes...

Since you started that second thread already two hours before installing SP2, it's probably a good idea to start the whole process from scratch again.

San (5/26/2009)

---

Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37

Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.1

(Build...

RTM is the first version which gets released without any patches. Could you post the results from this, just to be sure that SP2 is installed correctly:

SELECT @@VERSION

You say you configured this on your test server. Does that mean that the principal and the mirror databases are both on the same server? If that's the case you...

Sounds like the account under which you execute the backup, doesn't have enough permissions on the network share.

If you run the job under a local account, you have to give...

As for why SQL still don't start look in the Windows eventlog for the exact error message. You might just have made a typing error.

Why mirroring wasn't working I don't...

PS. Of course, if you have removed the parameters for the master files and the logfiles you must add them again.

(dC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf;

-eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG;

-lC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

)

This trace flag was only needed when SQL 2005 came out as RTM version which didn't support mirroring.

Once you install SP1 (or higher) you don't need this any more, so...

Did you try detaching the database and re-attach it using the correct filenames?

This article explains how the SQL 2000 passwords are hashed and more:

http://www.ngssoftware.com/papers/cracking-sql-passwords.pdf