Mirroring Failover/Failback

I have been using Mirroring now for a while and put the system into
production now after applying SQL sp 1.
We have a setup with a witness, principal and mirror with certificates (the
witness is on a webserver in a different domain, so we can't use integrated
security).
Automatic failover works fine if we take down the principal. But when the
principal is up and running again, no automatic failback occur. If this by
design, or is there something I've missed out in the configuration?
Per SchjetneThe roles for mirroring are soft roles. So, you cannot define a preferred no
de (like you can for a
cluster). If you want to fail back, you have to ask for it (ALTER DATABASE).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>I have been using Mirroring now for a while and put the system into product
ion now after applying
>SQL sp 1.
> We have a setup with a witness, principal and mirror with certificates (th
e witness is on a
> webserver in a different domain, so we can't use integrated security).
> Automatic failover works fine if we take down the principal. But when the
principal is up and
> running again, no automatic failback occur. If this by design, or is there
something I've missed
> out in the configuration?
> Per Schjetne
>|||"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>I have been using Mirroring now for a while and put the system into
>production now after applying SQL sp 1.
> We have a setup with a witness, principal and mirror with certificates
> (the witness is on a webserver in a different domain, so we can't use
> integrated security).
> Automatic failover works fine if we take down the principal. But when the
> principal is up and running again, no automatic failback occur. If this by
> design, or is there something I've missed out in the configuration?
Sorry, there isn't an option for automatic failback. You will have to do
that manually.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp|||If you think about it, failing back will cause all client connections to be
dropped again so you probably don't want SQL Server to decide when is a good
time to fail back. It's probably much better if you pick a time when the
change won't affect too many users.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>I have been using Mirroring now for a while and put the system into
>production now after applying SQL sp 1.
> We have a setup with a witness, principal and mirror with certificates
> (the witness is on a webserver in a different domain, so we can't use
> integrated security).
> Automatic failover works fine if we take down the principal. But when the
> principal is up and running again, no automatic failback occur. If this by
> design, or is there something I've missed out in the configuration?
> Per Schjetne
>|||I agree on that. Is there a way to query any system tables telling me which
database is acting as principal vs mirror? Is the witness aware of this, or
is it just monitoring which server is replying, being able to do a failover?
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23J5%23JJhaGHA.1192@.TK2MSFTNGP04.phx.gbl...
> If you think about it, failing back will cause all client connections to
> be dropped again so you probably don't want SQL Server to decide when is a
> good time to fail back. It's probably much better if you pick a time when
> the change won't affect too many users.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
> news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>|||There's an event that you can monitor to be notified when the state changes.
The sys.dm_database_mirroring view can be used to determine the mirroring
state of all the databases of an instance. The
sys.dm_database_mirroring_witnesses can be used from the witness to see
which server is the primary.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:OLn03SiaGHA.2368@.TK2MSFTNGP03.phx.gbl...
>I agree on that. Is there a way to query any system tables telling me which
>database is acting as principal vs mirror? Is the witness aware of this, or
>is it just monitoring which server is replying, being able to do a
>failover?
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:%23J5%23JJhaGHA.1192@.TK2MSFTNGP04.phx.gbl...
>|||That's not exactly correct.
The reason it did not failback, is because that database is no longer the
principal. Failover causes a role reversal. When it fails over to the
mirror, that database is promoted to a principal and begins serving the
database. When the other database comes online, its role is automatically
demoted to mirror and the transactions start flowing back to it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eDV9lIeaGHA.4936@.TK2MSFTNGP05.phx.gbl...
> The roles for mirroring are soft roles. So, you cannot define a preferred
> node (like you can for a cluster). If you want to fail back, you have to
> ask for it (ALTER DATABASE).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
> news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>|||Thanks! Just what I needed. By the way, the correct tablename is:
sys.database_mirroring_witnesses
Per :-)
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23bsLDGkaGHA.3720@.TK2MSFTNGP03.phx.gbl...
> There's an event that you can monitor to be notified when the state
> changes.
> The sys.dm_database_mirroring view can be used to determine the mirroring
> state of all the databases of an instance. The
> sys.dm_database_mirroring_witnesses can be used from the witness to see
> which server is the primary.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
> news:OLn03SiaGHA.2368@.TK2MSFTNGP03.phx.gbl...
>

