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 |
|
imtu_174
Starting Member
9 Posts |
 Posted - 2005-09-06 : 19:29:10
|
| HiI have some tables in my SQL Server 2005 database. I need to create insert scripts for them. Since these tables contain the CLOB and BLOB values and the number of records is huge, I need to devise a way to install this table data on any new database(Assuming the new database is created and the table structure exists) .Can some one suggest me how I can do this ?DTS or SSIS is out of question because least manual interference is required.Thanks & RegardsImtiaz |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-09-07 : 02:59:24
|
| Import from XML file?Kristen |
 |
|
|
imtu_174
Starting Member
9 Posts |
Posted - 2005-09-09 : 13:32:05
|
| Well can you explain a little bit more ? |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-09-09 : 14:18:26
|
Seems to me that you could do:- Provide a BACKUP file that gets RESTORED during the install
- Provide some sort of CSV file that is imported during the install
- Use some sort of INSERT(...) VALUES (...) script during the install
- Have a Stored Procedure in your freshly installed DB that could process XML
The first three are OK, but I guess don't really fit well with your needs.The XML route would allow you to pass some "huge" XML to a Stored Procedure in your freshly created, empty, database which them inserted the relevant rows into all the tables.Personally I use choice 1 - restoring the DB from a "Gold Master" - as we don't even need to have scripts that create the tables etc. So for each new version that we issue we just patch our Gold Master the same as we do our Client DBs, and "away we go". But this can be hard-ish to do in an unattended / self-install scenario.Kristen |
|
|
|
|
|
|
Data Migration - Insert Script / Fresh install