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 «««34567

SQL Overview SSIS Package III - Full Package Expand / Collapse
Author
Message
Posted Monday, September 12, 2011 3:11 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 4, Visits: 703
Hi David,

I have couple of questions on SQL_overview package 3. I see that the readme.txt file is missing in the ZIP folder or else may I know what changes need to be made for variable “SRV_Conn” and also to the connections which you have mentioned in the point because it is throwing me error for Update data used size and also load job history. Will this package execute if we are using mirroring because it throws me a error like this. I am also attaching the error file and screen shot for the errors I am getting.
ERROR 1: " failed with the following error: "The database "tibco_domain_stg3" cannot be opened. It is acting as a mirror database.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Error 2:
Source Output" (11). The column status returned was: "Text was truncated or one or more characters had no match in the target code page.".
Error: 0xC020902A at Load Job History, OLE DB Source [1]: The "output column "message" (47)" failed because truncation occurred, and the truncation row disposition on "output column "message" (47)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
Error: 0xC0047038 at Load Job History, DTS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Error: 0xC0047021 at Load Job History, DTS.Pipeline: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038.

also please let me know what changes I need to make I am only stuck in this part

Thanks!
Ashvin

Post #1173796
Posted Tuesday, September 13, 2011 6:40 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Yesterday @ 7:29 AM
Points: 184, Visits: 1,014
The SQL Overview package has been updated in SQL Overview V - Monitoring Long Running Jobs. You will find a full download of the package in this article.

I am sorry I could not find a list of changes for this package created in 2007.


I have never tested this package with mirrored databses and will need to create an environment to develop any solution to handle it. I know I added logic to handle offline databases but do not know if it handles database mirroiring.


David Bird

My PC Quick Reference Guide
Post #1174087
Posted Tuesday, September 13, 2011 6:30 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 4, Visits: 703
Hi David,

Thanks for the quick reply...

I was able to execute the package successfully from SQL server overview part 5. Thanks for the great post its great to work on...:)

I have one more question outside this topic which is related to DB mirroring...Our db's which are configured for DB mirroring keep on failing regularly without any specific reason we also verify the error log but still not able to identify the root cause for this. Can you please share your opinion regarding any changes for db's to not fail over on their own.this is implemented on Virtual machines.

Thanks!
Ashvin
Post #1174604
Posted Wednesday, September 28, 2011 2:31 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, September 3, 2014 6:35 AM
Points: 282, Visits: 2,211
Gaius Baltar (11/4/2008)
Hi,

Collect Job Info:
SELECT @@SERVERNAME AS Server

In Collect Backup History:
SELECT substring(@@SERVERNAME,1,128) AS Server,



Just found this today on a problem server. Seems to happen when a server name is changed after SQL is installed. Modify code.


--Old Way
Select @@ServerName

--Better way in some cases
SELECT SERVERPROPERTY('ServerName')


MCITP, Database Administrator
A hodgepodge of Information Technology and Life
LinkedIn Profile
My Twitter
Post #1182836
Posted Thursday, September 29, 2011 7:44 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Yesterday @ 7:29 AM
Points: 184, Visits: 1,014
To fix the value of @@SERVERNAME for renamed server use

sp_dropserver <old_name>
GO
sp_addserver <new_name>, local
GO

I have used these comamnds to fix @@SERVERNAME. It requires a restart of the instance.



Source http://msdn.microsoft.com/en-us/library/ms143799.aspx


David Bird

My PC Quick Reference Guide
Post #1183166
« Prev Topic | Next Topic »

Add to briefcase «««34567

Permissions Expand / Collapse