Mirroring Failover/Failback

I have been using Mirroring now for a while and put the system into
production now after applying SQL sp 1.
We have a setup with a witness, principal and mirror with certificates (the
witness is on a webserver in a different domain, so we can't use integrated
security).
Automatic failover works fine if we take down the principal. But when the
principal is up and running again, no automatic failback occur. If this by
design, or is there something I've missed out in the configuration?
Per SchjetneThe roles for mirroring are soft roles. So, you cannot define a preferred node (like you can for a
cluster). If you want to fail back, you have to ask for it (ALTER DATABASE).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>I have been using Mirroring now for a while and put the system into production now after applying
>SQL sp 1.
> We have a setup with a witness, principal and mirror with certificates (the witness is on a
> webserver in a different domain, so we can't use integrated security).
> Automatic failover works fine if we take down the principal. But when the principal is up and
> running again, no automatic failback occur. If this by design, or is there something I've missed
> out in the configuration?
> Per Schjetne
>|||"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>I have been using Mirroring now for a while and put the system into
>production now after applying SQL sp 1.
> We have a setup with a witness, principal and mirror with certificates
> (the witness is on a webserver in a different domain, so we can't use
> integrated security).
> Automatic failover works fine if we take down the principal. But when the
> principal is up and running again, no automatic failback occur. If this by
> design, or is there something I've missed out in the configuration?
Sorry, there isn't an option for automatic failback. You will have to do
that manually.
--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp|||If you think about it, failing back will cause all client connections to be
dropped again so you probably don't want SQL Server to decide when is a good
time to fail back. It's probably much better if you pick a time when the
change won't affect too many users.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>I have been using Mirroring now for a while and put the system into
>production now after applying SQL sp 1.
> We have a setup with a witness, principal and mirror with certificates
> (the witness is on a webserver in a different domain, so we can't use
> integrated security).
> Automatic failover works fine if we take down the principal. But when the
> principal is up and running again, no automatic failback occur. If this by
> design, or is there something I've missed out in the configuration?
> Per Schjetne
>|||I agree on that. Is there a way to query any system tables telling me which
database is acting as principal vs mirror? Is the witness aware of this, or
is it just monitoring which server is replying, being able to do a failover?
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23J5%23JJhaGHA.1192@.TK2MSFTNGP04.phx.gbl...
> If you think about it, failing back will cause all client connections to
> be dropped again so you probably don't want SQL Server to decide when is a
> good time to fail back. It's probably much better if you pick a time when
> the change won't affect too many users.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
> news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>>I have been using Mirroring now for a while and put the system into
>>production now after applying SQL sp 1.
>> We have a setup with a witness, principal and mirror with certificates
>> (the witness is on a webserver in a different domain, so we can't use
>> integrated security).
>> Automatic failover works fine if we take down the principal. But when the
>> principal is up and running again, no automatic failback occur. If this
>> by design, or is there something I've missed out in the configuration?
>> Per Schjetne
>|||There's an event that you can monitor to be notified when the state changes.
The sys.dm_database_mirroring view can be used to determine the mirroring
state of all the databases of an instance. The
sys.dm_database_mirroring_witnesses can be used from the witness to see
which server is the primary.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:OLn03SiaGHA.2368@.TK2MSFTNGP03.phx.gbl...
>I agree on that. Is there a way to query any system tables telling me which
>database is acting as principal vs mirror? Is the witness aware of this, or
>is it just monitoring which server is replying, being able to do a
>failover?
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:%23J5%23JJhaGHA.1192@.TK2MSFTNGP04.phx.gbl...
>> If you think about it, failing back will cause all client connections to
>> be dropped again so you probably don't want SQL Server to decide when is
>> a good time to fail back. It's probably much better if you pick a time
>> when the change won't affect too many users.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
>> news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>>I have been using Mirroring now for a while and put the system into
>>production now after applying SQL sp 1.
>> We have a setup with a witness, principal and mirror with certificates
>> (the witness is on a webserver in a different domain, so we can't use
>> integrated security).
>> Automatic failover works fine if we take down the principal. But when
>> the principal is up and running again, no automatic failback occur. If
>> this by design, or is there something I've missed out in the
>> configuration?
>> Per Schjetne
>>
>|||That's not exactly correct.
The reason it did not failback, is because that database is no longer the
principal. Failover causes a role reversal. When it fails over to the
mirror, that database is promoted to a principal and begins serving the
database. When the other database comes online, its role is automatically
demoted to mirror and the transactions start flowing back to it.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eDV9lIeaGHA.4936@.TK2MSFTNGP05.phx.gbl...
> The roles for mirroring are soft roles. So, you cannot define a preferred
> node (like you can for a cluster). If you want to fail back, you have to
> ask for it (ALTER DATABASE).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
> news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>>I have been using Mirroring now for a while and put the system into
>>production now after applying SQL sp 1.
>> We have a setup with a witness, principal and mirror with certificates
>> (the witness is on a webserver in a different domain, so we can't use
>> integrated security).
>> Automatic failover works fine if we take down the principal. But when the
>> principal is up and running again, no automatic failback occur. If this
>> by design, or is there something I've missed out in the configuration?
>> Per Schjetne
>|||Thanks! Just what I needed. By the way, the correct tablename is:
sys.database_mirroring_witnesses
Per :-)
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23bsLDGkaGHA.3720@.TK2MSFTNGP03.phx.gbl...
> There's an event that you can monitor to be notified when the state
> changes.
> The sys.dm_database_mirroring view can be used to determine the mirroring
> state of all the databases of an instance. The
> sys.dm_database_mirroring_witnesses can be used from the witness to see
> which server is the primary.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
> news:OLn03SiaGHA.2368@.TK2MSFTNGP03.phx.gbl...
>>I agree on that. Is there a way to query any system tables telling me
>>which database is acting as principal vs mirror? Is the witness aware of
>>this, or is it just monitoring which server is replying, being able to do
>>a failover?
>>
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:%23J5%23JJhaGHA.1192@.TK2MSFTNGP04.phx.gbl...
>> If you think about it, failing back will cause all client connections to
>> be dropped again so you probably don't want SQL Server to decide when is
>> a good time to fail back. It's probably much better if you pick a time
>> when the change won't affect too many users.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
>> news:uo3Ac4caGHA.3736@.TK2MSFTNGP04.phx.gbl...
>>I have been using Mirroring now for a while and put the system into
>>production now after applying SQL sp 1.
>> We have a setup with a witness, principal and mirror with certificates
>> (the witness is on a webserver in a different domain, so we can't use
>> integrated security).
>> Automatic failover works fine if we take down the principal. But when
>> the principal is up and running again, no automatic failback occur. If
>> this by design, or is there something I've missed out in the
>> configuration?
>> Per Schjetne
>>
>>
>

