Jeffrey Williams-493691 (12/24/2009)

---

Yes, there are restrictions on database names - and there are quite a few special characters that will cause problems.

You probably could have gotten around that particular error...

kareem007 (12/2/2009)

---

george sibbald (12/2/2009)

---

sorry mixing up my threads here.

did you backup the log on the primary with the norecovery option? In that case the database will be in a restoring...

So in my case shall I enable AWE ?

Mark_Pratt (12/21/2009)

---

You will need to ensure that you have the /PAE (and maybe /3GB) switch in your boot.ini file and you have set the Enable the Lock Pages in Memory...

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

Thanks for your reply. So setting...

Grant Fritchey (12/16/2009)

---

I'm sorry, but the question is a bit vague. I'm assuming you're tasked with doing this at work and you've never done it before.

First, you need to differentiate...

@MTY-1082557

Any update, did you resolve the issue. Please post output of CHECKDB

If DBCC CHECKDB is taking longer than usual, there must be something wrong.

Please wait for CHECKDB to complete.

Meanwhile check below link.

http://www.microsoft.com/emea/teched2008/itpro/tv/default.aspx?vid=78

george sibbald (12/2/2009)

---

sorry mixing up my threads here.

did you backup the log on the primary with the norecovery option? In that case the database will be in a restoring state...

Thanks to everyone. Finally I have tested DR test in test servers, it was successfull. I did below things. Before doing in production, I want to check with you...

george sibbald (11/20/2009)

---

chk2009 (11/20/2009)

---

george sibbald (11/20/2009)

---

you will be fine if you if you:

run sp_help_revlogin against primary server and save output to file

copy file to secondary and load into SSMS query...

george sibbald (11/20/2009)

---

you will be fine if you if you:

run sp_help_revlogin against primary server and save output to file

copy file to secondary and load into SSMS query window

edit to remove...

george sibbald (11/20/2009)

---

you will be fine if you if you:

run sp_help_revlogin against primary server and save output to file

copy file to secondary and load into SSMS query window

edit to remove...

george sibbald (11/20/2009)

---

or else. drop the logins and use sp_help_revlogin to copy them over again.

OR

when you failover properly for the first time use stored procedure sp_change_users_login to tie the user...