SQL Server instance was unreachable(down) at 2.00Pm and a dump was created at 2.01pm.
I have observed "Warning: Failure to calculate super-latch promotion threshold".
We haven't observed any blockings or long running queries during that time.There is no information at SQL log also.
Could somebody help me to find out the root cause for the server down?
Hello ,
This issue is only after reboot of the server. When the SQL server service stop and we started it again this do not happen untill the next reboot. It stop working around an hour after the reboot.
After debugging SQLDump0032.mdmp file we receive this:
|
Thank you.
Has that always been true? I was under the impression you had to stop the trace to read it, but I just tried it in SQL 2014 and it seems to read just fine even active.
Thanks,
Josh
Hi there,
how can I get who is logging to my server both successfully and failed? It is authorized domain users from different AD and before decommission some of them (not being used but I am not totally sure) need facts.
I know that you can enable on Security page on Server Properties(SSMS) but I don’t find the .log file.
\Program Files\Microsoft SQL Server\MSSQL12.instace1\MSSQL\Log ??
Thanks in advance
Hello all,
My database size is 72GB. I have deleted large amount of data.after deleted data the database size is 72GB.
How to Reclaiming data file free space after deleting a large amount of data .please suggest me.Please see the database current size and available space.please help me.
Dear All,
I have SSIS job which I'm running through proxy but I keep receiving the following error even though there is nothing wrong with the 'password', is there anything else I can check please?
Unable to start execution of step 1 (reason: Error authenticating proxy 'proxy name', system error: Logon failure: unknown user name or bad password.). The step failed.
Thank you in advance!
We have been backing up our on premise sql instances (3 different servers) to various azure storage accounts for the past several months without issue.
Starting on July 14th, we have been increasingly unable to complete backups with the following message recorded in the logs:
A nonrecoverable I/O error occurred on file "https://<removed>.blob.core.windows.net/sql-full/<removed>.bak:" Backup to URL received an exception from the remote endpoint. Exception Message: Unrecoverable error occurred during Flush operation. Msg 3013, Level 16, State 1, Server <removed>, Line 1 BACKUP DATABASE is terminating abnormally. Outcome: Failed Duration: 00:03:05 Date and time: 2016-07-17 03:33:05
The error is occurring on full, differential and log backups.
We are using SQL 2014 standard (sp 2) running on fully patched Windows 2012 R2 servers. At the point the errors started happening we had only installed sp 1, but have since installed sp 2 to see if it would help.
We generally use Ola Hallengren's backup scripts executed via sql jobs, but we have also tried manually backing up directly to azure via SSMS and that has failed as well.
We've searched around but have been unable to find any solution.
Any suggestions on how to resolve this issue would be greatly appreciated.
Hi,
We have SQL server DB which get refreshed with LIVE db every night and this restored DB is used for business objects reporting purposes, we are having performance problems some reports are running over 8 hours.
First place I looked at was indexing and found some missing indexes on heavy used tables and built them and some reports are OK but still having performance issues.
Next was looking at memory problems, then we increased ram to another 6GB from 28 to 34GB. But when I see plan cache on the server it almost empty for restored DB.
We have some additional index included in part of restore process.
Just to confirm does restoring the DB clears all plan cache?
Is it causes any proformance problems? Or should I safely exclude this from my troubleshooting list?
Any help appreciated.
Regards,
satwick
Hi,
I have a Database with Filetable size of 20GB. The Update Statistics maintenance task is taking more than 4 hours without any result (no Success nor Failed) for updating the statistics of the FileTable.
Why the Update statistics for filetable takes so long ? We are performing the Update Statistics for FileTable separately. Is there any recommendations for updating the Statistics for FileTable.
hello Gurus,
my backups are running 90 - 120 min.
Does backup captures changes after the beginning of the backup.
gene
In this article describing dmv sys.dm_os_memory_cache_hash_tables, column "buckets_max_length" is defined to mean "Maximum number of cache entries in a bucket."
From this description, I would infer that the threshold for desired maximum number of entries in a particular cache would be calculated as (buckets_count * buckets_max_length). Following this logic, running the following query on my system yields the results shown below:
SELECT name as cache_name
, buckets_count as buckets
, buckets_max_length as entries_per_bucket
, (buckets_count * buckets_max_length) as max_entries_for_cache
FROM sys.dm_os_memory_cache_hash_tables
WHERE [type] IN ('CACHESTORE_SQLCP', 'CACHESTORE_OBJCP', 'CACHESTORE_PHDR');
-- RESULTS --
cache_name buckets entries_per_bucket max_entries_for_cache
Object Plans 40009 4 160036
SQL Plans 40009 7 280063
Bound Trees 4001 24 96024However, in this article on SQL Caching, the description given in the section titled "Local Memory Pressure" regarding the calculation of an upper boundary on cache entries is as follows:
"In addition to memory pressure occurring when the total amount of memory reaches a particular limit, SQL Server also indicates memory pressure when the number of plans in a store exceeds four times the hash table size for that store, regardless of the actual size of the plans."
This definition is re-referenced in this recent hotfix article for SQL Server, where it is stated:
"The maximum number of entries that a plan cache can hold is four times of the buckets count."
While this definition is consistent with my assumption above for the "Object Plans" cache, which has a buckets_max_length = 4, it is inconsitent for other caches with other defined max_length values, leading me to question my very sanity.
:)
Can someone help me clear up the real intended meaning AND internal use of buckets_max_length? I'd like to be able to detect when internal caches might be under pressure due to too many entries or to much space used, and getting a clear understanding of this dmv would help.
Trying to apply the SQL Server 2008 R2 SP3 on passive node but getting an error message that "The SQL Server failover cluster instance 'SQL_REPORT' was not correctly detected. The instance was discovered on the local node but it was not found to be active. To continue, confirm the state of the instance installed on all applicable nodes of the cluster and the state of the failover cluster resources".
Instance SQL_REPORT overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): -2068578304
Exit facility code: 1204
Exit error code: 0
Exit message: The SQL Server failover cluster instance 'SQL_REPORT' was not correctly detected. The instance was discovered on the local node but it
was not found to be active. To continue, confirm the state of the instance installed on all applicable nodes of the cluster and the state of the failover cluster resources.
Start time: 2016-07-19 16:23:54
End time: 2016-07-19 16:24:51
Requested action: Patch
This is a Windows Server 2008 r2 and I successfully apply the 2008sp3 on the node two and failover the resources but this one is giving me the errors.
I am attempting to write an SQR (it will run from PeopleSoft) that updates a linked server. It fails with the following error:
(SQR 5528) ODBC SQL dbexec: SQLExecute error 7412 in cursor 2:
[Microsoft][SQL Native Client][SQL Server]OLE DB provider "SQLNCLI" for linked server "DUL41" returned message "No transaction is active.".
(SQR 5528) ODBC SQL dbexec: SQLExecute error 7391 in cursor 2:
[Microsoft][SQL Native Client][SQL Server]The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "DUL41" was unable to begin a distributed transaction.
Error on line 58:
(SQR 3735) Could not execute SQL.
SQR for PeopleSoft: Program Aborting.
-------------------- Details ------------------------------
- The code is simply doing a delete right now. delete from linkedserver.db.dbo.table where column = 1
- The SQL runs fine from Query Analyzer, so I think MSDTC must be setup correctly everywhere, and the linked servers must be defined correctly. My QA test is using the same ID (sa) as my SQR.
- If I just write a select statement in the SQR, it works fine.
- in this example, SQR is connecting via ODBC, using SQL Native Client driver.
------------------ Environment --------------------------
- Main server: Win2003, SQL2005sp2, active/passive cluster. MSDTC is setup on the cluster.
- Linked server: Win2003, SQL2000sp4, not a cluster. (I also tried a SQL2005 server just to test) This is the DUL41 server referenced in the error message. MSDTC is running.
- Everything is running from a different Win2003 box, that connects to the main server using ODBC/SQL Native client
Thanks for any help or ideas. Even any way to get better error messages, or a better way to test this.
Hi,
Please help me on this msdb mdf need shrink because we running very low space on the drive ..Request you please advice me if we shrink the msdb there is any issue further ?
what is better way to shrink msdb kindly advice .
baskarlakshmi
Dear Experts,
'sa' password is changing everyday automatically. What would be the reason behind this ?
How can we stop this ? Kindly help.
Regards
Senthil.K
Senthil
Hi All,
I have notice that one of our clustered SQL servers has terminated unexpectedly twice this week. I've check the SQL Server Logs and there are no entries fro the time during the crash.
I have also check the event logs and the below events were logged:
evt1
evt2
evt3
evt4
evt5
is there any other logs I can check for this as I can't find the cause of the issue
Thanks for your help
Robert
Hi experts,
I have a MERGE statement that it is taking too long… On the execution plan, this is 50% of the workload.
As you can see, I think the MERGE is taking long because it has to update every index… I created the indexes some time ago per requests of people complaining certain reports were slow… I created them as “test…” but never checked how much were they used.
How can I check if they are really used or they are wasting space/resources…?
I also noticed the difference between actual/estimated number of rows, but I don’t see outdated statistics, how come this happens???
Thanks in advance!!
Hello,
i am ruuning with a serious proble which is my cluster SQL Server 2008 start generte a Stack dump files every minutes and utilized all the system database drive
and i am so close from have a crashed SQL
i have uploaded a sample of the files SQL Server genrted at the below link
https://skydrive.live.com/?cid=d2927af923df3482&sc=documents&uc=2&id=D2927AF923DF3482%21113
please your urgent response is highly appriciated
Is "option(recompile)" more efficient than "with recompile"?
Say you have a stored procedure about 700 lines long, maybe twenty big selects populating a temp table, with some logic to choose about half of them for any set of parameters. If you say "with recompile" then all 700 lines are recompiled each call. If you say "option(recompile)" on all the big statements then just about half the lines will be recompiled each time.
Right?
Or, is "with recompile" smart enough that it acts pretty much the same way?
Thanks,
Josh