Hello,I have SQL server 2008 x64 and backup all my databases by using Symantec netbackup 7.5

recently I was trying to restore one of databases and every time I got the following error I did DBCC CHECKDB against the db and got no error but my restore always fail wil below msg

Last modified time: 4/6/2016 7:51:16 AM

Alert description: Event Description: Could not open File Control Bank (FCB) for invalid file ID 4096 in database 'DB_Name'. Verify the file location. Execute DBCC CHECKDB.

any clue? thanks

Need to be able to discover the multi subnet configurations for a data base instance.

Preferably by querying the MSDB views. Alternatively could query the Windows registry.

Thanks in advance.

Taking FULL backup of multiple databases using maintenance plan(s).

Should I :

a) Have a separate Maintenance Plan to backup each database

       - or -

b) Have one maintenance plan to backup multiple databases

Option a) will allow me to easily monitor and notify (email) details of a failure.

Option b) will give me one job to maintain but little control over reports

Timing :

With Option a) can all maintenance plans run at the same time - will this effect performance ?

With Option b) I assume that the one maintenance plan will run for all databases at the same time.

Thanks

Colin 

In our environment,  we've done a SQL consolidation project, with SQL Server 2012 R2 and Windows Server 2012 R2. We've used 3 physical server, where we've done Windows cluster. on top of windows cluster SQL cluster is running. We've configured 5 instances in the consolidate platform where instance- 1 and 2 running on host-1, instance-3 & 4 running on host 2 and Instance-5 is running on host-3.

To ensure proper resource distribution, we've already capped resources (Memory & CPU) instance wise because multiple instances are running on the same host.

We've migrated various databases from different different platform to instances. Now under a single instance we've hosted databases from different services. 

Can we give capping on the databases under the same instance, where as capping is already applied in the instance level? 

Please, help us. My system right now in production and i need to ensure proper resource utilization to avoid any kind of service outage. Please help. Urgent. 

Hi All,

we were running Mirroring between our Primary DC and Secondary DC on Sql Server 2008r2 with different IP Segment/Multi Subnet.

Primary DC :(Server A) 192.XXX.XX.XX(Clustered Instance)

Secondary DC: (Server B)10.XXX.XX.XX (Standalone)

Now our Central Project command Have switched the link to other NKN/NIC network. They have provided us some public IP Pool  for primary DC with starting 10.XXX.XX.1 .they are  telling us to carry  mirroring  data traffic to  secondary DC server with  this IP.

We are able to telnet  with FQDN from  A to B but not able to telnet from B to A. because network is terminated to IP 10.XXX.XX.1 at primary DC  . and server B is not able to reach directly to A.

we are able to telnet from B to 10.XXX.XX.1 without FQDN.

as per my knowledge mirroring is not possible in this situation. 

Is there any way to establish mirroring in this scenario.Please suggest any other possible way.

Regards Naveen MSSQL DBA

All instances are SQL Server 2014 Ent. edition

I would appreciate your input and thoughts about this design.

We have set this design at our lab and so far done some very basic tests simulating fail overs etc.

However, due to the design’s complexity I am interested to hear other opinions.

Here is a link to see a diagarm of the design:

https://drive.google.com/file/d/0B7yeAe4Hpq4SZEVVc1JjM3VHOXc/view?usp=sharing

The diagram shows the following:

sql03 + sql04 are both FCI (Failover Cluster Instance) serving as active/passive nodes and holding the OLTP database (most crucial db).

sql05, sql06 and sql07 each hold 2 databases that receive data via Transactional Replication (these 2 databases on each instance are the subscription databases of a 1-way Transactional Replication)

The OLTP database (hosted by the FCI on sql03 and sql04) is the Primary Replica of AG-OLTP sending data to the Secondary Replicas hosted by sql01 + sql02

The subscription databases (hosted by sql05, sql06, sql07) are each the Primary Replica for its 2 databases hosted by AG-PTS01, AG-PTS06 and AG-PTS07. sending data to the Secondary Replicas hosted by sql01 + sql02

So sql01 + sql02 receive data from the various sources via the different AGs

