Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all 4532 articles
Browse latest View live
↧

SQL Server Assertion: File: , line=3099 Failed Assertion = 'x_btFree == m_btUsed'.

November 5, 2017, 11:23 am
$
0
0

Hi All,

I am running SQL 2016 SP1 CU5 latest update on my SQL always on server .I have 3 node cluster and node 1 and node 2 are in sync commit mode .I have encountered below error in SQl logs and it generated sql dump .Just after this error transaction were not able to commit and i could see hadr_sync_commit wait type .I have also noticed no of sessions were blocked .Kindly review below error and let me know if anyone has experienced this .Just to inform you that DBCC is not giving any data corruption error 

Message
Error: 3624, Severity: 20, State: 1.

SPID 45 

SQL Server Assertion: File: <sosmemobj.cpp>, line=3099 Failed Assertion = 'x_btFree == m_btUsed'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

Error: 17066, Severity: 16, State: 1.

↧
Search

Stored Procedure Migraton with 100 Plus Applicatoins

November 12, 2018, 11:02 am
$
0
0

Ok, so I feel for DBA's who do this regularly. It can be very overwhelming to say the least. Here is my question and scenario.

I'm attempting to work out an ETL process for 12 databases. All are the similar such as LIMS, LIMS-1, LIMS-2 etc. There are 12 of these. Seven have an identical schema, 4 have an identical schema but not identical to the first 7. Then 1 has a schema different that the other 11.

Migrating schemas probably isn't the challenge, however, I've never done this before so any tools to help would be great to know about. The problem comes in with stored procedures. There are over 100 applications that would use this new database (hence the problem). If there are stored procedures that have the same name, but operate on a different schema, what would be a way to handle this. I first thought about renaming the stored procs and then make changes to the application. However, my manager isn't wanting to go down that route. Thanks in advance.

↧
↧

Log Shipping Server SQL Versions

November 27, 2018, 8:32 pm
$
0
0

Hello,

We are planning to have new log shipping set up as our DR model as below

  • Primary Server: Windows Server 2016 Standard 64 Bit with Database License of Microsoft SQL 2016 Standard Edition
  • Secondary/Failover Server:Windows Server 2012 R2 Standard 64 Bit with Database License of Microsoft SQL 2016 Web Edition

Please let us know if we have same version of sql server but different editions of database engine will work for log shipping set up.

Regards, Mahesh Ambokar India Capital Research and Advisors

↧

Transactional replication

November 28, 2018, 5:34 am
$
0
0
Can we able to setup transactional replication for the tables without a primary key?
↧

SQL 2014: AG listener up but DBs in "Recovery Pending" post shared cluster failover

November 28, 2018, 10:49 am
$
0
0

We had a SQL 2014 (12.0.5000.0 version) windows 2012 R2 shared disk sql server cluster with two nodes in primary and one node in muti-site DR.  We have an AG listener from primary to a multi-site secondary.  We had an issue where we had to failover the cluster to node 2 from node 1.  The AG listener stayed on node 1 and was up.  The databases stayed in "not synchronizing/recovery pending" until we started and stopped the AG listener so it failed over to node 2 with the rest of the cluster.  We did not have DB corruption as the cause of the recovery pending and all of the DBs were fine after AG listener start and stop.  Can someone please explain why the AG listener isn't failing over as it should with the cluster and why it could not recover the DBs until it was on node 1 with the cluster resources?

Thanks!

↧
↧

one's the database is corrupted that time .mdf & .ldf both files are corrupted or not ?sss

September 4, 2012, 9:10 am
↧

SQL Always on

November 14, 2018, 9:03 pm
$
0
0

Hello,

I am planning to purchase Four Servers. Each Server contains 4 Processor and total of 96 Cores. 

Please help me calculate required license for SQL AlwaysOn.

Regards

Tanveer

↧

Extracting data from .MDF file

October 16, 2011, 7:00 am
$
0
0
I have an SQL 2005 Database on a local computer. For unknown reason SQL Server cannot connect to the database and even the MSSQLSERVER Service cannot start. I can't even re-instal the SQL Server. I suspect the data is still intact. I have been able to copy away the actual .mdf and .ldf to a different computer. How can I get the data from this database? 
↧
Search

OpenRowSet without sysadmin rights

October 24, 2014, 2:39 am
$
0
0

Hi,

When I execute

SELECT * FROM OPENROWSET('Microsoft.ACE.OLEDB.12.0','Excel 12.0 Xml;HDR=YES;Database=\\LinkedServer\Share\TEST\emp.xls','SELECT * FROM [Sheet1$]');

 I got error 

"Ad hoc access to OLE DB provider 'Microsoft.ACE.OLEDB.12.0' has been denied. You must access this provider through a linked server."

I run it without sysadmin roles or rights. I give ADMINISTER BULK OPERATIONS permission to the user. Even using this user I can execute   EXEC xp_cmdshell  'dir "\\LinkedServer\Share\TEST\emp.xls"' 

How to execute OPENROWSET command without sysadmin permission plz help me.

↧
↧

AlwaysOn automatic failover is not happening

April 18, 2017, 1:09 am
$
0
0

i Experts,

AlwaysOn Configured on 2 node, automatic fail over was enabled.

When trying to test the automatic fail-over, it was not working.

scenario : to testing the automatic failover stopped the sql server on primary replica, but AG group is not moving to secondary replica, it goes to offline on cluster.

During the failover below event are logged on cluster log.

1196,1069.

1196:

Cluster network name resource 'XXXAG_XXXXAL' failed registration of one or more associated DNS name(s) for the following reason:
DNS signature failed to verify.

1069 :.

Cluster resource 'agXXXXXX' of type 'SQL Server Availability Group' in clustered role 'agxxxxx' failed.

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Thanks in advance.

