Hello, I support an application for a client and the SQL server was replaced with a new SQL server. The details I'm aware of at this point are: * This was an on-the-fly move to the new database and it's an application with a production-only environment (risky, I know). * There is a scheduled batch job which executes and pulls data from the SQL database and populates a report, which is then sent to a specific distribution list. * Since the move to the new SQL server, the reports are blank.
I'm thinking that the Job either has to be altered to point to the proper database hostname or the application itself may have a missing pointer we didn't configure properly.
Essentially, I'm also wondering if the SQL server has a logging area to record errors in abended jobs.
How is the batch job scheuled - if there is an error it should show there. That you are getting a blan report might mean that the error is being concealed - i.e. the called process isn't receiving an error.
Any SSIS involved - you might have to edit the connections in packages if they are not configurable.
========================================== Cursors are useful if you don't know sql. SSIS can be used in a similar way. Beer is not cold and it isn't fizzy.
SQL Server Migration gone bad...
Posted - 11/15/2012 : 10:03:15
