Deploying the database and data to the client site after development

[krussman]

I know I can generate SQL Scripts to reconstruct the database structure at the client's site after I've developed the database at our facility, but how do I move the data when the servers cannot see each other? I have several lookup tables that I need to move the data with the structure. I don't think Backup/Restore will work since the two sites do not use the same backup media.<br>
<br>
Thanks...

 

[Faust]

You can "DUMP" to a file and "LOAD DATABASE" from that same file.<br>
<br>
See details under "DUMP DATABASE" & "LOAD DATABASE". First, create a DUMP DISK DEVICE to which you can DUMP and to. Copy/move that file to a disk where the other SQL Server will see it, create a dump device that map over it, and restore from it. Hope this will help.<br>
<br>
Now, with SQL Server 7, you can simply use the sp_detach... and sp_attach... system stored procedures to send/copy/mail a database!<br>
<br>
Sylvain Faust<br>

http://www.sfi-software.com<br>

 

[Lehtoant]

If your lookup tables are small, I would recommend you to bcp them out to text file and zip/pack them to (several?) diskettes. For large data tables you should invest in zip-drive that you can dump/load the whole database and transfer to new locations.<br>
<br>
Al

 

[Faust]

Yes, you can also generate SCRIPTS that ALSO include data population (i.e. INSERT...).<br>
<br>
A script generator (I'm sorry, it's one of our products since 1993) like the one included in SQL-Programmer will do the job from your development SQL Server.<br>
<br>
Now, if you have zillion rows... it is really not the way of doing it... BCP will be.<br>
<br>
If the number of rows is not that much, having everying in a script file is easyer to handle and manage...<br>
<br>
Info on SQL-Programmer(r), just in case:<br>

http://www.sfi-software.com<br>

<br>
Sylvain Faust<br>
President<br>
Sylvain Faust Intl (SFI)<br>
880 boul. de la Carriere, Suite 130<br>
Hull, Quebec, Canada J8Y 6T5<br>
<br>
SQL-Programmer 2.VIII:<br>
"The best SQL integrated development environment we've seen, earning<br>
PC Week Labs' Analyst's Choice honors." [Oct. 26, 1998]<br>

http://www.zdnet.com/pcweek/stories/news/0,4153,363685,00.html<br>

<br>
Tel: (819) 778-5045, Ext. 804<br>
Toll Free: 1-800-567-9127 (U.S. and Canada only)<br>
Fax: (819) 778-7943 International; (617) 722-9389 U.S. only<br>
Email: sfaust@sfi-software.com<br>
<br>
Sylvain Faust Inc. (SFI)<br>
Delivering SQL Solutions, Since 1988<br>

http://www.sfi-software.com<br>

<br>
To receive news bulletins from SFI automatically, just send a blank email to:<br>
SFI-NEWS-SUBSCRIBE-REQUEST@peach.ease.lsoft.com<br>
<br>
SFI Online Store:<br>

http://store.sfi-software.com<br>

 

[calahans]

If its just a one off (which I presume when your developing for a client), why not link your SQL Server in the office to MSAccess running on a laptop/desktop, and copy the data to local tables in access. In the following manner:<br>
<br>
Make a link to SQL Server via access<br>
<br>
Create a local table (select * into local_table from SQLserv_table where 1=0) or (create local as select * from...)<br>
<br>
Copy in to the local (I'm not sure if access support select into)<br>
<br>
Bring the laptop to the client and configure to connect to client network (staight-forward if both NT or 95 etc.) and reverse process.<br>
<br>
This is a messy way, but would work for a one off.<br>
<br>
If you need more into let me know.<br>
<br>
C