Mirroring

Hello,

I have Microsoft SQL SERVER 2005 installed in my system.

To try out mirroring, I rightclicked on the database went to the tasks, but i found that in Status its written

"This database has not been configured for mirroring"

What shall I do now?

I think there are 2 possibilities,

1. You have Sql server RTM.......Microsoft supports mirroring from Sql 2005 SP1.......with RTM also you can configure mirroring but prior to that you need to start sql server with Trace flag -T1400 and then proceed with mirroring.

2. You need to take full backup and one transactional log backup in principal server and restore it in mirror server using the option WITH NORECOVERY for both the full backup and tran log backup.............then start configuring mirroring it will work perfectly...........

refer these links for mirroring,

http://sql-articles.com/articles.php?pageNum_alltop=3&totalRows_alltop=35

http://sql-articles.com/articles/dbmrr.htm

Revert if you need any more help............

Thanxx

Deepak

|||

downloading sp1.

Will certainly revert if any problem arises.

Thank you

|||Which SQL edition you installed? Only Standard and Enterprise supports Database Mirroring (SQL Server 2005 Features Comparison - http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx).|||

You can download the latest service pack SP2 for SQL 2005 from

http://technet.microsoft.com/en-us/sqlserver/bb331754.aspx instead of SP1..........

Mirroring

