Tuesday, March 12, 2013

[MS SQL Server] SSIS Job fails using Domain Account

[MS SQL Server] SSIS Job fails using Domain Account


SSIS Job fails using Domain Account

Posted: 12 Mar 2013 09:51 AM PDT

I get this error when I attempt to run the Package using the Domain Account, SQLServerAgent.[quote]MessageExecuted as user: MyDomain\SQLServerAgent. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 01:29:42 PM Could not load package "\Dev\AS400\CYP_Staging_Load_Truncate_Nightly" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80040E4D (Login failed for user 'MyDomain\SQLServerAgent'.). The SQL statement that was issued has failed. Source: Started: 01:29:42 PM Finished: 01:29:42 PM Elapsed: 0.046 seconds. The package could not be loaded. The step failed.[/quote]The package is stored in MSDB.I added the Account to sysadmin and made it a local admin.It works with my login.It is totally weird.I granted permissions to the Temp Folder for the SQLServerAgent but no dice.Any ideas?Thanks.

Monitoring error

Posted: 11 Mar 2013 07:47 AM PDT

I'm using Red-Gate Monitor tool to help me in managing our SQL Server. I see very frequently these two messages: Monitoring error (SQL Server data collection) and Monitoring Error (host machine data collection). I know there could be almost an infinite number of reasons for these error but I was wondering how would it be best to try to find out the reasons why I'm getting notified on these. I looked at our existing backup jobs and schedule jobs as well as the logs to see if I can find a reason why this is happening. Any other ideas or a direction that I need to go to get more information on this it would be very appreciated.

Find SPID of Linked Server Call

Posted: 12 Mar 2013 07:14 AM PDT

Hi SCC,I have a stored procedure on server A that makes a linked server call to server B.... on server A I see the wait type is OLEDB so I want to look at the SPID on server B... is there a way to identify the remote SPID other than connecting to the server and doing an sp_who2 and looking for the client who made the connection and then username of the linked server?Thanks!

Reporting Services Logs not being deleted

Posted: 08 Feb 2011 06:16 AM PST

We have a server running SQL 2008 SP1, Standard. We recently discovered that SSRS isn't cleaning up it's log files. Checking the in the ReportingServicesService.exe.config file and Service configuration confirms the service is configured to the default of 14 days, and the the log file locations are also default.Does anyone have an idea why SSRS would keep over a years worth of log files, or what could stop the cleanup. We aren't seeing anything fail in the environment but the drive fills up.CheersLeo

Big table

Posted: 11 Mar 2013 07:59 AM PDT

We have a lookup table GeographicLookup table with a primary key called gisGeorgraphicLookup.It now has 2 million records, with each year we have about 550000 rows records ranging year 2010-2014 .Could many records like this reduce performance or reduce the speed for lookup?If we only use most recently a couple years data, should we archive other records into another table?or any other recommendations, we are using SQL 2008 standard edition.

DR/HA proposal

Posted: 11 Mar 2013 10:59 AM PDT

I need to write DR/HA proposal any suggestions?

SSMS showing local DBs not remote DBs when editing remote maint package

Posted: 12 Mar 2013 12:11 AM PDT

Hi AllWhen I open an Integrity check task from a server (SQL 2008 R2) with my SSMS(SQL2012) on my PC the task shows loacal DBs in the database drop down. Any ideas.:w00t:

dadication and shared connection in sql

Posted: 12 Mar 2013 12:09 AM PDT

is there a concept of dadicated connection and shared connection in sql similar to oracle.if yes, how it has to be configured can anybody explain about this.Thanks in advance

Replication from SQL 2008R2 to SQL 2012

Posted: 11 Mar 2013 05:41 PM PDT

Gurus, I have weird replication issue. Can't figure out what the issue is here. Please help me with ideas/known bugs(if any):w00t:Publisher: SRVA - SQL 2008R2Distributor: SRVB - SQL 2008R2Subscribers: SRV1 - SQL 2008R2 SRV2 - SQL 2008R2 SRV3 - SQL 2008R2 SRV4 - SQL 2012Number of Publications: 3originally, replication was set-up from backup. later on, we had to add couple of articles to Publication-3. we followed an article which said to switch off "immediate_sync" and "allow_anonymous" to false and re-snap. This way, we will take snap of only the two articles we have to add.Now, the issue is, we had to add two more articles today, when we followed same procedure, snapshot agent has created drop and re-create scripts for the two articles. However, create table scripts were not applied to the SRV4. Rest of all the procs for repl insert, update, delete were created on this instance. Just the tables and thier pks weren't created.Fixed the issue by manually creating the table and Pk. Stopped and re-started Distributed agent and everything started to work fine.:pinch:Checked the permissions for snapshot, distributed agents. Everything is normal with regards to permissions. Can't find a root cause of the issue. Please help!!:crying:ThanksJagan K

No comments:

Post a Comment

Search This Blog