I posted the below to Microsoft Azure  >  Azure Key Vault

https://social.msdn.microsoft.com/Forums/en-US/00ac441e-75b5-4009-aba3-b4828a23b034/mssql-tde-certificates-in-key-vault?forum=AzureKeyVault

I am posting here in case if someone has experience with this and can answer my question.

Thanks!

-------------

Hello,

I'm pretty new to the Azure space and have some questions regarding Key Vault.

I recently setup SQL Server 2017 with TDE (Transparent Data Encryption) enabled for all databases in an on-prem sql server.  I have been playing with Azure.  I'm able to perform BACKUP/RESTORE between on-prem and Azure.  Now, I'm poking around with Azure Key Vault.  Because my databases are TDE enabled, I have previously backed the TDE certificate from the source server.  I have now converted my .cert and .pvk files to .pfx.   Uploaded to Azure -> Key Vault -> Certificate and downloaded it as a backup to my on-prem machine.   My question is this: If I had a disaster on my on-prem sql server, how would restore this downloaded certificate (in pfx format) onto say, a stand-by sql server or if I had to rebuild my sql server 2017 from scratch?

Thanks!

Hi all,

for some reason I am not able to see the certificate from the Configuration Manager --> SQL server network configuration --> Protocols for MSSQLSERVER when I right click and select the Certificate under the dropdown.
Certificate was imported from sys admin guy and I can see it under Certificates' Personal folder of the Console Root - certificates (Local Computer). It also looks that is configured and imported properly and in line with the requirements under the Microsoft's links below:

http://technet.microsoft.com/en-us/library/ms191192.aspx
http://technet.microsoft.com/en-us/library/ms189067%28v=sql.105%29.aspx

The version of the operating system is where SQL server resides is Windows Server 2012 Standard Edition and SQL Server is 2012 developer edition.

Since my sql server services Engine is running under service account with Deny Logon Locally domain policy, I started the service as LocalSystem and open the Configuration Manager with an administrative account, but still didn't worked.

Feedbacks on this issue are highly appreciated.

Cheers

Hi experts,

  I got an error message and the error message is ambiguous. I google and find a lot of discussions but I don't know how to troubleshoot.