These 2 servers are used for reports. They hold 2 partitioned tables that have the same schemes but one is a column store table and the other is a b-tree table (different type of queries will access each table, aggregates and none aggregates).

For load balancing and HA sql01 and sql02 each send data to the other via AG-REP01 and AG-REP02 respectively allowing applications to access both servers.

Thank you

-Yaniv

Yaniv Etrogi
site | blog | linked in | mail
Please click the Mark as Answer button if a post solves your problem! orVote As Helpful

All,

I am running log shipping between two SQL Server 2012 (11.0.6020), X64, and Enterprise instances.

My problem is periodically SQL Server will create a log backup that has two first and second log sequence numbers for the same log backup.  When SQL Server attempts to apply said log file it throws the classic error in this case, "The log in this backup set begins at LSN <LSN NUMBER>, which is too recent to apply to the database. An earlier log backup that includes LSN <LSN NUMBER> can be restored."  When I look in msdb..backupset and msdb..backupmedialfamily I can verify the other LSN it is referring to belongs to the very same file it has tried to restore.  My workaround is to simply take a diff backup and restore to the standby database.  Here is a screen shot of the multiple LSNs in a single backup log below.  You can see there are even multiple backup_start_dates that are seconds apart.

My questions is has anyone seen this behavior before and if so is there a fix/patch?  I have searched high and low and can't seem to find any information regarding this type of behavior.

Thanks in advance,

Coleman



TheColeman

I am trying to add an Always On Availability group on SQL Server 2012. No matter what I do I keep getting failures. I am at the point of this error when creating an endpoint:

grant connect on endpoint::Hadr_endpoint to [domain\machinename$]

Msg 15151, Level 16, State 1, Line 1
Cannot find the login 'domain\machinename$', because it does not exist or you do not have permission.

My understanding is that this is supposed to be relatively easy. So far that is not the case.

I already read the suggested link you're probably going to post about mirroring. This did not help. I need a solution for this ASAP

We have scheduled backups running in sql agent as follows:

1. Full backup at 6:00AM

2. Differential backup at 7:00AM and every hour until 6:00 PM

The differential backups are failing with the following error and I need help fixing as I do not understand why this is happening.

Cannot perform a differential backup for database "DataPak", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035)  BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013).  The step failed.

-kccrga http://dbatrend.blogspot.com.au/

We are having a database server in different locations with different databases at each site and a single common disaster recovery database server in a central location with synchronous commit. All the locations are connected through VSAT communication.How to enforce the local site server to be a primary role at each location. We are trying to use SQL Server Always ON Availability group ?

Architecture

Hello,

We are running sql server 2012 on windows 2012, with a 3 node config for AlwaysOn.  Nodes A and B are on site and node C is in our remote data center.  Sql Server and windows servers can connect to the database on any node.  We have several apps on Linux, using the jtds driver, and their connections when failed to the remote datacenter are failing 75% of the time.  DNS round robin is sending them to the wrong IP for the listener, and their connections fail.

Is there a solution for this?  I am seeing this RegisterAllProvidersIPData = 0 parameter.  Do I set this on all DB nodes?  Or just the remote?

Thanks kindly,

Dianne

Dianne

Hi

I am trying to use sql server 2005 management stodio to restore a database. But I got this error message:

Exclusive access could not be obtained because the database is in use

Anyone know how to solve this problem?

Thanks

Li

Team,

We have logshipping configued with generic setup. And when the restore job is running against standby database;only a portion of the log backups are being restored and the standby database is coming  back from restoring mode to standby mode in middle of restoe and the restore job is failing as all backups are not being restore. below is the log file of the restore job; can anyone help me out here ?

----- Log file -----

Dear Team,

As we already have SQL 2008 R2 mirroring environment on Windows server 2008. (Primary, Mirror, Witness), want to change the architecture to new environment and HA and DR. 

For example SQL 2012/2014 and Windows Server 2012 or newer. We prefer Clustering instead of Mirroring as our system not have huge data. 

Could you please guide me , which version of SQL Server i can go for and Windows Server. Your ideas really appreciated..!!

Thanks,

Rathan.

Y.K

Hello Experts,