Hello,

I have Microsoft SQL SERVER 2005 installed in my system.

To try out mirroring, I rightclicked on the database went to the tasks, but i found that in Status its written

"This database has not been configured for mirroring"

What shall I do now?

I think there are 2 possibilities,

1. You have Sql server RTM.......Microsoft supports mirroring from Sql 2005 SP1.......with RTM also you can configure mirroring but prior to that you need to start sql server with Trace flag -T1400 and then proceed with mirroring.

2. You need to take full backup and one transactional log backup in principal server and restore it in mirror server using the option WITH NORECOVERY for both the full backup and tran log backup.............then start configuring mirroring it will work perfectly...........

refer these links for mirroring,

http://sql-articles.com/articles.php?pageNum_alltop=3&totalRows_alltop=35

http://sql-articles.com/articles/dbmrr.htm

Revert if you need any more help............

Thanxx

Deepak

|||

downloading sp1.

Will certainly revert if any problem arises.

Thank you

|||Which SQL edition you installed? Only Standard and Enterprise supports Database Mirroring (SQL Server 2005 Features Comparison - http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx).|||

You can download the latest service pack SP2 for SQL 2005 from

http://technet.microsoft.com/en-us/sqlserver/bb331754.aspx instead of SP1..........

Mirroring

Is there a way to detect if the principal or mirror is running the database?
I want build my own altert system, sending an SMS whenever a automatic
failover/failback happens.
Per Schjetne"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
You can set alerts on the messages in the event log. Talk to your monitoring
application vendor for more info.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp|||select * from sys.database_mirroring
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>|||The sys.dm_database_mirroring view will give you the state information that
you
need to monitor. You will need to access this on both partners.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>

Mirroring

Is there a way to detect if the principal or mirror is running the database?
I want build my own altert system, sending an SMS whenever a automatic
failover/failback happens.
Per Schjetne"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
You can set alerts on the messages in the event log. Talk to your monitoring
application vendor for more info.
--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp|||select * from sys.database_mirroring
--
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>|||The sys.dm_database_mirroring view will give you the state information that
you
need to monitor. You will need to access this on both partners.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>

Migratre from SQL 2000 to SQL 2005

Migrating from SQL Server 2000 t o SQL Server 2005, what do I need to do wit
h
the system Database (master, tempdb, model, and msdb)? what needs to be
migrate over and what not need to moved over?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200707/1Have you read this guide:
http://www.microsoft.com/downloads/...&displaylang=en
Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"ajsql via droptable.com" <u35479@.uwe> wrote in message
news:749f424e180d9@.uwe...
> Migrating from SQL Server 2000 t o SQL Server 2005, what do I need to do
> with
> the system Database (master, tempdb, model, and msdb)? what needs to be
> migrate over and what not need to moved over?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200707/1
>

Migratre from SQL 2000 to SQL 2005

Migrating from SQL Server 2000 t o SQL Server 2005, what do I need to do with
the system Database (master, tempdb, model, and msdb)? what needs to be
migrate over and what not need to moved over?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200707/1
Have you read this guide:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&displaylang=en

Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"ajsql via droptable.com" <u35479@.uwe> wrote in message
news:749f424e180d9@.uwe...
> Migrating from SQL Server 2000 t o SQL Server 2005, what do I need to do
> with
> the system Database (master, tempdb, model, and msdb)? what needs to be
> migrate over and what not need to moved over?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200707/1
>

Migratre from SQL 2000 to SQL 2005

Migrating from SQL Server 2000 t o SQL Server 2005, what do I need to do with
the system Database (master, tempdb, model, and msdb)? what needs to be
migrate over and what not need to moved over?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200707/1Have you read this guide:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&displaylang=en
Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"ajsql via SQLMonster.com" <u35479@.uwe> wrote in message
news:749f424e180d9@.uwe...
> Migrating from SQL Server 2000 t o SQL Server 2005, what do I need to do
> with
> the system Database (master, tempdb, model, and msdb)? what needs to be
> migrate over and what not need to moved over?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200707/1
>