( https://support.microsoft.com/en-za/help/310834/description-of-common-causes-of-sql-server-error-message-844-or-error )

I run our SAP on SQL with HPE DL580. Please give me a guideline and any information is appreciated. I upload my complete errorlog on google drive( https://drive.google.com/file/d/1EKLhIGBxsEFYaJ6EIEPxUREqj0HOlLSj/view?usp=sharing )

By the way, database files and transaction log both are located on PCIe SSDs.

--- systeminfo ---

Processor(s):              4 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 85 Stepping 4 GenuineIntel ~2494 Mhz
                           [02]: Intel64 Family 6 Model 85 Stepping 4 GenuineIntel ~2494 Mhz
                           [03]: Intel64 Family 6 Model 85 Stepping 4 GenuineIntel ~2494 Mhz
                           [04]: Intel64 Family 6 Model 85 Stepping 4 GenuineIntel ~2494 Mhz

Total Physical Memory:     3,145,395 MB

---

"Windows Server 2016 Version 1607(OS Build 14393.2395)"

SQL: "Microsoft SQL Server 2012 (SP3-CU10) (KB4025925) - 11.0.6607.3 (X64) 

Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 14393: )"

--- when the problem occurred ---

2018-12-07 10:15:26.97 spid20s     Error: 5901, Severity: 16, State: 1.
2018-12-07 10:15:26.97 spid20s     One or more recovery units belonging to database 'TP1' failed to generate a checkpoint. This is typically caused by lack of system resources such as disk or memory, or in some cases due to database corruption. Examine previous entries in the error log for more detailed information on this failure.
2018-12-07 10:15:26.97 spid20s     Error: 845, Severity: 17, State: 1.
2018-12-07 10:15:26.97 spid20s     Time-out occurred while waiting for buffer latch type 3 for page (16:880781), database ID 5.

--- partial errorlog ---

2018-12-07 10:15:13.93 spid20s     A time-out occurred while waiting for buffer latch -- type 3, bp 0000013662FA21C0, page 16:880781, stat 0xb, database id: 5, allocation unit Id: 72057643394072576, task 0x00000133A2455498 : 1, waittime 300 seconds, flags 0x100000001a, owning task 0x00000133A1A4D498. Not continuing to wait.
2018-12-07 10:15:13.97 spid20s     Using 'dbghelp.dll' version '4.0.5'
2018-12-07 10:15:13.98 spid20s     **Dump thread - spid = 20, EC = 0x0000009729DAA160
2018-12-07 10:15:13.99 spid20s     ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0002.txt
2018-12-07 10:15:13.99 spid20s     * *******************************************************************************
2018-12-07 10:15:13.99 spid20s     *
2018-12-07 10:15:13.99 spid20s     * BEGIN STACK DUMP:
2018-12-07 10:15:13.99 spid20s     *   12/07/18 10:15:13 spid 22652
2018-12-07 10:15:13.99 spid20s     *
2018-12-07 10:15:13.99 spid20s     * Latch timeout
2018-12-07 10:15:13.99 spid20s     *
2018-12-07 10:15:13.99 spid20s     *  
2018-12-07 10:15:13.99 spid20s     * *******************************************************************************
2018-12-07 10:15:13.99 spid20s     * -------------------------------------------------------------------------------
2018-12-07 10:15:13.99 spid20s     * Short Stack Dump
2018-12-07 10:15:14.03 spid20s     Stack Signature for the dump is 0x000000011415DBA4
2018-12-07 10:15:26.94 spid169     Remote harden of transaction 'user_transaction' (ID 0x000000008eadcb41 0010:ab2858a7) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18905904:250) failed.
2018-12-07 10:15:26.94 spid39s     A connection timeout has occurred on a previously established connection to availability replica 'DL580-2' with id [B85FD98F-6E3B-420B-BAD3-CBD4FF4D133D].  Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
2018-12-07 10:15:26.94 spid819     Remote harden of transaction 'user_transaction' (ID 0x000000008eadcbda 0010:ab2858a8) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18905969:87) failed.
2018-12-07 10:15:26.94 spid36s     Remote harden of transaction 'GhostCleanupTask' (ID 0x000000008eadcd5b 0010:ab2858ab) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906120:20) failed.
2018-12-07 10:15:26.95 spid645     Remote harden of transaction 'user_transaction' (ID 0x000000008eadcbb1 0010:ab2858ac) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906127:51) failed.
2018-12-07 10:15:26.95 spid44s     AlwaysOn Availability Groups connection with secondary database terminated for primary database 'TP1' on the availability replica with Replica ID: {b85fd98f-6e3b-420b-bad3-cbd4ff4d133d}. This is an informational message only. No user action is required.
2018-12-07 10:15:26.95 spid782     Remote harden of transaction 'user_transaction' (ID 0x000000008eace892 0010:ab2858ad) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906148:70) failed.
2018-12-07 10:15:26.95 spid1656    Remote harden of transaction 'user_transaction' (ID 0x000000008eadc933 0010:ab2858af) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906182:23) failed.
2018-12-07 10:15:26.94 Server      Error: 19419, Severity: 16, State: 1.
2018-12-07 10:15:26.94 Server      Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group 'AGTP1' within the lease timeout period.
2018-12-07 10:15:26.95 Server      Error: 19407, Severity: 16, State: 1.
2018-12-07 10:15:26.95 Server      The lease between availability group 'AGTP1' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
2018-12-07 10:15:26.95 Server      AlwaysOn: The local replica of availability group 'AGTP1' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required.
2018-12-07 10:15:26.95 Server      The state of the local availability replica in availability group 'AGTP1' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. 
2018-12-07 10:15:26.95 spid44s     AlwaysOn Availability Groups connection with secondary database terminated for primary database 'TP1' on the availability replica with Replica ID: {b85fd98f-6e3b-420b-bad3-cbd4ff4d133d}. This is an informational message only. No user action is required.
2018-12-07 10:15:26.95 spid934     Remote harden of transaction 'user_transaction' (ID 0x000000008eadcb69 0010:ab2858b0) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906186:137) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.178]
2018-12-07 10:15:26.95 spid2182    Remote harden of transaction 'user_transaction' (ID 0x000000008eadbfd1 0010:ab2858b1) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906217:18) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.172]
2018-12-07 10:15:26.95 spid1171    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcc25 0010:ab2858b2) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906224:63) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.172]
2018-12-07 10:15:26.95 spid620     Remote harden of transaction 'user_transaction' (ID 0x000000008e6bdf8d 0010:ab2858b3) started at Dec  7 2018 10:11AM in database 'TP1' at LSN (957263:18906246:32) failed.
2018-12-07 10:15:26.95 spid1806    Remote harden of transaction 'user_transaction' (ID 0x000000008eadc908 0010:ab2858b5) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906255:5) failed.
2018-12-07 10:15:26.95 spid281     Remote harden of transaction 'user_transaction' (ID 0x000000008ead6f6c 0010:ab2858b4) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906257:1) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.173]
2018-12-07 10:15:26.95 spid1744    Remote harden of transaction 'user_transaction' (ID 0x000000008ead9cb8 0010:ab2858b7) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906258:27) failed.
2018-12-07 10:15:26.95 spid2445    Remote harden of transaction 'user_transaction' (ID 0x000000008eadc1e6 0010:ab2858b6) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906258:29) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.174]
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.173]
2018-12-07 10:15:26.95 spid1776    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcb80 0010:ab2858b8) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906268:62) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.178]
2018-12-07 10:15:26.95 spid2059    Remote harden of transaction 'user_transaction' (ID 0x000000008eadae7b 0010:ab2858b9) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906291:57) failed.
2018-12-07 10:15:26.95 spid2315    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcab4 0010:ab2858bb) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906313:39) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.179]
2018-12-07 10:15:26.95 spid994     Remote harden of transaction 'user_transaction' (ID 0x000000008eadc886 0010:ab2858ba) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906327:51) failed.
2018-12-07 10:15:26.95 spid20s     External dump process return code 0x20000001.
External dump process returned no errors.

