|
|
You're in the
sql server new users
group:Copying Database from sql 2005 to sql 2000
sql server new users:
Did my development work in sql 2005 -- neat works great Gotta put it into a sql 2000 instance for deployment. --- sql 2005 -- Database Properties -- Compatibility level set to SQL Server 2000 (80) detached the database copied the files into the data directory for SQL 2000 instance tried to attached files --> error's ----------------------Please what is the proper method to do this--- please be patient, I'm new to the SQL server family. Ed Warren.
You can't go backwards in versions. You can go from 2000 to 2005 but not the
other way around. This is true of most any software. You can't expect an older version of something to know about new features and such that were developed later on. You should not develop on a newer version of SQL Server if you have to support an older one. But to get you going you might try scripting the db and running that script on the 2000 box. If you have any data you will have to deal with that separately. When you generate the script you need to right click on the db in SSMS and choose "Tasks - Generate Scripts". And then in the script options tab of that dialog make sure you select SQL Server 2000 in the "Script for Server Version" property. -- Andrew J. Kelly SQL MVP [quoted text, click to view] "Ed Warren" <eowarren@fakeaddress.zzz> wrote in message news:ecJh%23ioBGHA.312@TK2MSFTNGP09.phx.gbl... > Got myself into a box!! > Did my development work in sql 2005 -- neat works great > Gotta put it into a sql 2000 instance for deployment. > > --- sql 2005 -- Database Properties -- Compatibility level set to SQL > Server 2000 (80) > detached the database > copied the files into the data directory for SQL 2000 instance > tried to attached files --> error's > > ----------------------Please what is the proper method to do this--- > please be patient, I'm new to the SQL server family. > > Ed Warren. >
Hi
No, you can't do that. The file format has changed a bit between SQL server 2000 and 2005, 2000 does not understand it anymore. It does not matter the compatibility level, the engine just behaves differently. You need to scripts your objects and run the script against a clean SQL Server 2000 database. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike@epprecht.net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ [quoted text, click to view] "Ed Warren" <eowarren@fakeaddress.zzz> wrote in message news:ecJh%23ioBGHA.312@TK2MSFTNGP09.phx.gbl... > Got myself into a box!! > Did my development work in sql 2005 -- neat works great > Gotta put it into a sql 2000 instance for deployment. > > --- sql 2005 -- Database Properties -- Compatibility level set to SQL > Server 2000 (80) > detached the database > copied the files into the data directory for SQL 2000 instance > tried to attached files --> error's > > ----------------------Please what is the proper method to do this--- > please be patient, I'm new to the SQL server family. > > Ed Warren. >
Thanks for the advice, as I said in the orginial post, I'm boxed in. Maybe,
just maybe, I can convince the administrator that the world won't end if we run an instance of SQL 2005 on the same server as SQL 2000. Again, Thanks Ed Warren. [quoted text, click to view] "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:OdCDs0oBGHA.2664@TK2MSFTNGP15.phx.gbl... > You can't go backwards in versions. You can go from 2000 to 2005 but not > the other way around. This is true of most any software. You can't expect > an older version of something to know about new features and such that > were developed later on. You should not develop on a newer version of SQL > Server if you have to support an older one. But to get you going you might > try scripting the db and running that script on the 2000 box. If you have > any data you will have to deal with that separately. When you generate > the script you need to right click on the db in SSMS and choose "Tasks - > Generate Scripts". And then in the script options tab of that dialog make > sure you select SQL Server 2000 in the "Script for Server Version" > property. > > -- > Andrew J. Kelly SQL MVP > > > "Ed Warren" <eowarren@fakeaddress.zzz> wrote in message > news:ecJh%23ioBGHA.312@TK2MSFTNGP09.phx.gbl... >> Got myself into a box!! >> Did my development work in sql 2005 -- neat works great >> Gotta put it into a sql 2000 instance for deployment. >> >> --- sql 2005 -- Database Properties -- Compatibility level set to SQL >> Server 2000 (80) >> detached the database >> copied the files into the data directory for SQL 2000 instance >> tried to attached files --> error's >> >> ----------------------Please what is the proper method to do this--- >> please be patient, I'm new to the SQL server family. >> >> Ed Warren. >> > >
With due respect, as an operational administrator, I would prefer to keep
the production installations clean. Just as you CAN upgrade the OS or upgrade a SQL Server installation, the preference would be to install on a clean server with a fresh build. Servers tend to accumulate "dust" that needs to be flushed out occasionally. I would recommend the same advice if a production system had been in service for 3 to 5 years or more: build a new system and switch them out just to clean out the garbage. Databases themselves tend to accumulate this "garbage" over time as well; although, cleaning out a production operational database would be much more complicated. As for your predicament, as in our shop, the anticipation of a new release always brings some hardship. I would recommend to your administrator that he/she can not stand in the way of technological change and to anticipate the future. In this case, get a production quality 2005 installation into place ASAP. The world would certainly not wait for your administrator to "finally" build such an installation. As you've indicated, third-party vendors as well as many internal developers are already making the switch. The Data Center will have to make these accommodations sooner or later. My advice for you would be to have two separate test/development environments, one for each production version platform that you support. In the test/dev environment, it would be possible to run just such a side-by-side installation that you suggested; however, I would never run such a creation in a production environment. It is unreasonable for you to expect as much from your administrator. Those side-by-side solutions are usually there to support migration efforts but rarely work out well for long-term support. Sincerely, Anthony Thomas -- [quoted text, click to view] "Ed Warren" <eowarren@fakeaddress.zzz> wrote in message news:%235Nt30tBGHA.3064@TK2MSFTNGP10.phx.gbl... > Thanks for the advice, as I said in the orginial post, I'm boxed in. Maybe, > just maybe, I can convince the administrator that the world won't end if we > run an instance of SQL 2005 on the same server as SQL 2000. > > Again, Thanks > Ed Warren. > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:OdCDs0oBGHA.2664@TK2MSFTNGP15.phx.gbl... > > You can't go backwards in versions. You can go from 2000 to 2005 but not > > the other way around. This is true of most any software. You can't expect > > an older version of something to know about new features and such that > > were developed later on. You should not develop on a newer version of SQL > > Server if you have to support an older one. But to get you going you might > > try scripting the db and running that script on the 2000 box. If you have > > any data you will have to deal with that separately. When you generate > > the script you need to right click on the db in SSMS and choose "Tasks - > > Generate Scripts". And then in the script options tab of that dialog make > > sure you select SQL Server 2000 in the "Script for Server Version" > > property. > > > > -- > > Andrew J. Kelly SQL MVP > > > > > > "Ed Warren" <eowarren@fakeaddress.zzz> wrote in message > > news:ecJh%23ioBGHA.312@TK2MSFTNGP09.phx.gbl... > >> Got myself into a box!! > >> Did my development work in sql 2005 -- neat works great > >> Gotta put it into a sql 2000 instance for deployment. > >> > >> --- sql 2005 -- Database Properties -- Compatibility level set to SQL > >> Server 2000 (80) > >> detached the database > >> copied the files into the data directory for SQL 2000 instance > >> tried to attached files --> error's > >> > >> ----------------------Please what is the proper method to do this--- > >> please be patient, I'm new to the SQL server family. > >> > >> Ed Warren. > >> > > > > > >
Don't see what you're looking for? Try a search.
|
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |