Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 SQL Server Migration gone bad...
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

1 Posts

Posted - 11/15/2012 :  10:03:15  Show Profile  Reply with Quote
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.


Flowing Fount of Yak Knowledge

United Kingdom
3385 Posts

Posted - 11/15/2012 :  10:08:02  Show Profile  Visit nigelrivett's Homepage  Reply with Quote
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.
Go to Top of Page

Very Important crosS Applying yaK Herder

52326 Posts

Posted - 11/15/2012 :  10:22:12  Show Profile  Reply with Quote
check the datasource for reports and make sure thats pointed to new database as well

SQL Server MVP

Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.04 seconds. Powered By: Snitz Forums 2000