DR Test Scenario

Hello All

We have Asynchronous DB Mirroring established for our Production database

which runs on SQL Server 2005.

For the DR Test we plan to do the following during the period of low activity :

1. Pause the mirroring on the Principal Server.

2. Break the mirror on the Mirror Server

3. Take on offline backup on the Mirror.

4. Bring the Mirror Database up.

5. Run the DR Tests on the Mirrored Database

6. Restore the Offline Backup taken in step 3.

7. Reestablish the mirror from the Principal to Mirror.

8. Resume Mirroring on the Principal Server.

9. Verify Mirroring is happening on the Mirror Server

Can u please let me know if this plan is feasible and if there should be any modifications to the plan that are required. Any other suggestions/input is appreciated.

TIA

Best,

Jay

Hi Jay,

You do need to pause and break the mirror on two different places to start with. Also I don't think your plan is feasible.

If you want to test the Mirror. DO the following:

1. Perform a backup of Principal database.

2. Break the mirror. (if you don't intend to keep changes from DR test)

3. Bring the mirror online.

4. Do your tests on the mirror.

5. Once finished testing, restore the database backup , taken in Step 1, to the as mirror db on mirror server.

6. Apply any logs if any necessary.

7. reconfigure mirroring.

Jag

Downgrade Install Plan

We are upgrading an application that is not yet supported on SQL Server 2005. The upgrade involves new hardware (including a new sql server). Any gotchas or advice regarding this plan:

1. Install Windows 2003 64 bit, configure hardware appropriately for running SQL Server.

2. Install SQL Server 2000 64 bit using the 2005 license key (is that how you 'downgrade'? I didn't see a 'how-to' article regarding this).

3. Restore backups of system databases from current SQL Server to new SQL Server (note: current SQL Server is running 32 bit - I realize that I need to make sure that I have the same service pack on the new server as that on the current server).

4. Apply sp4.

5. Restore user databases.

Not sure if the 32 vs. 64 bit thing is of any concern or if 'downgrading' is as simple as this.

Thanks!

Michelle

1. What is the version of current SQL Server? SQL Server 2005 requires SP1 for Windows 2003 Enterprise Edittion on x64 machines.

2. I do not think you can install SQL Server 2000 with SQL Server 2005 product key.

The following issues are clear.

1. SQL Server 2000 and SQL Server 2005 can be installed side by side successfully.

2. 32-bit SQL Server 2000/2005 can be installed side by side successfully on x64 machines.

3. 32-bit SQL Server 2005 and 64-bit SQL Server 2005 can be installed successfully on x64 machines.

|||I did talk to our Microsoft Solution Specialist and he explained that

we should already have the required license and media to install SQL

Server 2000 with our most recent media kit shipment. I don't think that

I will be prompted for a license key at all.

I'm hoping that the server admin team will be finished with the

hardware/os in the next couple of days so that I can start on my

portion. I'll document any issues that I have.

Thanks,

Michelle|||

Michelle,

Did you have any problems with your original installation plan? We are trying to do the same installation and it is unclear how to install 2000 with 2005 disks and keys. There is no prompting on install.

|||I did not have any problems but in hindsight had wished that I had

installed SQL Server 2005 as the default instance and 2000 as a named

instance. I believe that this would have made the upgrade to 2005

simpler. We have since built other machines this way.

Downgrade Install Plan

We are upgrading an application that is not yet supported on SQL Server 2005. The upgrade involves new hardware (including a new sql server). Any gotchas or advice regarding this plan:

1. Install Windows 2003 64 bit, configure hardware appropriately for running SQL Server.

2. Install SQL Server 2000 64 bit using the 2005 license key (is that how you 'downgrade'? I didn't see a 'how-to' article regarding this).

3. Restore backups of system databases from current SQL Server to new SQL Server (note: current SQL Server is running 32 bit - I realize that I need to make sure that I have the same service pack on the new server as that on the current server).

4. Apply sp4.

5. Restore user databases.

Not sure if the 32 vs. 64 bit thing is of any concern or if 'downgrading' is as simple as this.

Thanks!

Michelle

1. What is the version of current SQL Server? SQL Server 2005 requires SP1 for Windows 2003 Enterprise Edittion on x64 machines.

2. I do not think you can install SQL Server 2000 with SQL Server 2005 product key.

The following issues are clear.

1. SQL Server 2000 and SQL Server 2005 can be installed side by side successfully.

2. 32-bit SQL Server 2000/2005 can be installed side by side successfully on x64 machines.

3. 32-bit SQL Server 2005 and 64-bit SQL Server 2005 can be installed successfully on x64 machines.

|||I did talk to our Microsoft Solution Specialist and he explained that we should already have the required license and media to install SQL Server 2000 with our most recent media kit shipment. I don't think that I will be prompted for a license key at all.
I'm hoping that the server admin team will be finished with the hardware/os in the next couple of days so that I can start on my portion. I'll document any issues that I have.
Thanks,
Michelle
|||

Michelle,

Did you have any problems with your original installation plan? We are trying to do the same installation and it is unclear how to install 2000 with 2005 disks and keys. There is no prompting on install.

|||I did not have any problems but in hindsight had wished that I had installed SQL Server 2005 as the default instance and 2000 as a named instance. I believe that this would have made the upgrade to 2005 simpler. We have since built other machines this way.

downgrade from sql 2k enterprise edition to standard

Hello All,
I need to downgrade my production server from enterprise to standard edition
because of cost.
Has anyone been through this scenario?
My plan is to backup all dbs, leave data folders intact (I have db files in
4 drives), uninstall enterprise, install standard and reattach db files.
My questions are:
I have tons of jobs and DTS packages on the server. Can I simply restore
the msdb from enterprise or is it going to have problem with standard
edition?
Does anyone have a script to save logins and restore logins?
Thanks for any help,
sqlgirl"Biva" <biva.yauchler@.redprairie.com> wrote in message
news:407a9a90$0$40211$39cecf19@.news.twtelecom.net...
> Hello All,
> I need to downgrade my production server from enterprise to standard
edition
> because of cost.
> Has anyone been through this scenario?
> My plan is to backup all dbs, leave data folders intact (I have db files
in
> 4 drives), uninstall enterprise, install standard and reattach db files.
> My questions are:
> I have tons of jobs and DTS packages on the server. Can I simply restore
> the msdb from enterprise or is it going to have problem with standard
> edition?
> Does anyone have a script to save logins and restore logins?
The following links should help you in the restore and account migration
process:
http://support.microsoft.com/defaul...kb;en-us;246133
http://support.microsoft.com/defaul...2&Product=sql2k
With regard to your question on MSDB restore, I'm less certain if that will
work... If the SQL Server builds are the same I think you'll be OK, if not,
please see the following link:
http://support.microsoft.com/defaul...4&Product=sql2k
Also, you may want to consider running SQL backups on all of your databases,
prior to uninstalling SQL Server. This will give you one more avenue for the
restore process.
Steve|||Hi Biva,
I am reviewing your post and our MVP provide you some good links for you
question, I want to know if you still have any question on this issue. For
any question, please feel free to post message here and we are glad to help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

downgrade from sql 2k enterprise edition to standard

Hello All,
I need to downgrade my production server from enterprise to standard edition
because of cost.
Has anyone been through this scenario?
My plan is to backup all dbs, leave data folders intact (I have db files in
4 drives), uninstall enterprise, install standard and reattach db files.
My questions are:
I have tons of jobs and DTS packages on the server. Can I simply restore
the msdb from enterprise or is it going to have problem with standard
edition?
Does anyone have a script to save logins and restore logins?
Thanks for any help,
sqlgirl
"Biva" <biva.yauchler@.redprairie.com> wrote in message
news:407a9a90$0$40211$39cecf19@.news.twtelecom.net. ..
> Hello All,
> I need to downgrade my production server from enterprise to standard
edition
> because of cost.
> Has anyone been through this scenario?
> My plan is to backup all dbs, leave data folders intact (I have db files
in
> 4 drives), uninstall enterprise, install standard and reattach db files.
> My questions are:
> I have tons of jobs and DTS packages on the server. Can I simply restore
> the msdb from enterprise or is it going to have problem with standard
> edition?
> Does anyone have a script to save logins and restore logins?
The following links should help you in the restore and account migration
process:
http://support.microsoft.com/default...b;en-us;246133
http://support.microsoft.com/default...&Product=sql2k
With regard to your question on MSDB restore, I'm less certain if that will
work... If the SQL Server builds are the same I think you'll be OK, if not,
please see the following link:
http://support.microsoft.com/default...&Product=sql2k
Also, you may want to consider running SQL backups on all of your databases,
prior to uninstalling SQL Server. This will give you one more avenue for the
restore process.
Steve
|||Hi Biva,
I am reviewing your post and our MVP provide you some good links for you
question, I want to know if you still have any question on this issue. For
any question, please feel free to post message here and we are glad to help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Domain user account

New to SQL Server. Plan to install SQL Server 2005 standard edition on Windows 2k3. After searched a lot of places, still don't understand what exactly "domain user account" is. Could someone explain it to me?
1. Is this a OS account where SQL Server is running?
2. Or, is this an account under domain controller on other machine? Is this an account on DNS srver? How do I create it?
3. Or, is this an account in SQL Server?

Where is this account located? How do I manage it?

TIA.

A domain account in the Windows world is a user account in a shared security database. The current domain system is called Active Directory. It does not only store user accounts but a wide range of data used in a networking system (groups, computers, printers, software packages...). Those entities are stored on domain controllers, i.e. Windows Server with some services implementing the server side of a domain. You can have multiple domain controllers which replicate the domain data like user accounts with each other. Computers and users which are part of the domain can be authenticated by those domain controllers, so they can get authorized to execute tasks on their or other computers in the domain.

So:

1) Typically not, only if your SQL Server is running on a Windows Server which is also domain controller.

2) Yes, the account is from a domain controller, or from the security database of a domain which is hosted on its domain controllers. A DNS server plays no specific role here, except that Active Directory does need a DNS server. You create those account with Start->Programs->Administrative Templates->Active Directory Users And Computers. This management console is installed on domain contollers. You can manually install it from adminpak.msi which exists on Servers under windows\system32.

3) No. You can "import" a domain account to give it login rights and assign database roles.