2018-12-07 10:15:26.95 spid866     Remote harden of transaction 'user_transaction' (ID 0x000000008eadcb18 0010:ab2858bd) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906345:151) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.174]
2018-12-07 10:15:26.95 spid1635    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcbf3 0010:ab2858be) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906379:41) failed.
2018-12-07 10:15:26.95 spid1289    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcc56 0010:ab2858bf) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906394:31) failed.
2018-12-07 10:15:26.95 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.95 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.179]
2018-12-07 10:15:26.96 spid780     Remote harden of transaction 'user_transaction' (ID 0x000000008eadcbc4 0010:ab2858c0) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906405:47) failed.
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.173]
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.175]
2018-12-07 10:15:26.96 spid1782    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcc09 0010:ab2858c1) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906423:58) failed.
2018-12-07 10:15:26.96 spid2130    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcc3d 0010:ab2858c2) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906445:50) failed.
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.175]
2018-12-07 10:15:26.96 spid572     Remote harden of transaction 'user_transaction' (ID 0x000000008eada858 0010:ab2858c3) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906462:46) failed.
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.179]
2018-12-07 10:15:26.96 spid1048    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcc8f 0010:ab2858c4) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906479:29) failed.
2018-12-07 10:15:26.96 spid1800    Remote harden of transaction 'user_transaction' (ID 0x000000008eadc99d 0010:ab2858c5) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906490:30) failed.
2018-12-07 10:15:26.96 spid1388    Remote harden of transaction 'user_transaction' (ID 0x000000008eadcc6b 0010:ab2858c6) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906501:62) failed.
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.172]
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.173]
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.178]
2018-12-07 10:15:26.96 spid150     AlwaysOn: The local replica of availability group 'AGTP1' is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2018-12-07 10:15:26.96 spid881     Remote harden of transaction 'user_transaction' (ID 0x000000008eadcb2c 0010:ab2858c7) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906524:72) failed.
2018-12-07 10:15:26.96 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.96 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.175]
2018-12-07 10:15:26.96 spid1298    Remote harden of transaction 'user_transaction' (ID 0x000000008eadccaf 0010:ab2858ca) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906549:561) failed.
2018-12-07 10:15:26.96 spid718     Remote harden of transaction 'user_transaction' (ID 0x000000008ead234b 0010:ab2858cb) started at Dec  7 2018 10:15AM in database 'TP1' at LSN (957263:18906647:64) failed.
2018-12-07 10:15:26.97 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.97 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.173]
2018-12-07 10:15:26.97 spid20s     Error: 5901, Severity: 16, State: 1.
2018-12-07 10:15:26.97 spid20s     One or more recovery units belonging to database 'TP1' failed to generate a checkpoint. This is typically caused by lack of system resources such as disk or memory, or in some cases due to database corruption. Examine previous entries in the error log for more detailed information on this failure.
2018-12-07 10:15:26.97 spid20s     Error: 845, Severity: 17, State: 1.
2018-12-07 10:15:26.97 spid20s     Time-out occurred while waiting for buffer latch type 3 for page (16:880781), database ID 5.
2018-12-07 10:15:26.97 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.97 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.174]
2018-12-07 10:15:26.97 Logon       Error: 17191, Severity: 16, State: 2.
2018-12-07 10:15:26.97 Logon       Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors. [CLIENT: 192.168.28.172]
2018-12-07 10:15:26.98 spid35s     The availability group database "TP1" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.
2018-12-07 10:15:26.98 Server      Error: 10801, Severity: 16, State: 1.
2018-12-07 10:15:26.98 Server      Failed to stop the listener for Windows Failover Cluster resource '8b8c6680-2508-45a4-823b-5d91499ed14c'. Error: 87. The parameter is incorrect. 
2018-12-07 10:15:26.99 Backup      Error: 3041, Severity: 16, State: 1.

