D
ducity
Guest
Short answer is no. One approach, is that you edit the .sql from your failed attempt, change all datetime to datetime2 (allows for larger date range) , and all the varchar (X) to varchar (100) or varchar (150), obviously if you already have varchar (100) or (150) then you need consider increasing them first. Save this as .sql. When the "Output Completed" dialogue appears , DO NOT PRESS OK, instead, overwrite the generated .sql with your modified version .sql, and then press OK. Should you get another failure, adjust your modified schema and rinse and repeat. Other alternative is that you can modify the schema in SQL , suck it back to the schema holder, and (whilst connected to sql db as logical db "wot", run progress code input from , repeat: create wot. import wot. end. This approach means you aren't going through the whole migration each time....
Continue reading...
Continue reading...