Migraton from Enterprise to Standard

Hi
I wan to migrate an SQL Enterprise server system to SQL Standard system.
Can somebody guide me throgh the process?
Thanks
KNDHi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migraton from Enterprise to Standard

Hi
I wan to migrate an SQL Enterprise server system to SQL Standard system.
Can somebody guide me throgh the process?
Thanks
KND
Hi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migraton from Enterprise to Standard

H
I wan to migrate an SQL Enterprise server system to SQL Standard system
Can somebody guide me throgh the process
Thank
KNDHi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migration to Yukon

Hi,

Anyone kindly let me know more and clear details about the below 2 statements

1.Remove reference to undocumented system tables/stored procs

2. Remove statements modifying system objects

as are not supported in SQL Server 2005. while migrating from sql server 2000 to YUkon (sql server 2005) the above 2 points need to be taken care. but no much clarity on the above.

kindly help me

Regards

Crish

Hi,

not sure above the first one, which procedure are deprecated but the latter one had some major chnages. The system objects are now in the sys schema,e.g. changing the sysobjects to sys.objects. if you used INFORMATION_SCHEMA views before you don′t need to change anything, because the views were also modified to reflect the changes, if you use direct access to the system tables, you have to change your code.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||Thanks much for the information Jens.

Migration to new cluster enviroment

My production system is on stand alone Server and it is a publisher on the
replication system. I need to Migrate to a new hardware with fail over
cluster and upgrade to SQL 2005 .
I need to do that with out impacting replication. What is my options? Can I
do that Or not
If this was to stand alone new hardware I will have no issue.
Thanks for your help
You can't do it without any impact to replication, but you should be able to
with minimal impact.
Build out your new system and test thoroughly. Once you are confident that
the new system performs adequately, then drop your publication on the
production database and copy it (several options here for you) to the new
system.
You will have to redirect your clients to the new host name and reestablish
replication publication.
This should be doable during a reasonable off hours maintenance window.
Sincerely,
Anthony Thomas

<msnews.microsoft.com> wrote in message
news:ek7ECL6THHA.1552@.TK2MSFTNGP05.phx.gbl...
> My production system is on stand alone Server and it is a publisher on the
> replication system. I need to Migrate to a new hardware with fail over
> cluster and upgrade to SQL 2005 .
> I need to do that with out impacting replication. What is my options? Can
I
> do that Or not
> If this was to stand alone new hardware I will have no issue.
> Thanks for your help
>

migration from 32 bit to 64 bit

Hi, I want to upgrade a server from a 32 bit system to a 64 bit system, will
i be able to use my same license with the new server or should i need to buy
a new license for the 64 bit server?
Thanks in advance for the help.
Regards,> Hi, I want to upgrade a server from a 32 bit system to a 64 bit system,
> will
> i be able to use my same license with the new server or should i need to
> buy
> a new license for the 64 bit server?
<Excerpt href="http://links.10026.com/?link=">http://www.microsoft.com/sql/howtobuy/default.mspx">
While you should choose the platform that matches your current hardware (in
order to obtain the appropriate media), SQL Server licenses are not platform
specific. For example, if you currently have a 32-bit server and plan to
upgrade the hardware to 64 bit in the future, you can purchase a 32-bit SKU
today, and later switch to 64 bit without having to
purchase an additional license.
</Excerpt>
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Frivas" <Frivas@.discussions.microsoft.com> wrote in message
news:E1927DBA-0E12-47D1-AC7C-2A132DFFC626@.microsoft.com...
> Hi, I want to upgrade a server from a 32 bit system to a 64 bit system,
> will
> i be able to use my same license with the new server or should i need to
> buy
> a new license for the 64 bit server?
> Thanks in advance for the help.
> Regards,
>

Migration data from SQL 7.0 to SQL 2005