The nice part about domain accounts is, that you have a centralized place for user authentication, once authenticated on a system that authentication can be used agains other computers of the same domain and be authorized to do things on those computers. In contrast, in a workgroup you would need to log on to every computer indivually, except when you manage to have your user account and password synchronized manually on all machines you want to access.

--
SvenC

|||

Thank you for your response.

I should state my situation more clearly. Three MS 2003 servers. Plan to install sql server 2005 on them. One as principle, one as mirror, and one as witness. Don't have any control on domain controller.

I can see my computers on my MS Windows Network. I guess that I only have computer account on domain controller. Is it true only the administrator on domain controller can add a domain user account? If a domain user account has been added, how do I use this account in my local 2003 server to run sql server services? Where to put domain user name and password? How do I know this domain user is in trusted domains? In order to setup mirroring, should I use this account on all three machines?

My database will only be used to accept client requests from IIS on another machine. If running sql services under domain user account is too much trouble, create same local user account on all the machine and run service under this same user account, will this work for mirroring. Do I need to create certificate?

Just try to find an easy way to setup mirroring. MS BOL is not much helpful.

|||

You can set a domain account as your service account, using the SQL Server Configuration Manager tool. The SQL Server 2005 setup program will also allow you to select a domain account as the service account. For questions on setting up database mirroring, you should however post on the Database Mirroring forum instead of this one.