Good day! We encountered a problem with our production system which are running on two-node WSFC/SQL AlwaysOn environment, and SQL AG was stuck in 'RESOLVING' state on 2016/04/13 from 21:17:19 to 21:18:15.(About 1 min).

This two-node are running Windows Server 2012 Standard, and DBMS are running SQL Server 2012 Service Pack 3.

In some research, we've conducted to read some MS-KB article which mentioned similar situation issues/problem are listed below.

KB2699013-FIX_SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a 'Non-yielding Scheduler' error is logged
KB3081074-FIX_A stalled dispatcher system dump forces a failover and service outage in SQL Server 2014 or SQL Server 2012
KB3112363-Improvements for SQL Server AlwaysOn Lease Timeout supportability in SQL Server 2012

I thought/bold assumption this version of service pack/cumulative update was supposed to fix related problem, or not?

Anyway, finally the issue has initiative found us, I just want to clarify and know, Is it still a unresolved potential bug?

Any recommendation or advice is highly appreciated, thanks a lot!

Kevin

=====================================================================                                           

       SQL Error Log                                                                                            

=====================================================================  

04/13/2016 21:18:15,spid30s,Unknown,AlwaysOn Availability Groups connection with secondary database established for primary database 'QAP' on the availability replica with Replica ID: {ad0236ba-a1cf-449d-b1c1-ce7d3c86e9cc}. This is an informational message only. No user action is required.

04/13/2016 21:18:01,spid164,Unknown,The log shipping secondary database DL980-4.QAP has restore threshold of 45 minutes and is out of sync. No restore was performed for 520600 minutes. Restored latency is 10 minutes. Check agent log and logshipping monitor information.

04/13/2016 21:18:01,spid164,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.

04/13/2016 21:17:40,Logon,Unknown,Unable to access database 'QAP' because its replica role is RESOLVING which does not allow connections. Try the operation again later.

04/13/2016 21:17:40,Logon,Unknown,Error: 983<c/> Severity: 14<c/> State: 1.

04/13/2016 21:17:40,spid49s,Unknown,Nonqualified transactions are being rolled back in database QAP for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.

04/13/2016 21:17:40,Logon,Unknown,Unable to access database 'QAP' because its replica role is RESOLVING which does not allow connections. Try the operation again later.

04/13/2016 21:17:40,Logon,Unknown,Error: 983<c/> Severity: 14<c/> State: 1.

………………………………………

04/13/2016 21:17:23,Logon,Unknown,Unable to access database 'QAP' because its replica role is RESOLVING which does not allow connections. Try the operation again later.

04/13/2016 21:17:23,Logon,Unknown,Error: 983<c/> Severity: 14<c/> State: 1.

04/13/2016 21:17:23,Logon,Unknown,Unable to access database 'QAP' because its replica role is RESOLVING which does not allow connections. Try the operation again later.

04/13/2016 21:17:23,Logon,Unknown,Error: 983<c/> Severity: 14<c/> State: 1.

04/13/2016 21:17:23,Logon,Unknown,Unable to access database 'QAP' because its replica role is RESOLVING which does not allow connections. Try the operation again later.

04/13/2016 21:17:23,Logon,Unknown,Error: 983<c/> Severity: 14<c/> State: 1.

04/13/2016 21:17:23,Logon,Unknown,Unable to access database 'QAP' because its replica role is RESOLVING which does not allow connections. Try the operation again later.

04/13/2016 21:17:23,Logon,Unknown,Error: 983<c/> Severity: 14<c/> State: 1.

………………………………………

04/13/2016 21:17:09,spid49s,Unknown,The availability group database "QAP" 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.

04/13/2016 21:17:09,Server,Unknown,Stopped listening on virtual network name 'dbgrpqap'. No user action is required.

 ………………………………………

04/13/2016 21:17:09,spid49s,Unknown,AlwaysOn Availability Groups connection with secondary database terminated for primary database 'QAP' on the availability replica with Replica ID: {ad0236ba-a1cf-449d-b1c1-ce7d3c86e9cc}. This is an informational message only. No user action is required.