I am seeing a lot of latch wait on temp db but it is not on allocation pages ( gam,sgam,pfs). application is running a stored procedure frequently and it creates local temp table. Is there any way to reduce high latch wait events for non allocation pages in tempdb 

---

Thanks, Nithin

Hi All,

I restored a database from our PROD instance to reporting instance. While restoring through ssms i have selected the appropriate path in the "restore as" option and also selected standby mode. The DB is restored and is in standby mode and all users are able to access without any problem.

I checked with sys.sysaltfiles to see the path where exactly my mdf,ndfs and ldf are located. Its showing the path which is selected in the "restore as" option during restore. When i checked with the sys.database_files for the same DB, the physical filename which is see is the PROD DBs mdf,ndfs and ldf.

How it is possible to get two totally different physical paths for a DB when using sys.sysaltfiles and sys.database_files?

When i checked manually in the path which is selected in the "restore as" option, the files are created at the time i did the restore?

Im clueless about where exactly my datafiles and log file are now.

Thanks

hi, 

I am trying to list down all the hierarchies in a data sample, each hierarchy set having one id.

Data sample:

EmpId MgrId Dept

1	2	a
2	0	a
1	5	a
5	6	a
6	0	a
2	3	b
3	4	b
4	0	b

Expected Data: List down all the hirarchies present. All under one hieararchy should be of id 1, then next hierarchy of id 2 and so on..
Hierarchy	EmpID	Dept	MgrId	Root Mgr
1	1	a	2	2
1	2	a	0	2
2	1	a	5	6
2	5	a	6	6
2	6	a	0	6
3	2	b	3	4
3	3	b	4	4
3	4	b	0	4

thanks for the help.

---

To simplify the intended output:

thanks.

Have a SQL Server 2017 Standard edition box with build 14.0.3045.24 with one memory-optimized table. When our 3rd party backups or manual backups complete the SQL Server error log shows several [INFO] messages containingHKHostFreezeCkptTrimming(), HKHostBackupDeleteContext(), getMaxUnrecoverableCheckpointID() with the same user database ID. Are you familiar with these messages? Backups and restores are successful so it appears these are innocuous messages, but had us initially concerned. Is this something common as part of using In-Memory OLTP and I should get used to seeing it in my logs? Look forward to your feedback. Thanks!

I have a linked server defined on a SQL Server 2005 SP2 standard edition server using the IBMDASQL OLEDB driver. The linked server has been defined and working for months when used from a SQL Server authenticated session. I started converting our developers to Windows Authentication and access to the linked server is denied when used from a Windows Authenticated session. Here are the error messages:

 

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "IBMDASQL" for linked server "DB2ARUBA" reported an error. Access denied.

Msg 7350, Level 16, State 2, Line 1

Cannot get the column information from OLE DB provider "IBMDASQL" for linked server "DB2ARUBA".

 

The linked server security is defined to login to the IBM iSeries using a fixed user and password regardless of the login using the linked server.

 

In order to analyze the problem, I created one sysadmin SQL Server authenticated login and one sysadmin Windows Authenticated login. The Windows Authenticated login refers to a domain login having administrator priviledges on the local SQL Server box.

 

So, when I connect to SQL Server using the SQL Authenticated login, a query against the linked server works. When I connect to SQL Server using the Windows Authenticated login, the exact same query against the linked server fails with the messages above.

 

Does anyone know why?

 

Hi,

I need to plan a SQL Server 2017 Standard Edition installation: does this edition support the Management --> Maintenance Plans without installing Integration Services?

Thanks

Hi all,

I need some guidance regarding extracting table changes within SQL server. I am performing work on a client where I identified a segregation of duties issue on the database. In order to perform impact testing and determine if any unauthorised changes have been made, they provided me with a list of object changes to the database. They had challenges proving that each object change could be tied back to their ticketing system, so they provided an extract of release scripts executed instead and tied back each release script executed to an authorised ticket. When doing further analysis i noted that there were instances where an object change was made but nothing was recorded on the release script output for that day. I queried it with them and they mentioned that the object change report provided actually covers changes to components rather than tables. Component changes are more related to services not data or source code changes, and that the only what to make changes to a SQL database is by running these release scripts. I feel that they might not be giving me the correct information, and I am not comfortable just using the release script information because it does not give comfort that those were all the table changes made. Can anyone please provide some guidance on how best to approach this situation. Your input would be greatly appreciated.