Thaks

Vijay

↧

AlwaysOnHighAvailability

November 30, 2018, 6:06 am
$
0
0

Hi,

 Does it support active-active clustering that is, keep two (DB1,DB2) sql server instances (Nodes) always active for

transactions with synchronization. We are getting an error in validate configuration for selecting servers, not able to add

  DB2 server or Node.


Error is - You do not have administrative privileges on the server DB2.

Please suggest...

↧

SQL On-Prem to SQL managerd Azure instanace- Log shipping

November 30, 2018, 10:05 am
$
0
0

We are in the planning stages of moving away from hosted to azure and I have not found any articles pertaining to the SQL logshipped solution to Azure.

currently we are conducting log shipping every 15 minutes as a DR solution to a remote location and the Destination is on standby/readonly mode.

what would be the suggested most effective method for this?

Priyantha Perera

↧

Automatic failover in AlwaysOnHighAvailability

November 30, 2018, 2:50 pm
$
0
0

Hi,

Does AlwaysOn supports automatic failover when 

1] primary server shut down unexpectedly .

2] By stopping MSSQLSERVER service from services option.

Does Mirroring with witness server supports above two scenarios with automatic failover.

Thanks,

Ni3.

↧
↧

Cluster Error.

December 1, 2018, 6:59 am
$
0
0

Hi All,

Trying to create failover cluster, but getting an error.

Please refer attached image link.

https://social.msdn.microsoft.com/Forums/getfile/1365989

Thanks,

NI3

↧

Does applicationintent=readonly routes the read only connection to primary when the secondary goes down in SQL Server 2014?

December 3, 2018, 5:22 am
$
0
0

The Always configured is configured as Allow all connections on both primary (node1) and Secondary (Node2).

1. Node1 and Node2 in Primary DC

3. node3 in secondary DC (Readable secondary is set to no)

Node 1 is primary and Node2 is readable secondary.

aa

↧
Search

Automatic Seeding Failures

August 29, 2018, 5:32 am
$
0
0

Hi

We are running a two Server Always On HADR system with enabled Automatic Seeding. Both SQL Servers are Microsoft SQL Server Enterprise (64-bit) with Build 14.0.3029.16 and both are running on Windows Server 2016 Standard (10.0). Assigned memory is 4096 MB to 432128 MB. Disk space is enough on both servers and performance Tuning options like "Lock pages in memory" are set.

From time to time the automatic Seeding process will not start. In the DMV sys.dm_hadr_automatic_seeding the current_state is CHECK_IF_SEEDING_NEEDED and after a couple of seconds it changes to FAILED. The failure_state_desc then shows "Seeding Check Message Timeout".

The last database we had this problem was just 8 GB. The Problem can be easily solved by removing the DB from the Availability Group and adding it again. Then it is working without problems.

Where can I enhance this timeout?

What could delay the check if seeding needed?

Do you need more information?

Thanks for the help.

Kind Regards

Dominic

↧

SQL AlwaysOn failover problem

December 4, 2018, 12:04 am
$
0
0

The SQL version is SQL 2016 Enterprise.
Two servers, server A and server B.
When B is primary and A is secondary, the function works perfect.

But when doing a fail-over, the server cluster can not recognize server A is switched to primary and cluster is stick to secondary.

One thing strange is that, when doing failover to set Server A as primary, below screen will be shown while it will not shown when doing failover to set Server B as primary.


Does anyone meet this before? or can anyone help me on this?

Thank you.


↧
↧

SQL Server Replication Licensing Specifics

December 4, 2018, 2:49 am
$
0
0

We are planning to implement a disaster recovery solution for a client involving replication in SQL Server 2012 Standard Edition but I'm struggling to get specifics on the licensing involved. We are planning on using two virtual machines with an instance of MSSQL Server 2012 Standard installed on each, one serving as a primary and the other a standby secondary

It's my understanding that we can do this with a single license, granted the secondary is purely passive outside of the replication itself, with no querying, backups or activity of any kind except in the case of a failure on the primary, in which case the secondary would have to pick up the slack until we get the primary back online.

Can anyone clarify the scenario for me or direct me to somewhere that I can gather more info? I've tried to find official Microsoft information regarding this but information is few and far between and mostly quite general/vague.

Thanks in advance

↧

Always on availability group sql account

December 4, 2018, 12:25 pm
$
0
0

Hello all

I am running a SQL server 2016 always on availability group. To provide access to the databases, i created individual sql accounts for each replicated database. When i fail over all the databases to another node i can no longer access the database . When i check the sql account under logins, and then check user mappings , the sql account is not mapped to the database. In order to get access to the database i have to run the following sql query. After i run this query the sql account is mapped to the database again. How do i keep the sql account mapped to the database after a fail-over to another node?

USE TestHealth
EXEC sp_change_users_login 'Auto_Fix', 'test-svc'

Bulls on Parade

↧

SQL Server 2017 Fail-over Cluster License

December 6, 2018, 1:15 am
$
0
0

Good day!

I have an SQL Server Failover Cluster Setup (2 nodes). When I installed SQL Server 2017, I used enterprise evaluation first. And then I clustered the SQL Servers. My problem now is I want to use my SQL License for standard edition and I'm trying to upgrade my sql servers from evaluation to standard edition. But I encountered this error:

Rule "SQL Server 2017 Failover Cluster Edition Downgrade" failed.

The edition of the selected SQL Server instance is not supported in this SQL Server Edition downgrade scenario. The source Evaluation edition and the target Standard edition is not supported path.


My question is what does this error means? Is standard edition license compatible with the SQL Failover Cluster?

I hope someone could help me with my problem.


↧
Viewing all 4532 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>