Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2002-07-12 : 09:49:43
|
| Virginia Andersen writes "We are looking for an easy way to distribute our databsae to our clients. We would like to use a script but are finding numerous complications in :1. Creating a complete Script ( we manually create it through enterprise manager. This is clumsy and prone to error) 2. Running the script at the client site who has MSDE ( no admin tools) and needs a very user friendly process. We currently have tried using ADO but find many problems is translating the SQL Server - Generated Scripts to ADO Friendly Scripts. *. The script will have custom processes ( like installing stored procedures to the master database ) which need to be appended to the SQL Server - Generated Script.Before I spend a lot of development time making a custom process, Are there any tools out there which can help? Any tips? I plan to use SQL-DMO as I heard it works just like Query Analyser. Thanks for your help." |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-07-12 : 10:18:05
|
| Hi Virginia,A few comments. First, it sounds like you're doing a bit more than just distributing a database to external parties, if you're adding stored procedures to master. Is this part of a larger installation?Second, scripts only transfer object definitions, not the data itself. You haven't mentioned data in your post but I assume you want it.The easiest way, bar none, to transfer a database is to detach it, migrate the file to the destination database server, and re-attach it. You can read up on the specifics of this by looking up 'sp_attach_db' and 'sp_detach_db' in Books Online. From what you've posted so far I see no need for custom processes.Jonathan Boott, MCDBA |
 |
|
|
|
|
|