Hi

what is the best way to transfer a table data from MS Access 2013 to an SQL database table?

Thanks

Marco Dell'Oca

So I created an index maintenance for some of our tables. 

I used the REORG >5 but < 30 and REBUILD > 30 based on the avg fragmentation.

After the maintenance, an existing query that runs for 19 minutes now does not terminate. What am I missing here?

TIA

select * 
from orders_products op  
join mart_cpa_items c on 
c.price  = op.price 

error:

Cannot convert a char value to money. The char value has incorrect syntax.

select price from mart_cpa_items       --nvarchar  (this column contains some char data that cannot convert into money right?)

select price from orders_products       --money

Hi Experts，

How to edit the SQL Server instance name? I tried but failed.

Thanks in advance.

I am asking about if I have always-on AG

and I have a passive replica( non-readable)

as long as <g class="gr_ gr_132 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="132" id="132">i</g> know, the license will not count this node

the question is: what will happen if failover went to this replica 

and what about the license then, <g class="gr_ gr_259 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="259" id="259">i</g> mean when setup SQL server on this node, what key <g class="gr_ gr_260 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="260" id="260">i</g> use to have licensed version on it

I'm getting an error while operating the SQL server. It displays as SQL server error 5171. I'm not able to resolve this error. Please, somebody, help me get out of this.

We are creating a new Database which has very less disk space . we have two tables where the data loads frequently. Retention period for this data is five years.

We have created monthly partitions for this table. and have created 12 file groups which will  be reused by new partitions.

We created a process which delete the partitions with data older than 5  year and  new partitions for the next month is created .This process runs every month.

we need to create a new process when ever there is a warning for low disk space. we need to delete the oldest partition with data.

But we  really missed out the point that deleting partition wont free  the disk space.So we have thought of creating file groups dynamically for each month and assigning this file groups to the respective partition of that month.When we delete the partition the file should also be deleted along with it.

I just need need to know is there any problem in doing this?

i didn't find any related links which do the same.Can anyone give an input on how to handle this inside a sliding window partitioning Logic..

My email server and agent operators are configured properly in the instance.  If I define an operator with semi colon separated emails (I read there is a 100 char max) they all get notified as intended.  If I place an outlook email group that never works.  It seems to never get resolved and passed on for email notification,  Below are 3 different valid ways to reference the email group RTFF_DB in an outlook email.  None of these work as emails within a operator definition.  Does anyone know why?  Is something validating them outside of outlook and never passing them on for email notifications?

RTFF_DB                                    (never failed and never delivered)

RTFF_DB@hpd.nyc.gov                 (failed as undelivered)

RTFF_DB <RTFF_DB@hpd.nyc.gov> (failed as undelivered)

Thanks,

DBATony

---

Tony C

I would like to use the tool introduced in SSMS 2017 "Static Data Masking".

I need to mask a table, but since the column I mask is referenced by other table, I have to make sure that the new masking value will be same on both tables.

how do I accomplish this?

SELECT 
	c.company_name,
	count(e.employee_id) as total_persons,
	sum(s.salary) as total_salary,
	sum(f.total) as ffot
  FROM [payroll].[dbo].[employee] e
	Left join [payroll].[dbo].[facilities] f on f.employee_id = e.employee_id,
	[payroll].[dbo].[company] c,
	   [payroll].[dbo].[salary] s
	where e.company_id = c.company_id and s.employee_id = e.employee_id
	and s.salary_month = '2018-04-01'
	group by c.company_name

Here is just salary table

salary_id                      salary_month      employee_id       salary        arrears_payment           source

11                    2018-05-01        7                27500.0027500.00         office
12                    2018-05-01        3                45000.0045000.00         bank

According to query result is:-

company_name total_persons        total_salaryffot
ABC                           1                            45000.00          4500.00

XYZ                           1                            27500.00           1500.00

But I want to get Like this:-

company_name total_persons        total_salaryffot            Office                Bank
ABC                           1                            45000.00          4500.00           0  or empty              45000.00

XYZ                           1                            27500.00           1500.00         27500.00                   0    or  empty

I fetched record from multiple tables but here i mentioned just where i have issue