Hi guys,
(A repost from sqlserver NG, since I got no answer there)
I just installed MSDE2000 (SQLServer Desktop 2000) on XP Professional.
All seems to run Ok.
With MSDE and SQLserver 7 I used to be able to place a database from one
of my customers in the data directory of sqlserver and the server would
see that DB (seen e.g. by the enterprise mgr or while adding an ODBC
connection to that DB).
But now with the 2000 version, when adding a full DB to the data
directory, it is not seen by the odbc wizard. All I see is the master
DB, etc. When I use a front-end tool to MSDE like QALite, that also does
not recognise the added DB.
has something changed with the 2000 version?
The only change I noticed was that I needed a trusted connection to the
Db, instead of the "sa, NULL" I was able to do with sqlserver7. And I
think the customers DB is expecting the "sa,NULL" approach.

Hi Peter,

According to your description, I am not sure what the problem is. I would
like you to provide more information so that I can narrow down this issue.

1. What is the version of SQL Server on your customer's machine?
2. How do you move the database from your customer to your side,
detach/attach or Backup/restore?

When we migrate a database of SQL Server 7.0 to the instance of SQL Server
2000, we are unable to place a database in the database directory of SQL
Server 2000 directly.

For additional information regarding this issue, please refer to the
following article below:

This article addresses the frequently asked questions about the conversion
of a Microsoft SQL Server 7.0 or Microsoft SQL Server 6.5 installation to
Microsoft SQL Server 2000, version 8.0.
261334 INF: Frequently Asked Questions - SQL Server 2000 - Upgrade
http://support.microsoft.com/?id=261334

This article describes how to change the location of the data and log files
for any SQL Server 7.0 or SQL Server 2000 database.
224071 INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/?id=224071

Topic: "Upgrading Databases from SQL Server 7.0 (Copy Database Wizard)" on
SQL Server Books Online.
Please let me know if this solves your problem or if you would like further
assistance.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi Peter,

How is this issue going on your side? Please feel free to let me know. To
use the sp_detach_db and sp_attach_db stored procedures to move user
databases, please follow these steps:

1. Detach the database on the source server by using the sp_detach_db
stored procedure. You must copy the .mdf, .ndf and .ldf files associated
with the database to the destination server. See this table for a
description of the file types:

+======================+======================+
| File name extension | Description |
+======================+======================+
| .mdf | Primary data file |
+======================+======================+
| .ndf | Secondary data file |
+======================+======================+
| .ldf | Transaction log file |
+======================+======================+


2. Attach the database on the destination server by using the sp_attach_db
stored procedure and point to the files you copied to the destination
server in the preceding step.For additional information about how to use
these methods, click the article number below to view the article in the
Microsoft Knowledge Base:

224071 INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/?id=224071

Thanks for using MSDN newsgroup.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

In article <MPG.19fb4889777c59f7989682@news.wxs.nl>, pbouwman@wxs.nl
says...
[quoted text, click to view]
Thanks.
Sorry it took so long to answer.