Hi,
I have the master and msdb backup files of a broken server, as well as the .bak files of all other non system databases.
Now, in an online sql server, how do I retrieve the logins information from those .bak files?
Thanks for helpl
Jason
Hi,
I have the master and msdb backup files of a broken server, as well as the .bak files of all other non system databases.
Now, in an online sql server, how do I retrieve the logins information from those .bak files?
Thanks for helpl
Jason
My question is how to create logins on a replica server where the default database is not currently available i.e target for AlwaysOn, mirrorring, log shipping?
In order to reduce the amount of work (and diagnosis) in a DR event it is good to have all of the logins created and configured in advance but when the default database isn't available an alternative has to be used.
I'm assuming that the "default database" for a login is merely an entry in a table (whether it be a name or a DBID) so I'm unclear why this can't be set independently of the database being available. Is there some underlying functionality that occurs in the login or is this simply SQL Server preventing us from choosing an "invalid" database for our own good?!
Has anyone identified a workaround? Replica databases have been around for a while so this isn't a new issue.
Thanks.
Hi, I have set up Always on Availability Groups on top of Windows Server Failover Cluster(WSFC) with two sql server stand alone installations
Server1--Primary Replica
Server2--Secondary Replica
--Both above configured in Always on Availability Groups( listener name=AGListner)
Server 3-Remote Distributor Server where all sql agent jobs (Log,snapshot,dist jobs)...
Server 4--Subscriber server
Steps i have followed
I have setup Replication on Server 1 which was primary at the time of configuring replication to server 4(subscriber)
worked fine, replicated data, when failover happened Server 2 took over as primary and still replication worked fine...
my Issues are below and i am looking for some assistance
1.When i shout down Server 1(for testing), Server 2 took over the role as Primary and served the applications, but when i insert data at server 2( which is now primary), server 4 Subscriber did not get the data...once i turn on Server1 , the replication is replicated and subscriber is getting data ...does 2 servers(AG Servers) should be ruining in order to replication work?
2.and when i see the Replication monitor I see the All subscriptions are running, Agents are completed and running (ALL GREEN), also jobs on distributor are still running but server 4 Subscriber did not get the data..
can we join a node in a windows cluster which is already in a different cluster?
We have this requirement as we need to setup readable secondary ( always on AG) on the third node.
aa
Hi,
I have a Windows 2008 R2 Always on Cluster with 3 nodes (two in the primary site and one in the DR site).
Primary Site:
-Primary Site Server1
-Primary Site Server2
DR Site 1 (to be decommed):
-DR Site Server1
Our company is planning on decommissioning the DR site. But before we do this, we want to add a 4th site to the cluster. Migrate the data...and then decommission the original DR Site.
Is it possible to have this configuration:
Primary Site:
-Primary Site Server1
-Primary Site Server2
DR Site 1 (to be decommed):
-DR Site Server1
DR Site 2 (NEW DR Site):
-DR Site Server1
IF this is possible, do I simply add the new DR site to the existing cluster (same steps as adding the first DR node to the cluster when the cluster was originally configured? or are there special steps?
Thank you.
Hi, I have a very tricky question. We setup DB replication between 2 sql instances. For example, database A on SQL instance A was replicated to database A_repl on SQL instance B. Now I setup log shipping for database A on SQL A to database A (standby/read-only mode ) on SQL C. The interesting thing is: I can see database A_repl (on SQL B) is shown under local publications item on SQL C. But when I click its property, it said the subscription does not exist (of course not because I did not setup any replication on SQL C). I guess some replication info (between SQL A and SQL B) were transferred to SQL C due to log shipping. I also can't drop SQL A on SQL C (because it's in replication) unless I change to read write. I hope I explained clearly. Could anybody help me to find the reason?
If the database without replication was setup log shipping, no issue at all.
Thanks
David
Hi,
i have already install the sql 2008 r2 and the sql having share point 2013 /project server 2013 databases now i want to move this stand alone sql to cluster .Is it possible if yes then how?
please help me.
Hi,
I've set up a SQL server 2014 cluster with AlwaysOn availability groups. Upon creating the AG i opted for full syncronisation to a specific SMB share.
Now i want to change that share because it has to move to a new server. How can i do that? I found no settings in the SSMS for that.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights
W2012 R2 VM with 16vcpu and 128GB Ram and enabled dynamic memory and Using SQL 2012 with Resource Governor enabled to create a multi tenancy SQL Database service. Dynamic memory is used to cater for local Site Hyper-V host availability.
For Hyper-V virtualization have read the dynamic memory and Fixed memory designs for memory management for SQL 2012. My understanding is that SQL 2012 dynamic memory is fine as long as the correct configuration is applied for both SCVMM hyper-V and SQL 2012
memory settings.
Enabling Dynamic Memory with SQL resource Governor will this cause an issue? So far tests it has not but I have not seen any documentation or discussion on this. Is there an extra overhead in the SQL engine as it acquires the memory as part for that specific resource pool for example.
In short is best practice for using SQL 2012 Resource Governor enabled --> Is it Fixed memory or Dynamic Memory?
Hi,
One of our production databases was setup mirroring, log shipping and replication on it, the log file was setup unrestricted growth. This morning one index rebuilding process generated lots of logs, and the log file disk ran out of space, the database was in recovery mode. so we had to disable log shipping, pause mirroring and replication, expand log file disk, restarted SQL instance to fix the issue. Now we want to setup the log file to maximum size 80G, the whole log file disk is 120G. So if the log file reached 80G next time, we can change the max size to 90G or 100G and it's easier to fix the space issue. My question is, if the database log file reached max size,
1. is the database still available?
2. Will the active session causing the issue be rollback to release space back?
Thanks
David
Hi All
While evicting a node : Node2 (passive node) which is a part of SQL FCI, do we need to uninstall it (by clicking on remove node) or directly Evict the node?
We are using Windows server 2012 and SQL Server 2014 and it is a two node cluster.
Node1 - Active
Node2 - Passive
aa
Hi,
We have 2 clusters, 1 running SQL 2008 on Windows 2008 R2 server and 1 running SQL 2000 on Windows 2003 Server.
Because of a disaster with the disks, each of the passive nodes had to be rebuilt and Ive been asked to install SQL on the nodes.
Ive not done this before. Does this mean simply adding a new node to the cluster through the wizard? Or do I need to reinstall the entire cluster?
I think SQL 2000 is too risky as its unsupported, so Im going to resist that. But how should I approach the SQL 2008 Instance?
Thanks,
Zoe
I've got log shipping set up, and everything seems to be working fine, but the log files are not being deleted from the primary server despite configuring log shipping to retain them for 3 days. I see no errors concerning the log shipping, but did not configure a monitor. What process is responsible for deleting the older log backups, and how can I look for errors. I could simply set up a jog to delete the older files, but that will only mask the issue.
Thanks in advance for any help you can offer.
Hello experts,
I would like to understand if we want to buld a sqlserver mulitsite clustering if is mandatory to have or confiugre WSFC on all the nodes at each datacenter?.
Also, what would be the steps. we currently have a DC1 install SQL 2012 Always on AG (WITH 2 replicas), I have anohter DC2 where i would like to build teh multisite cluster with 2 nodes and want to know if is posible to incorporate the existing FCI that we have in DC1?
Hello Experts,
I am about to install a new failover SQL-Server environment (win 2012 \SQL 2008 Sp4) and after going to installation we found out that storage designed to map to over the number of drive letter alphabetic and was looking for your experience for which is more practical and best practice to follow , follow MS advised in this article https://support.microsoft.com/en-us/kb/947021?wa=wsignin1.0 or go with the straightforward scenario and adjust the storage design to be less than number of alphabetic characters.
Thanks
I have a 2 node cluster with 2 instances on them and everything has been running for a couple months, just fine. I needed to swap the drive letters for the cluster because of SQL mirroring, so I followed the MDSN procedures to change the drive letters. In Cluster Manager I changed the drive letters, then change the sql start up parameters for both instances and click start and now it can't find the drives. Like I said I only swapped the drive letters, nothing else. The error log on the cluster drive is written too, which also seems odd, that it can find the error log file, but not the database or log file and they are on the same cluster drive.
As a test I moved the master db to a local D:, changed the startup parameters and tried to start SQL, in the error log file, it found the master.mdf, but failed with the model database because as it was on the cluster shared drive. So it seems that it is around the cluster drives, from what I can tell anyway.
Thanks for any insight.