Getting below error while working on Microsoft Virtual Lab:
https://technet.microsoft.com/en-us/virtuallabs
System Name : SQL Two
"unable to save the alwayson high availability settings return code 0x80070046"
Getting above error while enabling Always on Availability group from SQL Server Configuration Manager.
I have spent hours trying to figure why so many articles say, or imply, that restoring a crash-consistent snapshot backup (one made without invoking VSS) can lead to data loss on a VM running SQL Server. I understand that, of course, any in-flight transactions would be lost, and that restart could take a long time if there were large transaction in flight. But what, if any, reasonable scenario would lead to corruption of the database?
To further confuse the matter, I found one (rather old) Dell vRanger support article which says that crash-consistent backups are OK but using a file-system quiesce without invoking SQL VSS can corrupt SQL Server. Huh?
To put the same question another way, if I suddenly pull the plug on a standalone physical SQL server, or a physical VMware host running SQL Server on a VM, might a database fail to come online when the server is restarted? If yes, why? I ask because I am expecting SQL server automatic database recovery to work every time.
Hi All,
When i am trying to use AlwaysOn in microsoft virtual lab i am not able to enable the AlwaysOn in the sqlserver services properties. Please help me how can i fix.
Thanks,
Suresh
Hi
I have a standalone SQL Enterprise 2012 running on windows 2012 server.
I would like to deploy AAG (always on availability groups).
Is it possible for me to do so? I mean can I install and configure AAG on theexisting server and then work on adding other SQL servers in the group?
More information is deeply appreciated.
Thank you
Hi Everyone,
Log shipping standby database went to restoring state, and the mdf and ldf of the database files are configured in to default drive D in my server. Currently the drive shows out of disk space 0 bytes showing. This drive also having all system DB files.
I checked error log and found the following issue : Operating system error 112(There is not enough space on the disk.) encountered. Error: 17053, Severity: 16, State: 1.
What I noticed is some one restarted the stand by server without knowing me after that only this issue found!
We don't have any chance to increase the D drive, please suggest me what are the steps I need to get back the database into standby mode.
Thanks,
V
DBA
On SQL Server 2008 Standard license.
I have just tested DB Mirroring with witness with the following setup:
Server A - Principal, Server B -
Mirror, Server C - Witness, Client
So I ran an insert of 100000 rows from Client connecting to Server A. At about 10k, I killed the services in Server A (simulatingServer A crashes), my connection on Client was terminated as well.
With the witness, it did automatically make Server B the principal. I was able to connect toServer B and query / insert / etc.
My question is,
1) Is there a way to set up DB Mirroring so the traffic automatically re-route toServer B?
2) If not, what are my options to re-route traffic to Server B and continues to insert toServer B, keeping in mind this is SQL2008.
Thank you.
Hi, my setup is:
2 servers, each with multiple named instances, on one instance I have set up an AG between the two servers.
I am trying to add a new AG on the same instances, but when I try to add the secondary replica, when I go to "join to availability group" I get the error:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to join the instance 'server\ins02' to the availability group 'agname'. (Microsoft.SqlServer.Management.SDK.TaskForms)
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Failed to join local availability replica to availability group 'OSLAGSSM001P'. The operation encountered SQL Server error 41106 and has been rolled back. Check the SQL Server error log for more details. When the cause of the error has been resolved, retry the ALTER AVAILABILITY GROUP JOIN command. (Microsoft SQL Server, Error: 41158)
So we encountered a scenario some time back (unfortunately I should have done this sooner, and the details may be a little fuzzy) and I've been tasked with being able account for it going forward.
We have a two node, synchronous Availability Group that does NOT fail over automatically. This environment is an 8 terabyte data warehouse. Every night about 1500 jobs run that gather data from lots of different sources.
We had maintenance occur in this environment and the developers didn't stop their jobs before the maintenance started. Our SA did maintenance on the Primary first, and then on the Secondary. Once the Secondary came back online, it was in an In Recovery state for a while (like 30 - 45 minutes) before it was finally usable. During this time of course the developers wanted to restart their jobs, and I told them "no". My logic being that I didn't want the transaction log on the Primary to fill up. Since it can't truncate until all the data is committed on the Secondary, and since the Secondary was already behind, I didn't want to make matters worse. Of course I was loved by some and hated by others for this decision, but that's the life of a DBA.
DMV's are accumulative since the last restart. The Dashboard, while useful, doesn't really allow me to tell people how long until they can restart their jobs. So what can be used to make this determination?
Thanks!
Thanks in advance! ChrisRDBA
Hi
I have 2 sites ( London & Paris)
I want to make high SQL Always on availability Group
2 SQL FCI on each site and between sites i have to create SQL always on availability group .
shall all application connected to availability group?
if the availability group active in London , can i make all applications in Paris connected to read only Database copy in Paris ? how can we do that ?
MCP MCSA MCSE MCT MCTS CCNA
Hello,
We have, clustered SQL server 2012 (11.0.6518.0 - SP3 + CU1). It has 2 nodes. Recently cluster has begun hanging up for 1 minute. This is critical to our business application. There is no any suspicious records in Application or System logs. Also MS SQL itself does not have any alerts. We've disabled failover for this resource, cause we thought it is cluster malfunction, but it did not help.
Any suggestions?
Cluster logs:
00002064.000023e4::2016/03/14-13:31:01.649 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:f50684d8-cf67-4354-a024-9f3676c9f40f:Netbios
00002064.000023e4::2016/03/14-13:31:01.688 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:510e4d82-fe8b-43b0-ad3c-b3c6e1a44a18:Netbios
00002064.000023e4::2016/03/14-13:31:01.691 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:510e4d82-fe8b-43b0-ad3c-b3c6e1a44a18:Netbios
00001e48.000081c0::2016/03/14-13:31:03.672 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] SQLMoreResults() returns -1 with following information
00001e48.000081c0::2016/03/14-13:31:03.672 ERR [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] ODBC Error: [HYT00] [Microsoft][SQL Server Native Client 11.0]Query timeout expired (0)
00001e48.000081c0::2016/03/14-13:31:03.672 ERR [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] ODBC Error: [01000] [Microsoft][SQL Server Native Client 11.0][SQL Server] (0)
00001e48.000081c0::2016/03/14-13:31:03.672 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] No more diagnostics results
00001e48.000081c0::2016/03/14-13:31:03.672 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Discard the pending result sets
00001e48.000081c0::2016/03/14-13:31:03.672 ERR [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] ODBC Error: [24000] [Microsoft][SQL Server Native Client 11.0]Invalid cursor state (0)
00001e48.000081c0::2016/03/14-13:31:03.672 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Diagnostics is stopped
00001e48.000072d0::2016/03/14-13:31:03.672 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Online worker helper is stopped
00001e48.000081c0::2016/03/14-13:31:03.673 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Cancel SQL request
00001e48.000081c0::2016/03/14-13:31:03.673 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Free SQL statement
00001e48.000081c0::2016/03/14-13:31:03.673 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Disconnect from SQL Server
00002064.000023e4::2016/03/14-13:31:03.803 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:efae3259-7e02-4550-988b-079e036e0485:Netbios
00001e48.000081c0::2016/03/14-13:31:04.684 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Connection string is 'Driver={SQL Server Native Client 11.0};Database=master;Server=cluster_address\INSTANCE_NAME;Trusted_Connection=yes'
00001e48.000081c0::2016/03/14-13:31:04.684 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] SQL_ATTR_LOGIN_TIMEOUT (30s) SQL_ATTR_CONNECTION_TIMEOUT (30s) SQL_ATTR_QUERY_TIMEOUT (30s)
00001e48.000081c0::2016/03/14-13:31:04.685 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Connect to SQL Server ...
00001e48.000081c0::2016/03/14-13:31:04.725 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] The connection was established successfully
00001e48.000081c0::2016/03/14-13:31:04.725 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Run 'EXEC sp_server_diagnostics 20'
00001e48.000081c0::2016/03/14-13:31:04.893 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Set query timeout to 60
00001e48.000081c0::2016/03/14-13:31:04.893 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Diagnostics is started
00001e48.000081c0::2016/03/14-13:31:04.893 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] SQL Server component 'system' health state has been changed from '' to 'clean' at 2016-03-14 16:31:04.887
00001e48.00009960::2016/03/14-13:31:04.893 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] Online worker helper is started
00001e48.000081c0::2016/03/14-13:31:04.913 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] SQL Server component 'resource' health state has been changed from '' to 'clean' at 2016-03-14 16:31:04.887
00001e48.000081c0::2016/03/14-13:31:04.923 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] SQL Server component 'query_processing' health state has been changed from '' to 'warning' at 2016-03-14 16:31:04.887
00001e48.000081c0::2016/03/14-13:31:04.923 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] SQL Server component 'io_subsystem' health state has been changed from '' to 'clean' at 2016-03-14 16:31:04.887
00001e48.000081c0::2016/03/14-13:31:04.929 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] SQL Server component 'events' health state has been changed from '' to 'unknown' at 2016-03-14 16:31:04.887
00002064.000090b0::2016/03/14-13:31:05.106 INFO [RES] Network Name <MSDTC_CL>: Dns: HealthCheck: MSDTC_CL
00002064.000090b0::2016/03/14-13:31:05.106 INFO [RES] Network Name <MSDTC_CL>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00001e48.00009768::2016/03/14-13:31:05.904 INFO [RES] SQL Server <SQL SERVER (INSTANCE_NAME)>: [sqsrvres] LooksAlive returns TRUE
Hi,
I have two servers (primary) with several databases. I would like to know if I can use onlyone server (Secondary) to configure a Synchronous AlwaysON failover?
SAMPLE
Thanks,
JL
We have SQL 2014 Enterprise edition (RTM) running with three availability replicas. Two are for failover, the third is for read only copies for reporting.
The issue we're having is that on a failover between the two read/write replicas is that the owner is changing from SA to one of our DBAs AD accounts. I think it's going to the person that originally created the database, but not 100% certain. We need to keep SA as the owner due to some CLR code that performs some encryption. When the owner changes, the CLR code doesn't work.
We can (and will) run a script upon failover to reset owners, but I find it strange that SQL changes owners when we failover.
Has anyone seen this problem?
Thanks,
Rick
Hi All
We have a PRD-CRM database in our organization. Few days back, our application production team started complaining of slow performance. Once the case was analysed, this appeared to be occurring due to higher percentage level of fragmentation in the tables of this database. So, correspondingly, we re-indexed the database tables. Once we completed the task and checked again the avg fragmentation level, it was fine, but my database size grew by more than 100 GB.
So, my query is that "whether we can do something to resist the increase in size of database after re-indexing".
Hi all,
I have a problem with a sql 2012 build on server 2012 cluster. The cluster has 2 nodes. Node 1 is active and here are a few DB for SCCM and SCOM. Unfortunately the server is very busy to serve this to apps. So I have tried to move from cluster sccm instance to node 2. I have Checked the logs on node 2 and I have a few errors related to spn registration and nothing more. In SCCM log I have:
*** [HY000][-2146893022][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The target principal name is incorrect. SMS_DATABASE_NOTIFICATION_MONITOR 21/03/2016 16:49:19 17208 (0x4338)
*** [HY000][-2146893022][Microsoft][SQL Server Native Client 11.0]Cannot generate SSPI context SMS_DATABASE_NOTIFICATION_MONITOR 21/03/2016 16:49:19 17208 (0x4338)
*** [HY000][-2146893022][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The target principal name is incorrect. SMS_DATABASE_NOTIFICATION_MONITOR 21/03/2016 16:49:19 17208 (0x4338)
*** [HY000][-2146893022][Microsoft][SQL Server Native Client 11.0]Cannot generate SSPI context SMS_DATABASE_NOTIFICATION_MONITOR 21/03/2016 16:49:19 17208 (0x4338)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_DATABASE_NOTIFICATION_MONITOR 21/03/2016 16:49:19 17208 (0x4338)
Logs from node 2:
Date,Source,Severity,Message 03/21/2016 16:46:37,spid5s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. 03/21/2016 16:46:37,spid5s,Unknown,SQL Server shutdown has been initiated 03/21/2016 16:46:37,spid5s,Unknown,.NET Framework runtime has been stopped. 03/21/2016 16:46:37,spid22s,Unknown,Service Broker manager has shut down. 03/21/2016 16:46:37,spid22s,Unknown,The Service Broker endpoint has stopped listening for connections. 03/21/2016 16:46:37,spid5s,Unknown,SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 03/21/2016 16:46:37,spid52,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 03/21/2016 16:46:37,spid52,Unknown,Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install. 03/21/2016 16:46:37,spid52,Unknown,Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 03/21/2016 16:33:00,spid5s,Unknown,Recovery is complete. This is an informational message only. No user action is required. 03/21/2016 16:33:00,spid21s,Unknown,Recovery completed for database CM_CAM (database ID 5) in 2 second(s) (analysis 60 ms<c/> redo 2072 ms<c/> undo 106 ms.) This is an informational message only. No user action is required. 03/21/2016 16:32:59,spid21s,Unknown,Recovery is writing a checkpoint in database 'CM_CAM' (5). This is an informational message only. No user action is required. 03/21/2016 16:32:59,spid21s,Unknown,3 transactions rolled back in database 'CM_CAM' (5:0). This is an informational message only. No user action is required. 03/21/2016 16:32:59,spid21s,Unknown,325 transactions rolled forward in database 'CM_CAM' (5:0). This is an informational message only. No user action is required. 03/21/2016 16:32:59,spid52,Unknown,Using 'xplog70.dll' version '2011.110.5058' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required. 03/21/2016 16:32:59,spid52,Unknown,Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required. 03/21/2016 16:32:59,spid52,Unknown,Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required. 03/21/2016 16:32:59,spid52,Unknown,Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required. 03/21/2016 16:32:59,spid52,Unknown,Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required. 03/21/2016 16:32:59,spid52,Unknown,Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required. 03/21/2016 16:32:58,spid52,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 03/21/2016 16:32:58,spid52,Unknown,Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install. 03/21/2016 16:32:58,spid52,Unknown,Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 03/21/2016 16:32:58,spid22s,Unknown,Service Broker manager has started. 03/21/2016 16:32:58,spid22s,Unknown,The Database Mirroring endpoint is in disabled or stopped state. 03/21/2016 16:32:58,spid22s,Unknown,The Service Broker endpoint is now listening for connections. 03/21/2016 16:32:58,spid22s,Unknown,Started listening on virtual network name 'dbinstance'. No user action is required. 03/21/2016 16:32:58,spid22s,Unknown,Server is listening on [ 10.64.15.113 <ipv4> 4022]. 03/21/2016 16:32:58,spid7s,Unknown,Starting up database 'tempdb'. 03/21/2016 16:32:58,spid21s,Unknown,Recovery of database 'CM_CAM' (5) is 8% complete (approximately 3 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid21s,Unknown,Recovery of database 'CM_CAM' (5) is 0% complete (approximately 257 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid7s,Unknown,Clearing tempdb database. 03/21/2016 16:32:57,spid7s,Unknown,Starting up database 'model'. 03/21/2016 16:32:57,spid20s,Unknown,Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid20s,Unknown,0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid20s,Unknown,5 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid7s,Unknown,The resource database build version is 11.00.5058. This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid7s,Unknown,Starting up database 'mssqlsystemresource'. 03/21/2016 16:32:57,spid21s,Unknown,Starting up database 'CM_CAM'. 03/21/2016 16:32:57,spid20s,Unknown,Starting up database 'msdb'. 03/21/2016 16:32:57,spid16s,Unknown,A new instance of the full-text filter daemon host process has been successfully started. 03/21/2016 16:32:57,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/dbinstance.office.local:1433 ] for the SQL Server service. Windows return code: 0x2098<c/> state: 20. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 03/21/2016 16:32:57,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/dbinstance.office.local:dbinstance ] for the SQL Server service. Windows return code: 0x2098<c/> state: 20. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 03/21/2016 16:32:57,Server,Unknown,SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required. 03/21/2016 16:32:57,spid11s,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required. 03/21/2016 16:32:57,spid11s,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\server\db\sql\query ]. 03/21/2016 16:32:57,spid11s,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\dbinstance ]. 03/21/2016 16:32:57,spid11s,Unknown,Started listening on virtual network name 'dbinstance'. No user action is required. 03/21/2016 16:32:57,spid11s,Unknown,Server is listening on [ 10.64.15.113 <ipv4> 1433]. 03/21/2016 16:32:57,Server,Unknown,Software Usage Metrics is enabled. 03/21/2016 16:32:57,spid11s,Unknown,The certificate [Cert Hash(sha1) "2EE9A5E0022CBA676D376DF12912478C44DEF741"] was successfully loaded for encryption. 03/21/2016 16:32:57,spid5s,Unknown,The NETBIOS name of the local node that is running the server is 'DUBNGSCOMSQL02'. This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid5s,Unknown,Server name is 'dbinstance\dbinstance'. This is an informational message only. No user action is required. 03/21/2016 16:32:57,spid5s,Unknown,SQL Trace ID 1 was started by login "sa". 03/21/2016 16:32:57,spid5s,Unknown,SQL Server Audit has started the audits. This is an informational message. No user action is required. 03/21/2016 16:32:57,spid5s,Unknown,SQL Server Audit is starting the audits. This is an informational message. No user action is required. 03/21/2016 16:32:57,spid5s,Unknown,Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details. 03/21/2016 16:32:56,Server,Unknown,Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 03/21/2016 16:32:56,Server,Unknown,CLR version v4.0.30319 loaded. 03/21/2016 16:32:56,spid5s,Unknown,Starting up database 'master'. 03/21/2016 16:32:56,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 03/21/2016 16:32:56,Server,Unknown,Node configuration: node 1: CPU mask: 0x00000000000000f0:0 Active CPU mask: 0x00000000000000f0:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 03/21/2016 16:32:56,Server,Unknown,Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 03/21/2016 16:32:56,Server,Unknown,This instance of SQL Server last reported using a process ID of 13068 at 21/03/2016 16:32:45 (local) 21/03/2016 16:32:45 (UTC). This is an informational message only; no user action is required. 03/21/2016 16:32:56,Server,Unknown,Using conventional memory in the memory manager. 03/21/2016 16:32:56,Server,Unknown,Detected 16371 MB of RAM. This is an informational message; no user action is required. 03/21/2016 16:32:56,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 03/21/2016 16:32:56,Server,Unknown,SQL Server detected 2 sockets with 4 cores per socket and 4 logical processors per socket<c/> 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 03/21/2016 16:32:56,Server,Unknown,Command Line Startup Parameters:<nl/> -s "dbinstance" 03/21/2016 16:32:56,Server,Unknown,Registry startup parameters: <nl/> -d S:\MSSQL11.dbinstance\MSSQL\DATA\master.mdf<nl/> -e S:\MSSQL11.dbinstance\MSSQL\Log\ERRORLOG<nl/> -l S:\MSSQL11.dbinstance\MSSQL\DATA\mastlog.ldf<nl/> -T 8295<nl/> -T 4199 03/21/2016 16:32:56,Server,Unknown,The service account is 'OFFICE\ngscomsqladmin'. This is an informational message; no user action is required. 03/21/2016 16:32:56,Server,Unknown,Logging SQL Server messages in file 'S:\MSSQL11.dbinstance\MSSQL\Log\ERRORLOG'. 03/21/2016 16:32:56,Server,Unknown,Authentication mode is MIXED. 03/21/2016 16:32:56,Server,Unknown,System Manufacturer: 'Dell Inc.'<c/> System Model: 'PowerEdge R710'. 03/21/2016 16:32:56,Server,Unknown,Server process ID is 9880. 03/21/2016 16:32:56,Server,Unknown,All rights reserved. 03/21/2016 16:32:56,Server,Unknown,(c) Microsoft Corporation. 03/21/2016 16:32:56,Server,Unknown,Microsoft SQL Server 2012 - 11.0.5058.0 (X64) <nl/> May 14 2014 18:34:29 <nl/> Copyright (c) Microsoft Corporation<nl/> Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
Date,Source,Severity,Message 03/21/2016 16:57:34,spid6s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. 03/21/2016 16:57:34,spid6s,Unknown,SQL Server shutdown has been initiated 03/21/2016 16:57:34,spid6s,Unknown,.NET Framework runtime has been stopped. 03/21/2016 16:57:34,spid22s,Unknown,Service Broker manager has shut down. 03/21/2016 16:57:34,spid22s,Unknown,The Service Broker endpoint has stopped listening for connections. 03/21/2016 16:57:33,spid6s,Unknown,SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 03/21/2016 16:57:33,spid52,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 03/21/2016 16:57:33,spid52,Unknown,Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install. 03/21/2016 16:57:33,spid52,Unknown,Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 03/21/2016 16:46:41,spid52,Unknown,Using 'xplog70.dll' version '2011.110.5058' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required. 03/21/2016 16:46:41,spid52,Unknown,Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required. 03/21/2016 16:46:41,spid52,Unknown,Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required. 03/21/2016 16:46:41,spid52,Unknown,Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required. 03/21/2016 16:46:41,spid52,Unknown,Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required. 03/21/2016 16:46:41,spid52,Unknown,Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required. 03/21/2016 16:46:41,spid6s,Unknown,Recovery is complete. This is an informational message only. No user action is required. 03/21/2016 16:46:40,spid52,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 03/21/2016 16:46:40,spid52,Unknown,Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install. 03/21/2016 16:46:40,spid52,Unknown,Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 03/21/2016 16:46:40,spid22s,Unknown,Service Broker manager has started. 03/21/2016 16:46:40,spid22s,Unknown,The Database Mirroring endpoint is in disabled or stopped state. 03/21/2016 16:46:40,spid22s,Unknown,The Service Broker endpoint is now listening for connections. 03/21/2016 16:46:40,spid22s,Unknown,Started listening on virtual network name 'dbinstance'. No user action is required. 03/21/2016 16:46:40,spid22s,Unknown,Server is listening on [ 10.64.15.113 <ipv4> 4022]. 03/21/2016 16:46:40,spid7s,Unknown,Starting up database 'tempdb'. 03/21/2016 16:46:40,spid7s,Unknown,Clearing tempdb database. 03/21/2016 16:46:40,spid7s,Unknown,Starting up database 'model'. 03/21/2016 16:46:39,spid7s,Unknown,The resource database build version is 11.00.5058. This is an informational message only. No user action is required. 03/21/2016 16:46:39,spid7s,Unknown,Starting up database 'mssqlsystemresource'. 03/21/2016 16:46:39,spid21s,Unknown,Starting up database 'CM_CAM'. 03/21/2016 16:46:39,spid20s,Unknown,Starting up database 'msdb'. 03/21/2016 16:46:39,spid16s,Unknown,A new instance of the full-text filter daemon host process has been successfully started. 03/21/2016 16:46:39,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/dbinstance.domain.local:1433 ] for the SQL Server service. Windows return code: 0x2098<c/> state: 20. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 03/21/2016 16:46:39,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/dbinstance.domain.local:dbinstance ] for the SQL Server service. Windows return code: 0x2098<c/> state: 20. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 03/21/2016 16:46:39,Server,Unknown,SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required. 03/21/2016 16:46:39,spid11s,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required. 03/21/2016 16:46:39,spid11s,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\dbinstance\MSSQL$dbinstance\sql\query ]. 03/21/2016 16:46:39,spid11s,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\dbinstance ]. 03/21/2016 16:46:39,spid11s,Unknown,Started listening on virtual network name 'dbinstance'. No user action is required. 03/21/2016 16:46:39,spid11s,Unknown,Server is listening on [ 10.64.15.113 <ipv4> 1433]. 03/21/2016 16:46:39,Server,Unknown,Software Usage Metrics is enabled. 03/21/2016 16:46:39,spid11s,Unknown,The certificate [Cert Hash(sha1) "2EE9A5E0022CBA676D376DF12912478C44DEF741"] was successfully loaded for encryption. 03/21/2016 16:46:39,spid6s,Unknown,The NETBIOS name of the local node that is running the server is 'DUBNGSCOMSQL02'. This is an informational message only. No user action is required. 03/21/2016 16:46:39,spid6s,Unknown,Server name is 'dbinstance\dbinstance'. This is an informational message only. No user action is required. 03/21/2016 16:46:39,spid6s,Unknown,SQL Trace ID 1 was started by login "sa". 03/21/2016 16:46:39,spid6s,Unknown,SQL Server Audit has started the audits. This is an informational message. No user action is required. 03/21/2016 16:46:39,spid6s,Unknown,SQL Server Audit is starting the audits. This is an informational message. No user action is required. 03/21/2016 16:46:39,spid6s,Unknown,Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details. 03/21/2016 16:46:39,Server,Unknown,Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 03/21/2016 16:46:39,Server,Unknown,CLR version v4.0.30319 loaded. 03/21/2016 16:46:39,spid6s,Unknown,Starting up database 'master'. 03/21/2016 16:46:39,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 03/21/2016 16:46:39,Server,Unknown,Node configuration: node 1: CPU mask: 0x00000000000000f0:0 Active CPU mask: 0x00000000000000f0:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 03/21/2016 16:46:39,Server,Unknown,Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 03/21/2016 16:46:39,Server,Unknown,This instance of SQL Server last reported using a process ID of 9880 at 21/03/2016 16:46:37 (local) 21/03/2016 16:46:37 (UTC). This is an informational message only; no user action is required. 03/21/2016 16:46:38,Server,Unknown,Using conventional memory in the memory manager. 03/21/2016 16:46:38,Server,Unknown,Detected 16371 MB of RAM. This is an informational message; no user action is required. 03/21/2016 16:46:38,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 03/21/2016 16:46:38,Server,Unknown,SQL Server detected 2 sockets with 4 cores per socket and 4 logical processors per socket<c/> 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 03/21/2016 16:46:38,Server,Unknown,Command Line Startup Parameters:<nl/> -s "dbinstance" 03/21/2016 16:46:38,Server,Unknown,Registry startup parameters: <nl/> -d S:\MSSQL11.dbinstance\MSSQL\DATA\master.mdf<nl/> -e S:\MSSQL11.dbinstance\MSSQL\Log\ERRORLOG<nl/> -l S:\MSSQL11.dbinstance\MSSQL\DATA\mastlog.ldf<nl/> -T 8295<nl/> -T 4199 03/21/2016 16:46:38,Server,Unknown,The service account is 'domain\ngscomsqladmin'. This is an informational message; no user action is required. 03/21/2016 16:46:38,Server,Unknown,Logging SQL Server messages in file 'S:\MSSQL11.dbinstance\MSSQL\Log\ERRORLOG'. 03/21/2016 16:46:38,Server,Unknown,Authentication mode is MIXED. 03/21/2016 16:46:38,Server,Unknown,System Manufacturer: 'Dell Inc.'<c/> System Model: 'PowerEdge R710'. 03/21/2016 16:46:38,Server,Unknown,Server process ID is 8476. 03/21/2016 16:46:38,Server,Unknown,All rights reserved. 03/21/2016 16:46:38,Server,Unknown,(c) Microsoft Corporation. 03/21/2016 16:46:38,Server,Unknown,Microsoft SQL Server 2012 - 11.0.5058.0 (X64) <nl/> May 14 2014 18:34:29 <nl/> Copyright (c) Microsoft Corporation<nl/> Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
We have configured Log Shipping for our databases that reside on a SQL2012 cluster. Everything is working fine from a synchronicity perspective, but we are seeing a 16 second delay from the LS Backup job starting to the Log Shipping Agent doing its business.
We wrote some simple SQL to help demonstrate this,
DECLARE @CMDvarchar(4000)
SET @CMD='"C:\Program Files\Microsoft SQL Server\110\Tools\Binn\sqllogship.exe" -Backup <OUR_PRIMARY_ID> -server <OUR_SERVER>'
SELECTGETDATE()
EXECxp_cmdshell@CMD
SELECTGETDATE()
You can see a 16 second delay from the initial timestamp to the START OF TRANSACTION LOG BACKUP timestamp:
-----------------------
2016-03-22 09:24:06.793
-----------------------
NULL
Microsoft (R) SQL Server Log Shipping Agent
[Assembly Version = 11.0.0.0, File Version = 11.0.6020.0 ((SQL11_PCU_Main).151020-1526 )]
Copyright (c) 2012 Microsoft. All rights reserved.
NULL
2016-03-22 09:24:22.07 ----- START OF TRANSACTION LOG BACKUP -----
2016-03-22 09:24:22.21 Starting transaction log backup. Primary ID: '35bbb26c-fc9b-452d-b930-360153334d6d'
2016-03-22 09:24:22.22 Retrieving backup settings. Primary ID: '35bbb26c-fc9b-452d-b930-360153334d6d'
2016-03-22 09:24:22.22 Retrieved backup settings. Primary Database: 'testLS', Backup Directory: '\\servername\Backups\servername\instance_CM\testLS\LOG', Backup Retention Period: 4320 minute(s), Backup Compression: Server Default
2016-03-22 09:24:22.29 Backing up transaction log. Primary Database: 'testLS', Log Backup File: '\\servername \Backups\servername\instance_CM\testLS\LOG\testLS_20160322092422.trn'
2016-03-22 09:24:22.43 Deleting old log backup files. Primary Database: 'testLS'
2016-03-22 09:24:22.50 The backup operation was successful. Primary Database: 'testLS', Log Backup File: '\\servername \Backups\servername \instance _CM\testLS\LOG\testLS_20160322092422.trn'
2016-03-22 09:24:22.51 ----- END OF TRANSACTION LOG BACKUP -----
NULL
Exit Status: 0 (Success)
NULL
-----------------------
2016-03-22 09:24:22.640
Hi All,
I have found that in some of our database cluster the service account is by default the sysadmin of that instance, however it is not the case with all the DB Clusters.
Is it because someone has deliberately made that account a 'sysadmin'?
Account_name e.g.: domain\serviceaccount
SQL version: SQL 2008
Windows Version: Windows 2008R2
aa
Hi
I have 2 sites and each site shall i have 2 sql servers with hight availabilty
I want to make under each site SQL always on FCI and between the 2 sites i need to do sql always on availability group
i need the steps to do that
My application will connect on the availability group listener .
I need recommendation and consideration regarding this design also .
MCP MCSA MCSE MCT MCTS CCNA
Hi,
I have got SQL server 2012 cluster with nodes, only one instance is hosted on the cluster.
I am facing a problem that the Quorum disk node did not change after moving SQL instance from one node to another.
Any idea how to resolve this issue ?
Regards,
Tarek
Hello Guys,
I have an SQL Server 2012 DAG running on top of a Windows Server 2012 Failover Cluster.
Today (suddenly), i was faced to an irregular issue when i want to manual failover the DAG from a node to another.
My nodes Names are SQL11 and SQL12, and I’m using the failover wizard from the SQL Server MS.
- When i failover the DAG from SQL11 to SQL12, all is good.
-When i want to get back the DAG to SQL11 (From SQL12 to SQL11), i receive the following error message:
--------------------------------
Manual Failover failed.
Error Message:Availability-group DDL operations are permitted
only when you are using the master database. Run the USE MASTER
command, and retry your availability-group DDL command.
-------------------------------------------
It's really obvious because i can't find any explanation to this issue.
I really appreciate your help.
Thanks
Regards, Samir Farhat Infrastructure Consultant
During restoration of database in test environment we face below issue once database gets set too single user mode.
Only user processes can be killed. Database is already open and can only have one user at a time.
Nothing worked from below steps.
-We tried to kill all session.
-We tried to put database offline.
-We tried to put database in multiuser mode.
-We tried database files attach-detach.
-We tried to wait till system process gets released still sessions not getting released.
-Last option : Restart database server which is not feasible each time.
Hoping for better assistance as issue seems not getting resolved with any available option except restart.