I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
on to of the existing 7.0 instance and perfrom a full system upgrade. What I
don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
import the SQL 7.0 database and convert it for use inder 2005? I don't want
to burn my tracks by upgrdaing the existing server. If the install goes bad,
I can't fall back if nercessary. The books online for the lates preview don't
indicate the abaility migrate data fromj 7.0 as a stand alone process
sepparate from a full upgrade.
You should be able to detach the database from SQL Server 7.0 and attach it
to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
procedures. For more information about upgrading databases from previous
versions to SQL Server 2005, see SQL Server 2005 Books Online.
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> I know that sQL 2005 support upgrading a SQL 7.0 database if you install
it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
want
> to burn my tracks by upgrdaing the existing server. If the install goes
bad,
> I can't fall back if nercessary. The books online for the lates preview
don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.
|||I have read the books online and I don't get the impression that you can
either directly attach a 7.0 database or alternatively, use the "copy
database wizard". Attempts to directly attach a SQL 7.0 database have failed
when initiated by scripts generated using the new scripting wizard. The “copy
database wizard” clearly states in its opening text that it can only be used
when copying SQL 2000 or 2005 data. There is no mention of copying SQL 7.0
data at all.
The books online recommend not using “sp_attach_db” command since it will no
longer be supported in the future. They suggest using the “CREAT DATABASE”
command in its place which is what the script generated by the wizard used.
In eaither case, the action failed.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>
|||OK, I got it to work. For some reason, scheduling the script to run via the
agent causes it to fail when executed. However, when I copied the script to
the query analyzer and executed it from there, it worked correctly.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>
|||For additional help with upgrading to SQL Server 2005 from earlier versions
of SQL Server, you may be interested in the SQL Server 2005 Upgrade Advisor:
http://www.microsoft.com/downloads/d...DisplayLang=en
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
>I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> I can't fall back if nercessary. The books online for the lates preview
> don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.

Migration data from SQL 7.0 to SQL 2005

I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
on to of the existing 7.0 instance and perfrom a full system upgrade. What I
don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
import the SQL 7.0 database and convert it for use inder 2005? I don't want
to burn my tracks by upgrdaing the existing server. If the install goes bad,
I can't fall back if nercessary. The books online for the lates preview don't
indicate the abaility migrate data fromj 7.0 as a stand alone process
sepparate from a full upgrade.You should be able to detach the database from SQL Server 7.0 and attach it
to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
procedures. For more information about upgrading databases from previous
versions to SQL Server 2005, see SQL Server 2005 Books Online.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> I know that sQL 2005 support upgrading a SQL 7.0 database if you install
it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
want
> to burn my tracks by upgrdaing the existing server. If the install goes
bad,
> I can't fall back if nercessary. The books online for the lates preview
don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.|||I have read the books online and I don't get the impression that you can
either directly attach a 7.0 database or alternatively, use the "copy
database wizard". Attempts to directly attach a SQL 7.0 database have failed
when initiated by scripts generated using the new scripting wizard. The â'copy
database wizardâ' clearly states in its opening text that it can only be used
when copying SQL 2000 or 2005 data. There is no mention of copying SQL 7.0
data at all.
The books online recommend not using â'sp_attach_dbâ' command since it will no
longer be supported in the future. They suggest using the â'CREAT DATABASEâ'
command in its place which is what the script generated by the wizard used.
In eaither case, the action failed.
"Narayana Vyas Kondreddi" wrote:
> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> > I know that sQL 2005 support upgrading a SQL 7.0 database if you install
> it
> > on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> > don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> > import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> > to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> > I can't fall back if nercessary. The books online for the lates preview
> don't
> > indicate the abaility migrate data fromj 7.0 as a stand alone process
> > sepparate from a full upgrade.
>
>|||OK, I got it to work. For some reason, scheduling the script to run via the
agent causes it to fail when executed. However, when I copied the script to
the query analyzer and executed it from there, it worked correctly.
"Narayana Vyas Kondreddi" wrote:
> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> > I know that sQL 2005 support upgrading a SQL 7.0 database if you install
> it
> > on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> > don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> > import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> > to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> > I can't fall back if nercessary. The books online for the lates preview
> don't
> > indicate the abaility migrate data fromj 7.0 as a stand alone process
> > sepparate from a full upgrade.
>
>|||For additional help with upgrading to SQL Server 2005 from earlier versions
of SQL Server, you may be interested in the SQL Server 2005 Upgrade Advisor:
http://www.microsoft.com/downloads/details.aspx?FamilyID=cf28daf9-182e-4ac2-8e88-f2e936558bf2&DisplayLang=en
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
>I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> I can't fall back if nercessary. The books online for the lates preview
> don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.

