BOOK: Wrox's ASP.NET 2.0 Visual Web Developer 2005 Express Edition Starter ISBN: 978-0-7645-8807-5
This is the forum to discuss the Wrox book Wrox's ASP.NET 2.0 Visual Web Developer 2005 Express Edition Starter Kit by David Sussman, Alex Homer; ISBN: 9780764588075
You are currently viewing the BOOK: Wrox's ASP.NET 2.0 Visual Web Developer 2005 Express Edition Starter ISBN: 978-0-7645-8807-5 section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
My question is once that I've got the example website working, I want to move it to a server. I used SQL 2005 Express for the development machine but the server is running SQL 2k. How do I convert the connection string so that when I copy the site to the new server it will find the SQL Svr 2k and work? In the past I did things with DSN's and am not sure how to proceed here.
You just remove the section User Instance=true from the connection string. Then copy the database .mdf and .ldf files into the data directory of your server (probably something like Program Files\Microsoft SQL Server\80\MSSQL\Data for SQL Server 2000), and attach the database using the SQL Server Enterprise manager utility. You cannot just "copy the site" if the target database server is using SQL Server 2000 - you must attach the database files using Enterprise Manager or the equivalent T-SQL Script.
quote:Originally posted by alexhomer
You just remove the section User Instance=true from the connection string. Then copy the database .mdf and .ldf files into the data directory of your server (probably something like Program Files\Microsoft SQL Server\80\MSSQL\Data for SQL Server 2000), and attach the database using the SQL Server Enterprise manager utility. You cannot just "copy the site" if the target database server is using SQL Server 2000 - you must attach the database files using Enterprise Manager or the equivalent T-SQL Script.