Dear SQL Forum Group Members,
1) Could anyone clarify me, will there be any issues in SQL server 2008 Mirroring because of Daylight Time saving ?? Also, will there be any impact on Tlog backup scheduled jobs which will be running in 15 Minutes interval.?
2) Do i need to reschedule my mirroring & scheduled jobs on Daylight saving days?? Is there manual(DBA) Intervention needed on these days??
Awaiting your valuable feedback.
Dear All,
Do we get any impact on Database Mirroring or SQL agent job due to changes on day light saving time?
Because, we configured database mirroring in our production environment in spain.
Below is spain day light saving start and end time for 2014.
| Year | Start Date | End Date |
|---|
| 2014 | Sunday, March 30 at 2:00 AM | Sunday, October 26 at 3:00 AM |
1) Could anyone clarify me, will there be any issues in SQL server 2008 Mirroring because of Daylight Time saving ?? Also, will there be any impact on Tlog backup scheduled jobs which will be running in 15 Minutes interval.?
2) Do i need to reschedule my mirroring & scheduled jobs on Daylight saving days?? Is there manual(DBA) Intervention needed on these days??
This will be helpful for us if anyone guide us in advance and thankful to you as well.
Hi all,
I'd like to know first off if this is possible...
We currently have a DB mirroring pair across two VM's (on separate physical machines) and a separate witness on another vm on the same host machine as one side of the pair.
One of our hosts had a small blip recently and it took down the witness, so nothing failed over...
Due to space and money restrictions... etc. I can't put another physical box into the mix to act as a standalone dedicated witness. Instead I'm trying to setup another VM at a remote location (this is on a different domain but does have a domain trust setup between this location and the location of the mirrors,) to act as an external witness.
I can ping the FQDN and ip address which all resolve fine. I've done a portquery either end and both sides are listening on port 5022. There are firewalls in the mix but I've allowed this port through.
I can get so far in the configure security wizard and then when I click the final 'OK' I'm hit with:
"Alter failed for Database 'X' (Microsoft.SqlServer.Smo)
An exception occurred while executing a Transact-SQL statement or batch (Microsoft>SqlServer.ConnectionInfo)
The ALTER DATABASE command could not be sent to the remote server instance." Error 1456
I've tried using both SQL and windows authentication but neither seem to get past this. I did previously notice an error with pings but I've updated the DNS entries and that seems to have fixed that problem.
Is what I'm trying to do possible and if so does anyone have any clues as to what could be wrong please? (All updates and patches have been installed.)
Thanks in advance.
Mark
I need to setup database mirroring between 2 separate SQL 2012 instances. The documentation states that if the 2 server instances are running under different user accounts then these need to be manually created on both instances. Is this login account the account that was used when installing SQL or is it the account assigned to run the SQL server service account?
Thanks
Alistair
Following a datacenter disaster, where the subscription database was/is lost and gone forever ("others" decided not to restore the database which was pulling the subscription), the local "master" database hosting the "publication" chugged along fine for a few weeks, me completely forgetting about the replication settings, 'till the distribution database started growing out of control. Point is, I'd just like to remove ANY reference to ANY legacy publication/replication on this database, and can't seem to do so. Database is SQL 2008 64 BIT.
First, just right-clicking on the publication name in Local Publications and selecting delete fails with:
Could notdelete publication 'FISHREP'.
An exception occurred while executing a Transact-SQL statement or batch.(Microsoft.SqlServer.ConnectionInfo)
Target string size is too small to represent the XML instance
Changed database context to'Fish'.(Microsoft SQL Server, Error:6354)Ok...so I tried:
DECLARE@publicationDB AS sysname;DECLARE@publication AS sysname;SET@publicationDB = N'FISH';SET@publication = N'FISHREP';USE[FISH]EXEC sp_droppublication @publication =@publication;Which fails with:
Msg 14013, Level 16, State 1,Procedure sp_MSrepl_droppublication, Line 87
This databaseisnot enabled for publication.Ok....so next:
EXEC sp_replicationdboption @dbname =@publicationDB,@optname = N'publish',@value = N'true';
GOThen
EXEC sp_droppublication @publication =@publication;Which gives a DIFFERENT ERROR
Msg 20026, Level 11, State 1,Procedure sp_MSrepl_droppublication, Line 146
The publication 'FISHREP' does not exist.I could go on and on with the hundreds of different permutations of SQL text I've tried to remove this !)@&^@!^!@& publication, nothing works. I can't even drop the database!
Is there some magical SQL management mode that will let me get rid of this publication?
Hello,
Is there any tutorial or step by step guide to implement Database Mirroring from Windows Azure VM to On-premise Server? I couldn't find it. I want to use database fromWindows Azure VM as Primary and on-premise database as Mirror.
Thanks
Hi Everybody,
We use the database mirroring a lot in our product solutions and we have recently experienced a strange behaviour in our failover tests with SQL2008R2.
We have 2 servers running Windows 2008 R2 standard and SQL 2008 R2 standard SP2. (let's call them DB1 and DB2)
We also have a Witness workstation running SQL 2008 Express on a Windows 7
A database from DB1 is mirrored to DB2 in "safety full" mode, with witness. At this stage, the database is principal on DB1 and mirror on DB2
To test the automatic failover, we first restart the DB1 server which has the database in principal mode
After a few seconds, the database on DB2 becomes principal, which is normal , that's exactly what we want.
After a few minutes, DB1 comes back online and its database takes the mirror role (still OK). At this stage then, the database is principal on DB2 and mirror on DB1
when the monitoring application shows that the mirror is synchronized and that both servers are connected to the witness, we restart DB2 to trigger an automatic failover to DB1.
What we see is that DB1 never takes the principal role and the database stays in mirror.
In the DB1 Errorlog, I only see these 2 lines when DB2 disappears, no other message related to the mirroring session.
2014-01-22 08:57:26.91 spid43s Starting up database 'Test123'.
2014-01-22 08:57:26.95 spid43s Bypassing recovery for database 'Test123' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
When DB2 comes back online, the database on DB2 keeps its principal status and the database on DB1 stays mirror.
And what is really really strange is that, if I restart DB2 once again, directly after that, DB1 failover normally and the database on DB1 takes the principal role after a few seconds. without any configuration changes between the 2 restarts.
DB1 errorlog shows then :
2014-01-22 09:00:37.53 spid29s Error: 1474, Severity: 16, State: 1.So, if I summarize,
- a first failover from DB1 to DB2 always work
- then, a restart of DB2 never failover to DB1
- a second restart of DB2 always failover to DB1
This is pretty much systematic on one our server couple.
Any explanation for this or any idea where I can search to find the reason of this strange behavior ?
Thanks a lot for your help
Seb
I have recently install 3 instances of SQL SERVER 2008 R2 and try to setup Mirroring but there is no mirroring option available on database property. I have then install SP1 as well. still no luck.
have some idea?
I have Windows 7 , SQL SERVER 2008 R2, SP1 Build 7600
This is the Version Information
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
Shamas Saeed (if Post helpful please mark as Answer) http://shamas-saeed.blogspot.com
Hi,
I have a 2008 SQL server, where the tlog kept on growing as there was no maintenance plan done. So, i took a full tlog backup so that the log size would reduce, but no matter how many backups i take of the log, i still end up with a log_backup when i run this command,
log_reuse_wait_desc
Even the link, http://msdn.microsoft.com/en-us/library/ms345414.aspx says that if i get that result, i should take another backup which i did, but it doesnt still go away. I am not sure how to proceed here on. Please advise.
Thanks.
Hi i have two SQL Cluster each cluster consist from Two Node A and B
Cluster one
Node A and B
Cluster Two
Node A and B
now my question can i make Database mirroring between two different clusters.
Thanks
Ahmed Ali
Guys,
We have weird scenario after configuring DB Mirroring between two Servers.
I have Primary with almost 300 databases with 32 GB RAM and Secondary with 64 GB RAM.
We took full backup of all databases and started restoring on Secondary and configured Mirroring for 120 databases also but when we tried to restore all the databases we have come across "Timed out Error" at Secondary Server end and goes to disconnected state even though my services are running fine.
Meanwhile,once my Primary was shut down for few minutes i.e Mirroring got disconnected thereafter I was able to connect to sql server at secondary server without any issue and able to restore backups.
But, as soon as my primary server is up we have come across time out error on secondary server again.
Error Below:
TITLE: Connect to Server
------------------------------
Cannot connect to DR-XXXX.
------------------------------
ADDITIONAL INFORMATION:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
(Microsoft SQL Server, Error: -2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Please help!!
sadankumar
Hi experts,
I got stuck on below strange situation:
1. On server01, I created DB_A, set its db_owner to 'sa', and turn its db_chaining on;
2. I(user [xxx], sysadmin of server01 and server 02) backup DB_A and restored it on server02 and set it up as mirror db DB_A_mirror, now the db_owner of this mirror DB is me [xxx], not 'sa' any more because I restored it;
2. Failover the DB_A_mirror as the principal to change its db_chaining ON and failover it back;
3. Create a snapshot A_ss based on DB_A_mirror on server02;
4. Create a DB DB_Read whose db_owner is 'sa' and db_chaining has been trun on, in this DB, create a view dbo.yyy which refer a table in the snapshot A_ss.
5. Add a AD user [uuu] with datareader role to DB_Read, and public role to A_ss.
Then, use [uuu] to select on the view dbo.yyy, it works!!! regardless of the cross DBs' db_owner are different: one is 'sa' one is me.
Who can explain to me on this???
I need to change sql server service account for both servers in live enviornment of database mirroring.
please tell me what how to stop & start database mirroring as changing service account will required serverices restart.
& what precautions do i take during this activity.
I want to change the service account of my both sql server services on which mirror is setup in live environment.
What precautions & steps do i need to follow. please tell me in details.
Hi All,
I use SQL Server 2005 with mirror enable.
Are there anyway to check/monitor/verify whether all data at principal are transit to mirror serer ?
Regards,
Pitou
Hi,
I have a 2014 SQL Mirror setup. The mirror is set up fine with a witness and auto failover. I am failing the database over and it is very quick, it appears as principal on the second server almost immediately and I can run queries against it.
My problem is however with the applications...
My application supports mirroring and I have the following connection string:
Data Source=10.0.x.x\INST; Failover Partner=10.8.x.x\INST;Initial Catalog=DBNAME;Database=DNAME;User ID=APPUSER;Password=xxxx;Network=dbmssocn
Now my problem is the following:
When i fail a DB over from principal to mirror, the application does not realise this very quickly. I see continuous login failures on the old princpal for about 4 minutes not a single request goes to the mirror during this time.Then all of a sudden the login failures will stop and the new principal is away and running and the application is fine.
During this 4 minutes or so i can run SQL queries on the new principal so the DB is definitely ready. The database is very small (about 6Mb with about 5Mb of logs).
Is this to be expected or is there a way of making it quicker. What I do notice is failing from failing back is sometimes instant, this is usually when going from Data Source to Failover Partner.
Regards,
Adam
Although there are a few questions similar to mine, I didn't find anything with these special circumstances, so I'll try a new thread:
We have an existing SQL 2008 Cluster with shared storage in a data center and we're moving this to a new data center. It's quite a bit of data (400GB+), and I'm looking for a way to move it over without extended downtime. Is there a way to add a third node perhaps to the cluster that's read only but syncs the data? As a systems administrator (this company just lost their DBA, so I'm short filling the role), I may be approaching this the wrong way, but anyway.
Any ideas?
Thanks!
ALTER DATABASE foo set PARTNER = 'TCP://10.3.3.1:1234'
The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed.
How to create index maintenance jobs in DB mirroring, as it doesn't support bulk-recovery?