Migration data from SQL 7.0 to SQL 2005

I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
on to of the existing 7.0 instance and perfrom a full system upgrade. What I
don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
import the SQL 7.0 database and convert it for use inder 2005? I don't want
to burn my tracks by upgrdaing the existing server. If the install goes bad,
I can't fall back if nercessary. The books online for the lates preview don'
t
indicate the abaility migrate data fromj 7.0 as a stand alone process
sepparate from a full upgrade.You should be able to detach the database from SQL Server 7.0 and attach it
to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
procedures. For more information about upgrading databases from previous
versions to SQL Server 2005, see SQL Server 2005 Books Online.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> I know that sQL 2005 support upgrading a SQL 7.0 database if you install
it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
want
> to burn my tracks by upgrdaing the existing server. If the install goes
bad,
> I can't fall back if nercessary. The books online for the lates preview
don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.|||I have read the books online and I don't get the impression that you can
either directly attach a 7.0 database or alternatively, use the "copy
database wizard". Attempts to directly attach a SQL 7.0 database have failed
when initiated by scripts generated using the new scripting wizard. The “c
opy
database wizard” clearly states in its opening text that it can only be us
ed
when copying SQL 2000 or 2005 data. There is no mention of copying SQL 7.0
data at all.
The books online recommend not using “sp_attach_db” command since it wil
l no
longer be supported in the future. They suggest using the “CREAT DATABASE
command in its place which is what the script generated by the wizard used.
In eaither case, the action failed.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach i
t
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>|||OK, I got it to work. For some reason, scheduling the script to run via the
agent causes it to fail when executed. However, when I copied the script to
the query analyzer and executed it from there, it worked correctly.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach i
t
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>|||For additional help with upgrading to SQL Server 2005 from earlier versions
of SQL Server, you may be interested in the SQL Server 2005 Upgrade Advisor:
http://www.microsoft.com/downloads/...&DisplayLang=en
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
>I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> I can't fall back if nercessary. The books online for the lates preview
> don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.

Migration ?