04/13/2016 21:17:09,Server,Unknown,The state of the local availability replica in availability group 'AGQAP' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup<c/> a failover<c/> a communication issue<c/> or a cluster error. For more information<c/> see the availability group dashboard<c/> SQL Server error log<c/> Windows Server Failover Cluster management console or Windows Server Failover Cluster log.

04/13/2016 21:17:09,Server,Unknown,AlwaysOn: The local replica of availability group 'AGQAP' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required.

04/13/2016 21:17:08,Server,Unknown,Process 0:0:0 (0xfe4) Worker 0x0000000006B16160 appears to be non-yielding on Scheduler 28. Thread creation time: 13102488101502. Approx Thread CPU Used: kernel 1591 ms<c/> user 0 ms. Process Utilization 7%. System Idle 94%. Interval: 74565 ms.

04/13/2016 21:17:08,Server,Unknown,The lease between availability group 'AGQAP' 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<c/> check the corresponding availability group resource in the Windows Server Failover Cluster.

04/13/2016 21:17:08,Server,Unknown,Error: 19407<c/> Severity: 16<c/> State: 1.

 ………………………………………

04/13/2016 21:17:08,Server,Unknown,DoMiniDump () encountered error (0x80004005) - Unspecified error

04/13/2016 21:17:07,Server,Unknown,Timeout waiting for external dump process 8480.

04/13/2016 21:17:07,Server,Unknown,Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group 'AGQAP' within the lease timeout period.

04/13/2016 21:17:07,Server,Unknown,Error: 19419<c/> Severity: 16<c/> State: 1.

04/13/2016 21:16:18,Server,Unknown,Stack Signature for the dump is 0x000000000000036A

04/13/2016 21:16:18,Server,Unknown,* *******************************************************************************

04/13/2016 21:16:18,Server,Unknown,*

04/13/2016 21:16:18,Server,Unknown,* Non-yielding Scheduler

04/13/2016 21:16:18,Server,Unknown,*

04/13/2016 21:16:18,Server,Unknown,*   04/13/16 21:16:18 spid 3976

04/13/2016 21:16:18,Server,Unknown,* BEGIN STACK DUMP:

04/13/2016 21:16:18,Server,Unknown,*

04/13/2016 21:16:18,Server,Unknown,* *******************************************************************************

04/13/2016 21:16:18,Server,Unknown,***Unable to get thread context for spid 0

=====================================================================                                           

       BugCheck Dump                                                                                             

=====================================================================  

Current time is 21:16:17 04/13/16.                                                                                                                                                             

This file is generated by Microsoft SQL Server                                                                  

version 11.0.6020.0                                                                                             

upon detection of fatal unexpected error. Please return this file,                                              

the query or program that produced the bugcheck, the database and                                               

the error log, and any other pertinent information with a Service Request.                                                                                                                                                 

Computer type is Intel(R) Xeon(R) CPU           X7560  @ 2.27GHz.                                               

Bios Version is HP     - 2                                                                                      

128 X64 level 8664, 2 Mhz processor (s).                                                                        

Windows NT 6.2 Build 9200 CSD .                                                                                 

Memory                              

MemoryLoad = 99%                    

Total Physical = 1048565 MB          

Available Physical = 3472 MB        

Total Page File = 1348565 MB        

Available Page File = 364906 MB     

Total Virtual = 8388607 MB          

Available Virtual = 7188925 MB      

***Unable to get thread context for spid 0                                                                       

* *******************************************************************************                               

*                                                                                                               

* BEGIN STACK DUMP:                                                                                             

*   04/13/16 21:16:18 spid 3976                                                                                 

*                                                                                                               

* Non-yielding Scheduler                                                                                        

*                                                                                                                

* *******************************************************************************    

=====================================================================                     

       SQL Server Memory Configuration & Availability Group Properties                                                                                            

=================================================================

Memory_usedby_Sqlserver_MB Locked_pages_used_Sqlserver_MB Total_VAS_in_MB      process_physical_memory_low process_virtual_memory_low
-------------------------- ------------------------------ -------------------- --------------------------- --------------------------
960375                     950171                         8388607              0                          0

=====================================================================