Hi,
I wrote a number of SQL scripts to do a data migration, from MSSQL 2000 to 2008 R2. These scripts should be run each night. All error message should be captured, though execution may continue, so we have an overview of all errors in the morning. We know when one failing script will cause others scripts to fail, so that's not a real problem.
Multiple related SQL scripts are grouped in a file for ease of development. There a are multiple files, and their number is still growing.
How can I automate this? Can I leave multiple SQL scripts in one file, or do I have to limit the number of scripts per file to one?
I am thinking of using a scheduled job, but I have never created one and I don't know how to handle the error messages.
I wrote a number of SQL scripts to do a data migration, from MSSQL 2000 to 2008 R2. These scripts should be run each night. All error message should be captured, though execution may continue, so we have an overview of all errors in the morning. We know when one failing script will cause others scripts to fail, so that's not a real problem.
Multiple related SQL scripts are grouped in a file for ease of development. There a are multiple files, and their number is still growing.
How can I automate this? Can I leave multiple SQL scripts in one file, or do I have to limit the number of scripts per file to one?
I am thinking of using a scheduled job, but I have never created one and I don't know how to handle the error messages.