Hello,
I currently have a SQL 2000 SP3 STD running in my org, I want to move it's
contents to a clustered (two node) system running SQL 2005 STD edition. Is
it possible to move the entire contents of my old SQL environment to the new
environment? I would like to preserve user logins and the current instance
name of my old server. I know it might require me renaming the old SQL
server name when I get to that point. If someone could give me some tips on
how (or if it's even possible) to do this I would be highly greatful.
Thank you
Alex Anderson
You have to move the databases to the new server individually. Most of
these were written for 2000 but still apply to 2005.
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/featu...le.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/colu...rdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scri...tions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
news:2DF0B36D-5B38-4BE1-A448-91CE4F33F5B2@.microsoft.com...
> Hello,
> I currently have a SQL 2000 SP3 STD running in my org, I want to move it's
> contents to a clustered (two node) system running SQL 2005 STD edition.
> Is
> it possible to move the entire contents of my old SQL environment to the
> new
> environment? I would like to preserve user logins and the current
> instance
> name of my old server. I know it might require me renaming the old SQL
> server name when I get to that point. If someone could give me some tips
> on
> how (or if it's even possible) to do this I would be highly greatful.
> Thank you
> Alex Anderson
>
|||Actually, it can be done a bit more simply than that. You need to do the
following:
1. Configure the cluster
2. Install a SQL Server failover cluster instance
3. Backup the master database on your standalone and restore it to the
failover cluster instance
4. Backup msdb and restore it to the failover cluster instance
5. Move your databases using either a detach/attach or backup/restore
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:et0zGJSVGHA.6084@.TK2MSFTNGP14.phx.gbl...
> You have to move the databases to the new server individually. Most of
> these were written for 2000 but still apply to 2005.
> http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
> http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx
> Moving system dbs 2005
> http://www.databasejournal.com/featu...le.php/3379901
> Moving system DB's 2000
> http://www.support.microsoft.com/?id=314546 Moving DB's between
> Servers
> http://www.support.microsoft.com/?id=224071 Moving SQL Server
> Databases to a New Location with Detach/Attach
> http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a
> Restore
> http://www.sqlservercentral.com/colu...rdatabases.asp
> Moving Users
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs
> after a Restore
> http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 User Logon and/or
> Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 How to Resolve Permission
> Issues When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scri...p?scriptid=599
> Restoring a .mdf
> http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
> for SQL Server
> http://www.support.microsoft.com/?id=320125 Moving a Diagram
> http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
> http://www.sqlservercentral.com/scri...tions/1598.asp Script
> Roles and Permissions
> --
> Andrew J. Kelly SQL MVP
>
> "Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
> news:2DF0B36D-5B38-4BE1-A448-91CE4F33F5B2@.microsoft.com...
>
|||Michael,
Moving the Master and MSDB database, what if the old server where those
databases are coming from are different builds? Will a restore on the SQL
2005 cluster allow this?
Thank you
Alex Anderson
"Michael Hotek" wrote:

> Actually, it can be done a bit more simply than that. You need to do the
> following:
> 1. Configure the cluster
> 2. Install a SQL Server failover cluster instance
> 3. Backup the master database on your standalone and restore it to the
> failover cluster instance
> 4. Backup msdb and restore it to the failover cluster instance
> 5. Move your databases using either a detach/attach or backup/restore
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:et0zGJSVGHA.6084@.TK2MSFTNGP14.phx.gbl...
>
>
|||During a restore, all of the metadata is upgraded. So, yes, it does work.
You will obviously want to test it before doing it in production.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
news:0A3A75CF-166A-4BD7-88C9-1B55B519B9B7@.microsoft.com...[vbcol=seagreen]
> Michael,
> Moving the Master and MSDB database, what if the old server where those
> databases are coming from are different builds? Will a restore on the SQL
> 2005 cluster allow this?
> Thank you
> Alex Anderson
>
> "Michael Hotek" wrote:
|||Michael,
I've tried every way I can think of trying to restore the master database.
I fail every time because it's complaining about the build numbers being
different. Is there something I can need to check to override this?
Thank you
Alex Anderson
"Michael Hotek" wrote:

> During a restore, all of the metadata is upgraded. So, yes, it does work.
> You will obviously want to test it before doing it in production.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
> news:0A3A75CF-166A-4BD7-88C9-1B55B519B9B7@.microsoft.com...
>
>

Migrating to SQL Server from Versant

Can anyone point me to someone who could advise on migrating databases. I am
a system consultant (but not a database consultant or expert) and one of my
customers wants to convert their database from Versant to SQL server. The
Database is used to record customer information and includes the following
requirements. All data entered or changed must have a change history
recorded. Pictures will be save and linked to customers and the ability to
annotate the pictures is also required. The system will be used in various
locations worldwide.
Any help would be required.
thanks
George
George Adrian
All possible to do in SQL Server. I have no clue what Versant is, I've
never heard of it.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
> Can anyone point me to someone who could advise on migrating databases. I
> am
> a system consultant (but not a database consultant or expert) and one of
> my
> customers wants to convert their database from Versant to SQL server. The
> Database is used to record customer information and includes the following
> requirements. All data entered or changed must have a change history
> recorded. Pictures will be save and linked to customers and the ability to
> annotate the pictures is also required. The system will be used in various
> locations worldwide.
> Any help would be required.
> thanks
> George
> --
> George Adrian
|||The biggest issue is that since Versant is an Object Oriented database, you
will have to redesign the data model - Identity columns to replace
ObjectID's, Foreign Key columns to replace object references, etc. I would
recommend rethinking the data model completely to produce an efficient
relational model rather than trying to map their OO schema directly to a
relational schema.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:OKjSseSDGHA.2040@.TK2MSFTNGP14.phx.gbl...
> All possible to do in SQL Server. I have no clue what Versant is, I've
> never heard of it.
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
> news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
>