Thanks
Laurentiu

Domain user account

New to SQL Server. Plan to install SQL Server 2005 standard edition on Windows 2k3. After searched a lot of places, still don't understand what exactly "domain user account" is. Could someone explain it to me?
1. Is this a OS account where SQL Server is running?
2. Or, is this an account under domain controller on other machine? Is this an account on DNS srver? How do I create it?
3. Or, is this an account in SQL Server?

Where is this account located? How do I manage it?

TIA.

A domain account in the Windows world is a user account in a shared security database. The current domain system is called Active Directory. It does not only store user accounts but a wide range of data used in a networking system (groups, computers, printers, software packages...). Those entities are stored on domain controllers, i.e. Windows Server with some services implementing the server side of a domain. You can have multiple domain controllers which replicate the domain data like user accounts with each other. Computers and users which are part of the domain can be authenticated by those domain controllers, so they can get authorized to execute tasks on their or other computers in the domain.

So:

1) Typically not, only if your SQL Server is running on a Windows Server which is also domain controller.

2) Yes, the account is from a domain controller, or from the security database of a domain which is hosted on its domain controllers. A DNS server plays no specific role here, except that Active Directory does need a DNS server. You create those account with Start->Programs->Administrative Templates->Active Directory Users And Computers. This management console is installed on domain contollers. You can manually install it from adminpak.msi which exists on Servers under windows\system32.

3) No. You can "import" a domain account to give it login rights and assign database roles.

The nice part about domain accounts is, that you have a centralized place for user authentication, once authenticated on a system that authentication can be used agains other computers of the same domain and be authorized to do things on those computers. In contrast, in a workgroup you would need to log on to every computer indivually, except when you manage to have your user account and password synchronized manually on all machines you want to access.

--
SvenC

|||

Thank you for your response.

I should state my situation more clearly. Three MS 2003 servers. Plan to install sql server 2005 on them. One as principle, one as mirror, and one as witness. Don't have any control on domain controller.

I can see my computers on my MS Windows Network. I guess that I only have computer account on domain controller. Is it true only the administrator on domain controller can add a domain user account? If a domain user account has been added, how do I use this account in my local 2003 server to run sql server services? Where to put domain user name and password? How do I know this domain user is in trusted domains? In order to setup mirroring, should I use this account on all three machines?

My database will only be used to accept client requests from IIS on another machine. If running sql services under domain user account is too much trouble, create same local user account on all the machine and run service under this same user account, will this work for mirroring. Do I need to create certificate?

Just try to find an easy way to setup mirroring. MS BOL is not much helpful.

|||

You can set a domain account as your service account, using the SQL Server Configuration Manager tool. The SQL Server 2005 setup program will also allow you to select a domain account as the service account. For questions on setting up database mirroring, you should however post on the Database Mirroring forum instead of this one.

Thanks
Laurentiu

Does transactional replication require DTC?

Hi
Does the DTC service need to function properly if I plan to use
transactional replication between two Microsoft SQL Server 2000 machines?
Many thanks,
Oskar
no, unless you are using immediate updating.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:71A33B88-8AB7-4395-97DC-32F463381F26@.microsoft.com...
> Hi
> Does the DTC service need to function properly if I plan to use
> transactional replication between two Microsoft SQL Server 2000 machines?
> --
> Many thanks,
> Oskar
>