SQL Server platform specific notes

• To use Windows authentication (authenticating as your Windows user), do not provide a username or password. Entering your Windows username and password will not work.
• msdbsc supports using GO in scripts to separate batches so your scripts work just like if you ran them in Management Studio or using sqlcmd.
• If you are using the .zip package, you must have ENU\x86\SQLSysClrTypes.msi and ENU\x86\SharedManagementObjects.msi from http://www.microsoft.com/en-us/download/details.aspx?id=35580 installed. The msdbsc installer will automatically install those for you and they are also installed as part of SQL Server Management Studio 2012. You may need to install them yourself if you are using the .zip package.
• Messages printed using the PRINT statement will be displayed in msdbsc's output.
• Imports will use a snapshot transaction on the source database to ensure transactional consistency of the imported data only if snapshot isolation is enabled on the import source database. If snapshot isolation is not enabled on the import source database and the database is in use, the imported data may not be logically consistent. Foreign keys are checked after an import but that is not a guarantee of logical consistency.
• If the target database is using the full recovery model when importing data into it, it is set to the bulk logged recovery model for the duration of the import and set back to the full recovery model after the data has been imported.