Hello All
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
Paul
That isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.com/sf_block_prevention.asp
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegro ups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>
|||You are absolutely right, I was being a dumb-XXX
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P
|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegrou ps.com...
> You are absolutely right, I was being a dumb-XXX
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>
sql
Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts
Wednesday, March 28, 2012
mirror db blocking issue
Hello All
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
PaulThat isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.com/sf_block_prevention.asp
--
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegroups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>|||You are absolutely right, I was being a dumb-ass
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
--
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegroups.com...
> You are absolutely right, I was being a dumb-ass
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
PaulThat isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.com/sf_block_prevention.asp
--
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegroups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>|||You are absolutely right, I was being a dumb-ass
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
--
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegroups.com...
> You are absolutely right, I was being a dumb-ass
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>
mirror db blocking issue
Hello All
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
PaulThat isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.c..._prevention.asp
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegroups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>|||You are absolutely right, I was being a dumb-XXX
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegroups.com...
> You are absolutely right, I was being a dumb-XXX
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
PaulThat isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.c..._prevention.asp
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegroups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>|||You are absolutely right, I was being a dumb-XXX
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegroups.com...
> You are absolutely right, I was being a dumb-XXX
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>
Monday, March 26, 2012
Mirror Backup
Hello All!
I have a very simple question.
Im studying for 40-431 and just finished reading about Log Shipping.
It says in the book that when using Log Shipping you cannot run any other log backups because that would affect the LSNs. Can one do log backups with mirroring - principle and mirror?
Because mirroring uses log to keep the mirror up-to-date and synchs on LSN.
Thank youof course,you can backup your log in mirror.mirror and log shipping work in different way.
thanks.
Friday, March 23, 2012
minimum role/permissions for backup
I have a MS SQL database process that is run from ASP.NET.
I would like to be able to backup the SQL database using either
a full database or transaction log backup immediately before the
process is done. Is this possible with ASP.NET and
what kind of permissions or role would the SQL connection account
need to perfom the backup. I would like to give the account the minimum
permissions needed.
Ed
--
EdThere is a built in SQL Server role called "db_backupoperator".
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:6EF64E64-B72C-4C84-9AD8-1F9B3072758A@.microsoft.com...
>I have a MS SQL database process that is run from ASP.NET.
> I would like to be able to backup the SQL database using either
> a full database or transaction log backup immediately before the
> process is done. Is this possible with ASP.NET and
> what kind of permissions or role would the SQL connection account
> need to perfom the backup. I would like to give the account the minimum
> permissions needed.
> --
> Ed
> --
> Ed
I would like to be able to backup the SQL database using either
a full database or transaction log backup immediately before the
process is done. Is this possible with ASP.NET and
what kind of permissions or role would the SQL connection account
need to perfom the backup. I would like to give the account the minimum
permissions needed.
Ed
--
EdThere is a built in SQL Server role called "db_backupoperator".
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:6EF64E64-B72C-4C84-9AD8-1F9B3072758A@.microsoft.com...
>I have a MS SQL database process that is run from ASP.NET.
> I would like to be able to backup the SQL database using either
> a full database or transaction log backup immediately before the
> process is done. Is this possible with ASP.NET and
> what kind of permissions or role would the SQL connection account
> need to perfom the backup. I would like to give the account the minimum
> permissions needed.
> --
> Ed
> --
> Ed
Monday, March 12, 2012
Migration: SQL Server 7.0 - SQL Server 2000
I have to migrate my SQL Server 7 databases to SQL Server 2000.
What I was planning to do was to restore my full 7.0 backup to my new SQL Server 2000 system. This looks to good to be
true so......... Is there a problem with this plan? What are the "gotchas"? What should I look-out for? Is there
a better way of doing this migration.
I've only been a DBA for about a year so I can definitely use all the help I can get. Any ideas, help, suggestions are
greatly appreciated.
tx.
cathy
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> What I was planning to do was to restore my full 7.0 backup to my new SQL
Server 2000 system. This looks to good to be
> true so......... Is there a problem with this plan? What are the
"gotchas"? What should I look-out for? Is there
> a better way of doing this migration.
That's an excellent way to perform your upgrade.
> I've only been a DBA for about a year so I can definitely use all the help
I can get. Any ideas, help, suggestions are
> greatly appreciated.
Planning is a key part of any DBA's job, so you are on target. If you have
not seen the following links, have a read ;)
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
Upgrading an Existing Installation of SQL Server
http://msdn.microsoft.com/library/de...rview_2xtf.asp
Steve
|||... and some other links that might be useful:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
> news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> Server 2000 system. This looks to good to be
> "gotchas"? What should I look-out for? Is there
> That's an excellent way to perform your upgrade.
> I can get. Any ideas, help, suggestions are
> Planning is a key part of any DBA's job, so you are on target. If you have
> not seen the following links, have a read ;)
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
> Upgrading an Existing Installation of SQL Server
> http://msdn.microsoft.com/library/de...rview_2xtf.asp
> Steve
>
|||Thanks Steve & Tibor. The links are definitely helpful. I always get a
case of the "warm fuzzies" when I have someone with lots of experience
validating my decisions & plans.
cathy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uVdec5XpEHA.516@.TK2MSFTNGP09.phx.gbl...
> ... and some other links that might be useful:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers[vbcol=seagreen]
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
message[vbcol=seagreen]
SQL[vbcol=seagreen]
help[vbcol=seagreen]
have[vbcol=seagreen]
http://www.microsoft.com/technet/pro...y/sqlugrd.mspx[vbcol=seagreen]
http://msdn.microsoft.com/library/de...rview_2xtf.asp
>
What I was planning to do was to restore my full 7.0 backup to my new SQL Server 2000 system. This looks to good to be
true so......... Is there a problem with this plan? What are the "gotchas"? What should I look-out for? Is there
a better way of doing this migration.
I've only been a DBA for about a year so I can definitely use all the help I can get. Any ideas, help, suggestions are
greatly appreciated.
tx.
cathy
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> What I was planning to do was to restore my full 7.0 backup to my new SQL
Server 2000 system. This looks to good to be
> true so......... Is there a problem with this plan? What are the
"gotchas"? What should I look-out for? Is there
> a better way of doing this migration.
That's an excellent way to perform your upgrade.
> I've only been a DBA for about a year so I can definitely use all the help
I can get. Any ideas, help, suggestions are
> greatly appreciated.
Planning is a key part of any DBA's job, so you are on target. If you have
not seen the following links, have a read ;)
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
Upgrading an Existing Installation of SQL Server
http://msdn.microsoft.com/library/de...rview_2xtf.asp
Steve
|||... and some other links that might be useful:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
> news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> Server 2000 system. This looks to good to be
> "gotchas"? What should I look-out for? Is there
> That's an excellent way to perform your upgrade.
> I can get. Any ideas, help, suggestions are
> Planning is a key part of any DBA's job, so you are on target. If you have
> not seen the following links, have a read ;)
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
> Upgrading an Existing Installation of SQL Server
> http://msdn.microsoft.com/library/de...rview_2xtf.asp
> Steve
>
|||Thanks Steve & Tibor. The links are definitely helpful. I always get a
case of the "warm fuzzies" when I have someone with lots of experience
validating my decisions & plans.
cathy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uVdec5XpEHA.516@.TK2MSFTNGP09.phx.gbl...
> ... and some other links that might be useful:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers[vbcol=seagreen]
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
message[vbcol=seagreen]
SQL[vbcol=seagreen]
help[vbcol=seagreen]
have[vbcol=seagreen]
http://www.microsoft.com/technet/pro...y/sqlugrd.mspx[vbcol=seagreen]
http://msdn.microsoft.com/library/de...rview_2xtf.asp
>
Migration: SQL Server 7.0 - SQL Server 2000
I have to migrate my SQL Server 7 databases to SQL Server 2000.
What I was planning to do was to restore my full 7.0 backup to my new SQL Server 2000 system. This looks to good to be
true so......... Is there a problem with this plan? What are the "gotchas"? What should I look-out for? Is there
a better way of doing this migration.
I've only been a DBA for about a year so I can definitely use all the help I can get. Any ideas, help, suggestions are
greatly appreciated.
tx.
cathy"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> What I was planning to do was to restore my full 7.0 backup to my new SQL
Server 2000 system. This looks to good to be
> true so......... Is there a problem with this plan? What are the
"gotchas"? What should I look-out for? Is there
> a better way of doing this migration.
That's an excellent way to perform your upgrade.
> I've only been a DBA for about a year so I can definitely use all the help
I can get. Any ideas, help, suggestions are
> greatly appreciated.
Planning is a key part of any DBA's job, so you are on target. If you have
not seen the following links, have a read ;)
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
Upgrading an Existing Installation of SQL Server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
Steve|||... and some other links that might be useful:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
> news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
>> I have to migrate my SQL Server 7 databases to SQL Server 2000.
>> What I was planning to do was to restore my full 7.0 backup to my new SQL
> Server 2000 system. This looks to good to be
>> true so......... Is there a problem with this plan? What are the
> "gotchas"? What should I look-out for? Is there
>> a better way of doing this migration.
> That's an excellent way to perform your upgrade.
>> I've only been a DBA for about a year so I can definitely use all the help
> I can get. Any ideas, help, suggestions are
>> greatly appreciated.
> Planning is a key part of any DBA's job, so you are on target. If you have
> not seen the following links, have a read ;)
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
> Upgrading an Existing Installation of SQL Server
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
> Steve
>|||Thanks Steve & Tibor. The links are definitely helpful. I always get a
case of the "warm fuzzies" when I have someone with lots of experience
validating my decisions & plans.
cathy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uVdec5XpEHA.516@.TK2MSFTNGP09.phx.gbl...
> ... and some other links that might be useful:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> > news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> >> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> >> What I was planning to do was to restore my full 7.0 backup to my new
SQL
> > Server 2000 system. This looks to good to be
> >> true so......... Is there a problem with this plan? What are the
> > "gotchas"? What should I look-out for? Is there
> >> a better way of doing this migration.
> >
> > That's an excellent way to perform your upgrade.
> >
> >> I've only been a DBA for about a year so I can definitely use all the
help
> > I can get. Any ideas, help, suggestions are
> >> greatly appreciated.
> >
> > Planning is a key part of any DBA's job, so you are on target. If you
have
> > not seen the following links, have a read ;)
> >
> > How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> >
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
> >
> > Upgrading an Existing Installation of SQL Server
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
> >
> > Steve
> >
> >
>
What I was planning to do was to restore my full 7.0 backup to my new SQL Server 2000 system. This looks to good to be
true so......... Is there a problem with this plan? What are the "gotchas"? What should I look-out for? Is there
a better way of doing this migration.
I've only been a DBA for about a year so I can definitely use all the help I can get. Any ideas, help, suggestions are
greatly appreciated.
tx.
cathy"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> What I was planning to do was to restore my full 7.0 backup to my new SQL
Server 2000 system. This looks to good to be
> true so......... Is there a problem with this plan? What are the
"gotchas"? What should I look-out for? Is there
> a better way of doing this migration.
That's an excellent way to perform your upgrade.
> I've only been a DBA for about a year so I can definitely use all the help
I can get. Any ideas, help, suggestions are
> greatly appreciated.
Planning is a key part of any DBA's job, so you are on target. If you have
not seen the following links, have a read ;)
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
Upgrading an Existing Installation of SQL Server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
Steve|||... and some other links that might be useful:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
> news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
>> I have to migrate my SQL Server 7 databases to SQL Server 2000.
>> What I was planning to do was to restore my full 7.0 backup to my new SQL
> Server 2000 system. This looks to good to be
>> true so......... Is there a problem with this plan? What are the
> "gotchas"? What should I look-out for? Is there
>> a better way of doing this migration.
> That's an excellent way to perform your upgrade.
>> I've only been a DBA for about a year so I can definitely use all the help
> I can get. Any ideas, help, suggestions are
>> greatly appreciated.
> Planning is a key part of any DBA's job, so you are on target. If you have
> not seen the following links, have a read ;)
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
> Upgrading an Existing Installation of SQL Server
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
> Steve
>|||Thanks Steve & Tibor. The links are definitely helpful. I always get a
case of the "warm fuzzies" when I have someone with lots of experience
validating my decisions & plans.
cathy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uVdec5XpEHA.516@.TK2MSFTNGP09.phx.gbl...
> ... and some other links that might be useful:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> > news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> >> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> >> What I was planning to do was to restore my full 7.0 backup to my new
SQL
> > Server 2000 system. This looks to good to be
> >> true so......... Is there a problem with this plan? What are the
> > "gotchas"? What should I look-out for? Is there
> >> a better way of doing this migration.
> >
> > That's an excellent way to perform your upgrade.
> >
> >> I've only been a DBA for about a year so I can definitely use all the
help
> > I can get. Any ideas, help, suggestions are
> >> greatly appreciated.
> >
> > Planning is a key part of any DBA's job, so you are on target. If you
have
> > not seen the following links, have a read ;)
> >
> > How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> >
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
> >
> > Upgrading an Existing Installation of SQL Server
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
> >
> > Steve
> >
> >
>
Saturday, February 25, 2012
Migration from 7 to 2000
Hello,
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
Arto Ylikotila arto.ylikotila@.santamargarita.fiThere is always a possibility, but it is unlikely that you need to do any si
gnificant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converte
d the constant side to the column
side. Today, SQL Server does the conversions according to the documented "da
tatype precedence" in Books
Online.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books[vbcol=seagreen]
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...|||Hi,
SQL 7.0 Backups are fully compatible with SQL 2000.
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends
MDAC versions > 2.6x.
We had several problems with clients that has mdac versions < 2.6x (speciall
y sql servers with multiple instances and also have some localization probl
ems).
Regards..
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
Arto Ylikotila arto.ylikotila@.santamargarita.fiThere is always a possibility, but it is unlikely that you need to do any si
gnificant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converte
d the constant side to the column
side. Today, SQL Server does the conversions according to the documented "da
tatype precedence" in Books
Online.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books[vbcol=seagreen]
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...|||Hi,
SQL 7.0 Backups are fully compatible with SQL 2000.
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends
MDAC versions > 2.6x.
We had several problems with clients that has mdac versions < 2.6x (speciall
y sql servers with multiple instances and also have some localization probl
ems).
Regards..
Migration from 7 to 2000
Hello,
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
Arto Ylikotila arto.ylikotila@.santamargarita.fi
There is always a possibility, but it is unlikely that you need to do any significant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converted the constant side to the column
side. Today, SQL Server does the conversions according to the documented "datatype precedence" in Books
Online.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>
|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books[vbcol=seagreen]
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
|||Hi,
SQL 7.0 Backups are fully compatible with SQL 2000.
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends MDAC versions > 2.6x.
We had several problems with clients that has mdac versions < 2.6x (specially sql servers with multiple instances and also have some localization problems).
Regards..
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
Arto Ylikotila arto.ylikotila@.santamargarita.fi
There is always a possibility, but it is unlikely that you need to do any significant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converted the constant side to the column
side. Today, SQL Server does the conversions according to the documented "datatype precedence" in Books
Online.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>
|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books[vbcol=seagreen]
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
|||Hi,
SQL 7.0 Backups are fully compatible with SQL 2000.
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends MDAC versions > 2.6x.
We had several problems with clients that has mdac versions < 2.6x (specially sql servers with multiple instances and also have some localization problems).
Regards..
Migration from 7 to 2000
Hello,
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
--
Arto Ylikotila arto.ylikotila@.santamargarita.fiThere is always a possibility, but it is unlikely that you need to do any significant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converted the constant side to the column
side. Today, SQL Server does the conversions according to the documented "datatype precedence" in Books
Online.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > How compatible is database Backup from MSSQL 7 to 2000?
> > Database has a lot of Procedures. Can there be syntax Problems?
> >
> > Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)|||Hi
SQL 7.0 Backups are fully compatible with SQL 2000
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends MDAC versions > 2.6x
We had several problems with clients that has mdac versions < 2.6x (specially sql servers with multiple instances and also have some localization problems)
Regards.
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
--
Arto Ylikotila arto.ylikotila@.santamargarita.fiThere is always a possibility, but it is unlikely that you need to do any significant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converted the constant side to the column
side. Today, SQL Server does the conversions according to the documented "datatype precedence" in Books
Online.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > How compatible is database Backup from MSSQL 7 to 2000?
> > Database has a lot of Procedures. Can there be syntax Problems?
> >
> > Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)|||Hi
SQL 7.0 Backups are fully compatible with SQL 2000
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends MDAC versions > 2.6x
We had several problems with clients that has mdac versions < 2.6x (specially sql servers with multiple instances and also have some localization problems)
Regards.
Migration 2005 beta to 2005 release
Hi Group,
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.com...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.
> Cheers,
> Stewart
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.com...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.
> Cheers,
> Stewart
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>
Migration 2005 beta to 2005 release
Hi Group,
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart
"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.c om...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.
> Cheers,
> Stewart
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart
"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.c om...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.
> Cheers,
> Stewart
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>
Migration 2005 beta to 2005 release
Hi Group,
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.com...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.
> Cheers,
> Stewart
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.com...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.
> Cheers,
> Stewart
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>
Migrating VS 2003 -> 2005
Hello all,
I'd like to upgrade VS and also SQL server with RS. I just want make
sure, if I backup all databases, uninstall SQL2000, install SQL2005,
install VS 2005 with RS - if everything will be OK.
I tried to find how to proper upgrade RS2000 to RS2005, but I dont
find anything, and I just want to be sure...
Thanks for any help!Actually you don't have to uninstall your 2000, when your run 2005 Setup on
the computer hosting the report server. it detects your existing 2000 server
and provides you with the options to upgrade.
But it's more than a good idea to backup everything before processing
Have also a look to this
http://msdn2.microsoft.com/en-us/library/ms143747(en-us,SQL.90).aspx
Med Bouchenafa
"Brano" <2ge@.2NOgeSPAM.us> wrote in message
news:27981190.20051223134023@.ble.com...
> Hello all,
> I'd like to upgrade VS and also SQL server with RS. I just want make
> sure, if I backup all databases, uninstall SQL2000, install SQL2005,
> install VS 2005 with RS - if everything will be OK.
> I tried to find how to proper upgrade RS2000 to RS2005, but I dont
> find anything, and I just want to be sure...
> Thanks for any help!
>|||Hello Med,
Friday, December 23, 2005, 3:23:44 PM, you wrote:
> Actually you don't have to uninstall your 2000, when your run 2005 Setup on
> the computer hosting the report server. it detects your existing 2000 server
> and provides you with the options to upgrade.
> But it's more than a good idea to backup everything before processing
> Have also a look to this
> http://msdn2.microsoft.com/en-us/library/ms143747(en-us,SQL.90).aspx
thanks very much for answer! I wish you everything you like :)
--
Best regards,
Brano mailto:2ge@.2NOgeSPAM.us
I'd like to upgrade VS and also SQL server with RS. I just want make
sure, if I backup all databases, uninstall SQL2000, install SQL2005,
install VS 2005 with RS - if everything will be OK.
I tried to find how to proper upgrade RS2000 to RS2005, but I dont
find anything, and I just want to be sure...
Thanks for any help!Actually you don't have to uninstall your 2000, when your run 2005 Setup on
the computer hosting the report server. it detects your existing 2000 server
and provides you with the options to upgrade.
But it's more than a good idea to backup everything before processing
Have also a look to this
http://msdn2.microsoft.com/en-us/library/ms143747(en-us,SQL.90).aspx
Med Bouchenafa
"Brano" <2ge@.2NOgeSPAM.us> wrote in message
news:27981190.20051223134023@.ble.com...
> Hello all,
> I'd like to upgrade VS and also SQL server with RS. I just want make
> sure, if I backup all databases, uninstall SQL2000, install SQL2005,
> install VS 2005 with RS - if everything will be OK.
> I tried to find how to proper upgrade RS2000 to RS2005, but I dont
> find anything, and I just want to be sure...
> Thanks for any help!
>|||Hello Med,
Friday, December 23, 2005, 3:23:44 PM, you wrote:
> Actually you don't have to uninstall your 2000, when your run 2005 Setup on
> the computer hosting the report server. it detects your existing 2000 server
> and provides you with the options to upgrade.
> But it's more than a good idea to backup everything before processing
> Have also a look to this
> http://msdn2.microsoft.com/en-us/library/ms143747(en-us,SQL.90).aspx
thanks very much for answer! I wish you everything you like :)
--
Best regards,
Brano mailto:2ge@.2NOgeSPAM.us
Monday, February 20, 2012
migrating to 2005 troubles :(
hey guys
just to do a test run i wanted to migrate the northwind database from
2000 to 2005
when i do a backup and try to restore on the new machine ... i receive
this message
i know its probably something trivial ... but can anyone give me a
hand with this ?
TITLE: Microsoft SQL Server Management Studio
Restore failed for Server 'NAMECLapps\ins1'.
(Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Restore+Server&LinkId=20476[/url]
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
for clustered server. Only formatted files on which the cluster
resource of the server has a dependency can be used.
(Microsoft.SqlServer.Smo)
For help, click: [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&LinkId=20476[/url]
You can't put a user db on the local drive of a cluster. It must be one of
the drives in the cluster resource group.
Andrew J. Kelly SQL MVP
<glombica@.hotmail.com> wrote in message
news:1185286074.533480.16750@.m3g2000hsh.googlegrou ps.com...
> hey guys
> just to do a test run i wanted to migrate the northwind database from
> 2000 to 2005
> when i do a backup and try to restore on the new machine ... i receive
> this message
> i know its probably something trivial ... but can anyone give me a
> hand with this ?
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'NAMECLapps\ins1'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Restore+Server&LinkId=20476[/url]
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
> for clustered server. Only formatted files on which the cluster
> resource of the server has a dependency can be used.
> (Microsoft.SqlServer.Smo)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&LinkId=20476[/url]
>
just to do a test run i wanted to migrate the northwind database from
2000 to 2005
when i do a backup and try to restore on the new machine ... i receive
this message
i know its probably something trivial ... but can anyone give me a
hand with this ?
TITLE: Microsoft SQL Server Management Studio
Restore failed for Server 'NAMECLapps\ins1'.
(Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Restore+Server&LinkId=20476[/url]
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
for clustered server. Only formatted files on which the cluster
resource of the server has a dependency can be used.
(Microsoft.SqlServer.Smo)
For help, click: [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&LinkId=20476[/url]
You can't put a user db on the local drive of a cluster. It must be one of
the drives in the cluster resource group.
Andrew J. Kelly SQL MVP
<glombica@.hotmail.com> wrote in message
news:1185286074.533480.16750@.m3g2000hsh.googlegrou ps.com...
> hey guys
> just to do a test run i wanted to migrate the northwind database from
> 2000 to 2005
> when i do a backup and try to restore on the new machine ... i receive
> this message
> i know its probably something trivial ... but can anyone give me a
> hand with this ?
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'NAMECLapps\ins1'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Restore+Server&LinkId=20476[/url]
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
> for clustered server. Only formatted files on which the cluster
> resource of the server has a dependency can be used.
> (Microsoft.SqlServer.Smo)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&LinkId=20476[/url]
>
migrating to 2005 troubles :(
hey guys
just to do a test run i wanted to migrate the northwind database from
2000 to 2005
when i do a backup and try to restore on the new machine ... i receive
this message
i know its probably something trivial ... but can anyone give me a
hand with this ?
TITLE: Microsoft SQL Server Management Studio
--
Restore failed for Server 'NAMECLapps\ins1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
--
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
for clustered server. Only formatted files on which the cluster
resource of the server has a dependency can be used.
(Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476You can't put a user db on the local drive of a cluster. It must be one of
the drives in the cluster resource group.
--
Andrew J. Kelly SQL MVP
<glombica@.hotmail.com> wrote in message
news:1185286074.533480.16750@.m3g2000hsh.googlegroups.com...
> hey guys
> just to do a test run i wanted to migrate the northwind database from
> 2000 to 2005
> when i do a backup and try to restore on the new machine ... i receive
> this message
> i know its probably something trivial ... but can anyone give me a
> hand with this ?
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'NAMECLapps\ins1'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
> for clustered server. Only formatted files on which the cluster
> resource of the server has a dependency can be used.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476
>
just to do a test run i wanted to migrate the northwind database from
2000 to 2005
when i do a backup and try to restore on the new machine ... i receive
this message
i know its probably something trivial ... but can anyone give me a
hand with this ?
TITLE: Microsoft SQL Server Management Studio
--
Restore failed for Server 'NAMECLapps\ins1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
--
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
for clustered server. Only formatted files on which the cluster
resource of the server has a dependency can be used.
(Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476You can't put a user db on the local drive of a cluster. It must be one of
the drives in the cluster resource group.
--
Andrew J. Kelly SQL MVP
<glombica@.hotmail.com> wrote in message
news:1185286074.533480.16750@.m3g2000hsh.googlegroups.com...
> hey guys
> just to do a test run i wanted to migrate the northwind database from
> 2000 to 2005
> when i do a backup and try to restore on the new machine ... i receive
> this message
> i know its probably something trivial ... but can anyone give me a
> hand with this ?
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'NAMECLapps\ins1'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
> for clustered server. Only formatted files on which the cluster
> resource of the server has a dependency can be used.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476
>
migrating to 2005 troubles :(
hey guys
just to do a test run i wanted to migrate the northwind database from
2000 to 2005
when i do a backup and try to restore on the new machine ... i receive
this message
i know its probably something trivial ... but can anyone give me a
hand with this ?
TITLE: Microsoft SQL Server Management Studio
--
Restore failed for Server 'NAMECLapps\ins1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
for clustered server. Only formatted files on which the cluster
resource of the server has a dependency can be used.
(Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?Prod...00&LinkId=20476You can't put a user db on the local drive of a cluster. It must be one of
the drives in the cluster resource group.
Andrew J. Kelly SQL MVP
<glombica@.hotmail.com> wrote in message
news:1185286074.533480.16750@.m3g2000hsh.googlegroups.com...
> hey guys
> just to do a test run i wanted to migrate the northwind database from
> 2000 to 2005
> when i do a backup and try to restore on the new machine ... i receive
> this message
> i know its probably something trivial ... but can anyone give me a
> hand with this ?
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'NAMECLapps\ins1'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
> for clustered server. Only formatted files on which the cluster
> resource of the server has a dependency can be used.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...
0&LinkId=20476
>
just to do a test run i wanted to migrate the northwind database from
2000 to 2005
when i do a backup and try to restore on the new machine ... i receive
this message
i know its probably something trivial ... but can anyone give me a
hand with this ?
TITLE: Microsoft SQL Server Management Studio
--
Restore failed for Server 'NAMECLapps\ins1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
for clustered server. Only formatted files on which the cluster
resource of the server has a dependency can be used.
(Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?Prod...00&LinkId=20476You can't put a user db on the local drive of a cluster. It must be one of
the drives in the cluster resource group.
Andrew J. Kelly SQL MVP
<glombica@.hotmail.com> wrote in message
news:1185286074.533480.16750@.m3g2000hsh.googlegroups.com...
> hey guys
> just to do a test run i wanted to migrate the northwind database from
> 2000 to 2005
> when i do a backup and try to restore on the new machine ... i receive
> this message
> i know its probably something trivial ... but can anyone give me a
> hand with this ?
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'NAMECLapps\ins1'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: Cannot use file 'C:\test\northwnd.mdf'
> for clustered server. Only formatted files on which the cluster
> resource of the server has a dependency can be used.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...
0&LinkId=20476
>
Subscribe to:
Posts (Atom)