see my post immediately above, he needs to confirm he is logging into the correct instance first!

paulc.byrum (3/29/2010)

---

The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL...

Hi Paul

got that

Youngoz

upgrade straight to 2008, just bear in mind what i previously pointed out and as Jeffrey said update your stats too. The full rebuild should catch most of those anyway,...

whether upgrading to SQL server 2005 or 2008, immediately after run DBCC UPDATEUSAGE and rebuild all indexes. Also run DBCC CHECKDB with DATA_PURITY to ensure your database(s) have no metadata...

pandrikopoulos (3/28/2010)

---

Perry,

I agree in general with your suggestions but you should take into account that the database hosts a SAP application. SAP has some restrictions in the way a database...

what info does the event log show?

when upgrading from SQL Server 2000 to 2005 you are well advised to run DBCC UPDATEUSAGE and rebuild all indexes.

Having said that when carrying out normal maintenance on a SQL...

scripting the login accounts from the primary to the secondary should take care of any SID mismatches. Or just use the SP_Change_Users_Login stored procedure

Pull the network cable out!!!!

To bring secondary databases online, restore any...

No problem, glad i could help!

to execute as another database user that is not linked to a server level login

test the SP3 first on a test sql server to make sure it doesnt break anything!

river1 (3/24/2010)

---

I need to create a login and a user account in several databases using t-sql

I need to know where (in wich database) to create the login and the...

if you script this yourself just remember to disable or remove any foreign keys, triggers, etc first. Create the base schema (Tables) and load all the data then apply any...