Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Troubleshooting steps of Deploymnet Expand / Collapse
Author
Message
Posted Thursday, November 21, 2013 6:47 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, March 10, 2014 8:38 AM
Points: 107, Visits: 205
Hi Everyone,
Could any one suggest me how to proceed if my deployment gets failed?
What are the minimum troubleshooting steps?
Thanks.


Thanks,
I’m nobody but still I’m somebody to someone………….
Post #1516621
Posted Friday, November 22, 2013 5:24 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 5:08 AM
Points: 391, Visits: 703
What are you deploying? What errors are you getting? Please be more specific




I'm on LinkedIn
Post #1516727
Posted Friday, November 22, 2013 7:52 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, March 10, 2014 8:38 AM
Points: 107, Visits: 205
I have created a package in BIDS
Created a deployment utility
Build the package in BIDS
Deployed from Manifest files.
Fortunately it successes. But i want to know the basic troubleshooting steps.


Thanks,
I’m nobody but still I’m somebody to someone………….
Post #1516794
Posted Friday, November 22, 2013 8:41 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 5:08 AM
Points: 391, Visits: 703
Ah so it's SSIS.

To be honest with you, problems with deployment don't happen so often - as long as the account doing the deployment has permissions to deploy packages to your server and the server you are deploying to has an SSIS instance and is switched on then you'll be fine.

Errors in running a package are far more common. Steps to troubleshooting that (depending on how you are executing) could include looking at the SQL Agent history, looking at the ssislog table (if you have set it up) or simply screaming an offensive word at the computer

I would recommend you set up your own logging of events in any packages that you have. Check out this article for tips on how to go about doing that.





I'm on LinkedIn
Post #1516824
Posted Wednesday, November 27, 2013 10:15 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 2:51 PM
Points: 285, Visits: 771
yeah, it's gonna be a lot easier to assist in troubleshooting when something actually goes wrong.

Like anything else, ya follow the trail from hopefully a helpful error message.
Post #1518143
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse