We are using SQL Server 2014 (version in screenshot shown below). From a very long time we have a Waiting Tasks visible int Activity Monitor. After installing latest version of SSMS in his Activity Monitor Waiting Tasks are gone.
Why does this happen?
From where can I get script to get Waiting Tasks the same as included in Activity Monitor?
Related
For the past week, multiple SSIS packages running on SQL Server Agent that load data into Snowflake have started returning the follow message randomly.
"Failed to acquire connection "snowflake". Connection may not be configured correctly or you may not have the right permissions on this connection."
We are seeing this message across multiple jobs and each of the jobs is loading multiple tables and its not happening on each call to Snowflake within the projects, but just on one or two tasks in jobs that have 100s.
We are using the 2.20.2 drivers from Snowflake
We have ran the jobs while WireShark was capturing network traffic and were received by the network team. They didn't have much luck because the ACK messages were not being shown.
We also ran Process Monitor while the jobs ran and we did not find anything that alluded to any issues
We also dug though the logs from the Snowflake driver and found the calls right before and right after, but no messages for the task that failed. Since those logs bounce around on which file they are sending to, its a bit hard to track sequential actions when multiple task on a job are running together.
We also installed SnowCD and ran it and it returned a full success message.
The user that runs the jobs on SQL Server Agent is an Admin on the server and has SysAdmin rights on the Sql Sever instance.
The warehouse the drivers are connected to are a size Large with a max of 3 clusters (was at 1 when the issue started, but upped it to 3 to see if that helped)
Jobs are running on Windows Server 2016 DataCenter in Azure
SQL Server instance is Sql Sever 2016 13.0.4604.0
We cannot figure out why we are suddenly and randomly using connection to Snowflake.
Some ideas to help get these packages working:
Add a retry to the tasks that are failing. The task would move onto the next step only upon success:
https://www.mssqltips.com/sqlservertip/5625/how-to-retry-sql-server-integration-services-ssis-control-flow-tasks/
You can also combine the truncate and insert into one step using the insert overwrite into command which will allow your package to run quicker and have one less task for failure:
https://docs.snowflake.net/manuals/sql-reference/sql/insert.html#insert-using-overwrite
Once the SSIS packages are consistently completing, you can analyze the logs at the point of failure to see if there is any pattern to help you identify the root cause.
SSIS package wasn't even started, SQLAgent returned error almost instantly.
It happened once, the job is scheduled to run daily for almost a year now, and until now there wasn't any problem with it. Credentials, data structure weren't changed (we're migrating to another domain, but it didn't affect other jobs using the same proxy).
Error returned by SQLAgent:
Executed as user: <SSIS_PROXY>. Microsoft (R) SQL Server Execute Package Utility
Version 12.0.4100.1 for 64-bit
Copyright (C) Microsoft Corporation. All rights reserved.
Started: <TIME> Failed to execute IS server package because of error 0x80131904.
Server: <SERVER>,
Package path: <PATH>, Environment reference Id: NULL.
Description: Timeout expired.
The timeout period elapsed prior to completion of the operation
or the server is not responding.
Source: .Net SqlClient Data Provider Started: <TIME>
Finished: <TIME> Elapsed: 30.654 seconds.
The package execution failed. The step failed.
There are other jobs running in the same time window and they weren't affected.
One of them is maintenance job (backup), could that put some exclusive locks on system tables (or whatever) and result in timeout?
Any idea what could've happened?
I was having this error intermittently. On occasion a job that runs fine on a schedule would error and the next interval would run fine. After some research I found that the resources in the SSIS catalog can become locked by other agents starting jobs. The fix that worked for me was to automatically retry 3 times. I have not had the error since.
Hopefully MS will find a way to correct this issue under the hood.
Hope this works for you:
https://technet.microsoft.com/en-us/library/ms188952.aspx
SQL Server Version: Microsoft SQL Server 2014 - 12.0.2495.0 (X64)
Mar 31 2015 09:47:37
Copyright (c) Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 (Build 9600: )
Database Recovery Model : Full
Backup Type : Full
Performing simple insert transactions using SQLBulkCopy with Batch size : 10000
Database errors out after sometime as below:
“The transaction log for database 'ClientDB' is full due to 'XTP_CHECKPOINT'.”
I am not able to perform any operations after this error message. Not able to shrink the log file.
I had a similar problem: I did not have replication but once I used Memory Optimized table as a test, database in Simple recovery mode, but my transaction logs weren't truncated. Manual truncation, even right after a full backup, gave the error:
Cannot shrink log file X because the logical log file located at the end of the file is in use.
A manual checkpoint failed:
Msg 41315, Level 16, State 4, Line N
Checkpoint operation failed in database X.
A manual checkpoint only succeeded right after restarting the SQL Service, which would lead to a 4 hour In Recovery state because of my Multi Tb database size. I also tried to set the autogrowth to a specific size, but it all ended up doing the same: fill up the transaction logs until no space was left.
Finally, after days and nights trying and researching, I found the solution for my problem by installing the Cumulative Update 3 for SQL Server 2014 SP1
I am not sure but you can see this link
They make: "... The XTP_CHECKPOINT cannot be removed from the log_reuse_wait unless a full db backup is done..."
while runnig the ssis package i'm calling sp in the ADO.net source,but getting this error
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.I have set the command timeout to 0(infinite time),but still getting the error.The sp is working fine in sql server and taking approx 31 seconds for executing it,but in ssis its throwing error..please help me on this.Thanks in advance.
Check out this bug report - there is a sp in the SSISDB database in SQL Server 2012 causing packages to time out before they start running. I had error message "Failed to execute IS server package because of error 0x80131904" and "Description: The operation failed because the execution timed out" when calling multiple (more than 10) packages from my scheduling tool via DTExec. Please vote for the issue on the connect site so that MS can release an official fix.
Today, I was experiencing the same error while using the ADO Net Source, my sp works fine on the SSMS, but fails in the package, while In the package, it errors our with a long laundry list of errors, but basically it is timing out.
Solution is Right click on the ADO Net Source - Show Advanced Editor - Component Properties - Custom Properties - CommandTimeout - Increase the time here
I had the same problem in SSAS.
The way I sorted this out was extending the client and server time out settings.
you can see more details in the link below:
routine to backup ssas databases fails with: The XML for Analysis request timed out before it was completed
Last night we migrated to a brand new server and moved all our data from SQL 2000 to SQL 2008 R2.
Everything worked out fine except any jobs that have steps where a linked server is referenced are failing and we can't figure out why.
If I log in as 'sa' and browse the linked servers I can expand and browse the objects, etc. I can also run the jobs' code in a query window logged in as 'sa' with no problems.
However when I run the job I get the following:
Execute of job 'ARUpdate' failed. See the history log for details.
History log:
The job failed. The Job was invoked by User sa. The last step to run was step 1 (Step 1).
Executed as user NT AUTHORITY\SYSTEM. Login failed for user 'ANSAC_NT\ANSAC-SQL$'
[SQLSTATE 28000] (Error 18456). The step failed
Sql Severity: 14
Sql Message ID: 18456
Any ideas as to why this is happening? I assume it's something with the sa account?
Happens even if I recreate the job from scratch logged in as sa or with a new sysadmin account created.
Note: we ported over the logins from 2000-2008 as well if that helps.
Thanks!