I have transferred a database from SQL 2000 to SQL 2005 and now I am getting an error when I try to run backup. I get there error "An error occurred while processing 'BackupMetadata' metedata for datase ID..." Does anyone have any suggestions on how to resolve this error?
↧
An error occurred while processing 'BackupMetadata' metadata for database
↧
ALWAYSON readonly connect to server through Listener and connection testing
Hi I already configured always on(2016 EE R1) two node replica. I need to setup read intent routing connection depending on the role. That mean when I connect to Always on using listener name using SQL Server management studio and setup "additional connection parameters ApplicationIntent =ReadOnly. After connect I checked the server select @@servername and always connect to active primary.
Before that I set up read only routing as follows. This has executed this same script on both nodes while active by failover over and fail back process.
secondly I tested though following method. But still I can see the primary node.
sqlcmd -s AGlistener,50000 -E -d dbname -K ReadOnly
select @@SERVERNAME
go
Any one have this issue to resolution .
↧
↧
SQL Always On with SQL Srv 2012 STANDARD ?
Hi Guys,
we recently saw MS Docs saying that it is possible to have a SQL Always On Group with 2 Nodes on a SQL Server 2012 Standard Edition - is that true ?! We know about the Enterprise Edition as a prerequisite so far !?!
Thank you in advance,
Markus
↧
2016 to 2008 R2 cluster
Can I add a SQL Server 2016 node to a SQL Server 2008 R2 cluster?
Reza Negarestani
↧
Not able to uninstall cluster instance.
Hello all,
please any tips how to uninstall, cluster instance SSAS?
The thing is it is 2008 R2 instacne running on OS 2012, there were also big issues to install it unable to find cluster etc.
Then found some guide to make splitstream installation with SP2 and couple of other steps which worked fine at the end.
But now I need to uninstall one instance but not able because of following error.
1, - Not able to select any instance
2, - Name of this node is wrong showing XXXSQL0 while the correct is XXXSQL01
Any advice please?
↧
↧
SQL AlwaysOn - SQL Server 2014
Hi All,
We have implemented SQL alwayson on A-P cluster environment. The DB size is 390 GB. The fail-over mode is Automatic.
primary DB box: SQL1 (DB file hosted on local disk not on shared disk)
secondary DB box: SQL2 (DB file hosted on local disk not on shared disk)
when we reboot primary DB box, the DB is moving to secondary but DB status is showing recovery pending on secondary node (SQL2). It's taking 2-3 hours to complete recovery on SQL2.
when we reboot secondary DB box (after recovery complete), DB is moving to primary but again DB status is showing recovery pending. It will take 2-3 hours to complete recovery on SQL1.
During the reboot, DB is taking 2-3 hours time for recovery, Just for reboot my customer is not ready to give 3 hours downtime. Please suggest is this is SQL expected behavior or is there any changes required?
↧
How to validate the configuration of alwaysON?
Hi Team,
I have two node alwayson configured but i am not SQL guy.
and below is the setup details
1- I have AD which is file share witness as well
2- Two node failover cluster
3- Installed SQL with newly user created on AD on both node.
Now if primary replica fails and failover happens to secondary replica then do i need to configured anything else on the secondary node ? will my apps will work perfectly. since I have checked AG dashboard & it shows failover successful.
but i want to make sure everything works fine from apps side as well.
need expert advise here.
Thanks
NM-BG
↧
SQL service delay start for Always On instance
Are there any consideration when using SQL service delay start for a Always on SQL instance ?
↧
Pre Production - Always ON
Hi Experts,
Our current requirement need to do proc performance testing on an environment as close to Production before deploying them to actual Production environment.
The proc's can do update/inserts/deletes/select. Is always on ( SQL Server enterprise & standard 2014- 2016) a feasible solution as data is also PCI compliance based. Am very new to always on and willing to learn more about it if in case it solves the requirement or please guide me to right approach for this requirement.
Thanks & regards
Priya
↧
↧
DBCC CheckDB fails on Secondary replica with error it is not enabled for read access...
The customer failed over their "Availability Group" 5 days before the DBCC Checkdb job ran on the secondary replica and failed with this error:
Executed as user: xxx Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : The target database, 'DBAAdmin', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica
is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement
in SQL Server Books Online.. Process Exit Code 1. The step failed
Can someone tell me why?
It is my understanding the secondary sql server should be able to run dbcc checkdb without having "read-only" access enabled.
The customer is running Microsoft SQL Server 2014 - 12.0.4213.0 (X64) and is using Ola Hallengren DB Maintenance script but is running the script using "CmdExec" vs "transact sql" not sure that makes a difference or not. The Ola Hallengren script is in a database that is part of the "Availability Group".
Thanks,
Sue
Sue
↧
Master key issue in Secondary SSIS DB
Hi Experts
we have always on AG servers (SQL 2014) packages are working fine in A01 node when fail-over happens AG moves to A02 then all packages are failing with error
Description: Please create a master key in the database or open the master key in the session before performing this operation. Source: .Net SqlClient Data Provider Started: 7:44:42 PM Finished: 7:44:42 PM Elapsed: 0.156 seconds. The package execution failed. The step failed.
i have tried below options but no luck.
USE [SSISDB]
OPEN master Key decryption by password = 'password' -- Password used when creating SSISDB
ALTER Master Key ADD encryption by Service Master Key
Alter master key add encryption by service master key
close master key
Could you please suggest me is there any other alternatives to resolve this.
Thanks
Raghavendra
Thanks & Regards Raghavendra Petla
↧
EntityFramework Connections to SQL Server Distributed Availability Group Cluster
We recently built a Distributed Availability Group cluster. The cluster has three different availability groups within three different domains/region. One primary read/write listener and two other listeners with read-only replicas.
We plan to have an application built with EntityFramework configured in each domain/region. How would we configure EntityFramework connections to properly send read/write connections to the Primary Listener and read-only connections to the Local Listener?
Is there documentation on how to configure connections to communicate with Distributed Availability Group clusters?
Thx
↧
Automatic failover in AlwaysOnHighAvailability
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.
↧
↧
Trying to restore our data
Here is the case:
Our database got corrupted due to I/O failure. I have old backup and some data is missing too. I know about DBCC CHECKDB with repair allow data loss and there will be the last option if no method will work.
Please suggest me.
↧
how many ip adresses are needed.
Good Morning Experts,
I would like to create 4 AGs . So, could you please let me know how many ip adresses are needed.
Kiran
↧
Shrink Log File on High Availability
Dear support
good day for you,
i using SQL server 2012 and using AlwaysON High Availability (server_SQL1 = Primary & Server_SQL2=Secondary), when i try to shrink the log files he told me you must alter the database to simple recovery mode first but i cant coz using AlwaysON !
thats mean:
- remove the DB's from AlwaysON (Server_SQL1)
- Shrink Files
- remove DB's from Server_SQL2
- add again DB's to AlwaysON
any other solution for shrink logs without add/remove DB from AlwaysON
Regards,
↧
AG on primary replica went offline
Good Morning Experts
AG on primary replica went offline. Could you please let me know how to fix this
Kiran
↧
↧
Similate crossite link down using windows firewall
I have 4 nodes cluster + 1 fsw, 2 nodes in main site and 2 nodes in backup site and they have different subnet .
is it possible to use windows firewall to simulate heartbeat disconnect between both site using windows firewall ?
↧
Zero Downtime Upgrade: Upgrade application database with DLL changes up and running with Always On Availability Group
Our Companies vision is to achieve zero downtime application upgrade (minimum downtime in seconds) which is already up and running with Always On Availability Group.
The current design for our application is to have 2 application server (grouped together by using windows server failover clustering) and 2 database servers (grouped together by using windows server failover clustering and ALwaysOn Availability Group). Both individually joined with WSFC.
Both Application server point to the primary database in the cluster using listener IP. No queries are made to secondary.
If my application upgrade contains of version upgrades including SQL, windows and also database schema changes to support new enhanced features of our application. How can we leverage AlwaysOn AG to handle this kind of upgrade with zero downtime/minimal downtime?
We release application updates on an 5-6 months cycle and any release could include schema changes and/or data migrations.
What I am trying to understand is whether or not the HA/DR solution handles the schema changes transparently (new columns, indexes get added to secondaries) or is manual intervention required to create the schema on each instance and then turn Always On <g class="gr_ gr_100 gr-alert gr_gramm gr_inline_cards gr_disable_anim_appear Grammar only-ins replaceWithoutSep" data-gr-id="100" id="100">back</g> on.
The data migration piece I'm assuming is handled transparently but would like to confirm that as well.
I guess I am also making a blanket assumption that there is no difference in these behaviors based on the Availability Groups configuration which may be false as well. Please let me know.
In a nutshell; In any given release of my application, I may change a very large table (10s to 100s of millions of records) by adding columns to it. Some columns may be "net new" so they can make use of the Enterprise Online schema change functionality. Other columns may be a refactoring of an existing column (FullName gets split into FirstName and LastName) and migration will be run for each row in the table to populate these fields. Do any of these behaviors require DBAs to change the AlwaysOn configuration or is this handled by default and all secondaries get the DDL and DML statements "for free"?
Surabhi
↧
Alwayson - two nodes
hI
I have two instances with a database in an availability group. My question I must have a witness for the listener role. Actually I have no querum disk.
best regards,
Eusebio
↧