Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 19,088 of 19,505    |
|    Mads Aggerholm to All    |
|    'Import' scripted DB ?    |
|    16 Aug 14 07:09:41    |
      From: mads001@xxxxxhotmail.com              Hello!              I am about to move a DB from a 10.50.1600 MS SQL Server to a 10.0.1600       Server.       Backup the SB and restoring in the new place is impossible, since the       version does not 'fit'. I did already try setting it to 'Level 90', but       no luck.       I scriptet the whole thing, including data, and got a large file, about       one Gbyte.       This is far too big for the MS SQL Server to handle.              On the internet i forund this:       sqlcmd -S xxx.xxx.xxx.xxx -i C:\SQLFOLDER\database.sql -o              Unfortunately, it does not work.              So, I scripted it all again, but this time I asked it to split it up,       one file per table/Procedure/function/etc.       I believe it will work, but now I have a lot of files and don't know       which one to do first.       The names are like:       ##MS_PolicyEventProcessingLogin##.Login.sql       ##MS_PolicyTsqlExecutionLogin##.Login.sql       Conv.Schema.sql        |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca