Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
twystedpair
Starting Member
5 Posts |
 Posted - 2008-03-13 : 09:41:00
|
| Because of recent changes in the company, I have inherited the SQL Server. I have a little bit of experience, but I will be knee deep in study for the foreseeable future. In the meantime, I do have to manage the SQL Server and deal with all of the problems. It has been fairly self-sufficient until now. I have a regularly scheduled SSIS package that has recently been erroring out. I just don't even know where to start figuring this out. When I look at the History of this two step job, I see that it's failing on the second step, which is a T-SQL script. I am way more of a GUI kinda guy (at least for now) and I am lost when looking at the script. I know that I am not giving enough info in order for someone to help me, but my problem is I just don't know where to even look. Can someone at the very least point me to a place where I can get a better clue as to what is happening and why???Thanks for listening and God bless anyone who understands at all what I'm even trying to ask!!!!! |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-03-13 : 09:44:20
|
| Check job history:click the + sign and you will all error in down pane.Send us those errors , We will be able to help youor check application log. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-03-13 : 23:12:00
|
| And post the script if possible. |
|
|
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2008-03-14 : 09:43:57
|
| This is how I would start troubleshooting if I was on your shoes: (I'm assuming you're familiar with SSMS and where to find things around SQL Server and its tools, if not, let us know)a) Check the job history and see if the information given by that is enough to start troubleshooting the package, which sometimes is not.b) If not, open the package in design mode on Visual Studio and execute it, just keep it in mind that if you are on a Windows Authentication environment, when you execute the package from VS, the system will be using your credentials which could (and should) be different from the credentials you have set on your job.Let me know if this helps, also make sure to post any error messages you get. |
|
|
|
|
|
|
|
|
SSIS package failure