sql server (alternate): Hi there, we tried to restore a sql 7 DB to sql2000, somehow some of
the varchar filed become nvarchar, why is this?

thanks,

-sarah

YES I am!! I was indeed looking into a different database.
One quick follow up question, is there any tool that I can use to make
sure that the restored database is "completely" identicial? say,
premission, or data.

Thanks!!

-sarah

(sarahlin@yahoo.com) writes:
[quoted text, click to view]

Sounds like you are victim to a mirage. That does simply just not happen.
You may be mistaken about the source database. Or you are looking into
the wrong database on the target server.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at

(sarahlin@yahoo.com) writes:
[quoted text, click to view]

I guess Red Gate's SQL Compare could do the job. But I have not used
it myself, so I don't know how far it goes.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at

I use SQL Compare frequently. It is awesome. I do not know, however, if
you can compare SQL7 to SQL2000. That seems reasonable enough ;).

Hi Sarah Lin,

I would bet dollars to donuts that your data is identical. Permissions could
be complicated since they are stored by and id number not by name
(permissions to dchristo on Server1 are not going to translate to dchristo
on Server2).

I would be most concerned that the stored procedures and SQL Code used to
access your database continue to work as advertised. Particularly if any
column or table names in the SQL 7 database are now reserved words in SQL
2000. (I seem to recall having trouble with a column called "Level")

--
-Dick Christoph
[quoted text, click to view]