Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Attach Databse vs Upgrade

Status
Not open for further replies.

omeryesil

Programmer
Jun 26, 2000
27
CA
Hi,
We use SQL Server 7.0 and we want to upgrade SQL 2000.
Now, there are 5 databases on the SQL 7.0

We have just realized that there is an 'Attach Database' functionality in SQL
2000.

In this case;
when we attach to SQL 2000 our SQL 7.0 databases , will there occur any problem
in future?

Does it provide for SQL backward compatibility ?
Or
What are differences between attaching Database and running SQL upgrade version ?

I mean, will it be the same with upgrading? If not, could you figure out main
differences?..

Thanks..


Omer YESIL
Visual C++, SQL, TCP/IP, Delphi, Pascal, Assembler, 3D Studio Max.
 
The attach/detach database capability exists in SQL 7 also.

You can attach a SQL 7 databse to SQL 2000 but once done it is not backward compatible. That is, you cannot attach the SQL 2000 database file to SQL 7. SQL 2000 changes the file format slightly.

You could probably get away with attaching but we recently upgraded a server to SQL 2000. The upgrade was quick and painless. We will make the same choice as we upgrade our other servers.

Check this Microsoft article for more info.

INF: Frequently Asked Questions - SQL Server 2000 - Upgrade

You can also get more info in SQL Books Online. See the following topics.

Upgrading from SQL Server 7.0 to SQL Server 2000
Upgrading Databases from SQL Server 7.0 (Copy Database Wizard)
Upgrading an Existing Installation of SQL Server
Terry

The reason why worry kills more people than work is that more people worry than work. - Robert Frost
 
Hi,

Following on from this I recentlt had the pleasure of installing a new application which used a VB front end and SQL2000 backend. However the backend was developed using a developer edition of SQL Server 7.0, I attached the developer pc to the network, registered the SQL7 server into the SQL2000 server group and started the Copy Database Wizard thinking this to be a good simple tool.

Did it work? NO!!!!!!!!!!

It kept coming up with the error - "....check you have permission to copy over the network". I then went shopping and bought a book on SQL2000 which wen the process and recommended setting one server as a Master and the other as a Target, but when I tried this I got the response "You are using a Developer edition, this edition can't be assigned as a target".

I ended up manually copying over the Tables into a new database, recreating the Views and Indexes. Long way round but never mind. I did however have more problems setting up the relationships, kept coming up with cyclic errors. Why should SQL2000 give this error when SQL7.0 didn't?

Can anyone offer any advice about what I could have done instead?

CID8
 
Hi i have got a big problem to export a sql table to a text file.
SQL server automaticaly cut the field at the 255 th character. My field has 2000!

I didn´t find a way to set this.

Thanks

Romain
 
Romain,

Please post your question in a new thread . The question is not related to the topic of this thread. When you post it, please tell us the version of SQL Server you use and the method used to export. Are you using DTS, BCP or something else? Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top