Hi All,

We have x2 SQL 2012 servers configured in a mirrored setup and are using an offsite (non-domain) server as our witness.  This setup has been working fine for some time. Yesterday we had an internet outage which of course meant that the witness server could not be contacted by either of the SQL servers.  This was confirmed by going into management studio and seeing the witness listed as 'disconnected'.  Around 4 hours later the internet connection was restored and we could see the witness (from a networking perspective) but SQL server just refused to use it or acknowledge that it was up again.  We have run all kinds of tests that prove that the previous working configuration is still valid so why wont SQL accept the witness now that it can be contacted again?  Is there something we have to do on the x2 SQL servers to resume the witness functionality?

Any help greatly appreciated!

Cheers

Rob

can any one plz define me what is windows cluster and sql server cluster 

is there any cluster like sql server cluster

Kamal

We have an AlwaysOn Availability Group, with 3 nodes, one database, running SQL Server 2012 SP1 on Windows Server 2012 R2.  We have a client application written in C++, that uses SQL Native Client (ADO) to access the database.  We have been testing our client app in various AlwaysOn failover scenarios.  We have observed one odd scenario:

1. We create a table with over 2 million rows

2. Our client app issues a simple delete, to delete all rows in the table

3. After about 20 seconds, we perform a manual failover of the AlwaysOn availability group

4. The client application loses its database connection, as we expect.  However, instead of getting the usual error about communication link failure, the client gets this error:

I tried this same operation in SQL Server Management Studio, and I got the following messages:

I looked at the SQL Server error severity documentation, and it says that errors in the 20-24 range: "Indicate system problems and are fatal errors, which means that the Database Engine task that is executing a statement or batch is no longer running. The task records information about what occurred and then terminates. In most cases, the application connection to the instance of the Database Engine may also terminate. If this happens, depending on the problem, the application might not be able to reconnect."

Should the SQL Server Native Client report this "Remote harden of transaction failed" error to the client application, or should it translate this message into a known error code that indicates that the client lost its connection (such as "Communication link failure")?  If the Native Client should return this "Remote harden" error, can we rely on Native Error = 3303 to know that we've lost our connection?  

Thanks,

Heather

Hello,

I have setup sql 2012 clustering for a test env. The clustered instance is a named instance. Now I want to change it to the default instance. Is this possible without requiring a sql uninstall and reinstall?

Thanks

Hello,

My company are looking to implement some new SQL Always On AG's over the course of the next few months, all of the infrastructure will be located in Azure.  We would like to create and implement a level of DR into this solution and have as close to 100% uptime as possible from the start, I was wondering what people's thoughts are about this?

Initially we would be looking at a 2 node SQL always on AG, and then scale out to DR.  Ideally we would like the DR in another region.  We've been toying around with the idea of having potentially a 4 node AG, 2 located in one region and 2 for DR in another region, and setting the DR replicas as asynchronous?

Suggestions?

Marcus

II am developing an application for a waterborne shipping company. The main office is running SQL server 2008 and holds an employee database. They would like each ship to have access to the Db. Each ship is also running SQL 2008. In addition each ship will have multiple user needing update access to the Db.

I'm not sure it is smart (or even Possible) to sync between multiple copies of a SQL Server 2008 DB. I started (and am not opposed to using .net Sync Services, creating compact edition (.sdf) files on the servers and 'sharing' it with the users. The problem with this is the sdf file would have to be replicated on each user machine. This would make data integrity a challenge.

I should note that the ships are only occasionally connected to the internet, so working directly with the office db is not possible.

Does anyone have any ideas, or shoud I resolve myself to using a shared copy of a compact edition of the DB?

Thanks

Hi,

We have been getting the below error while restoring a database onto SQL Server 2008. We are using lite speed and performing a full restore. When we restart the server, the restore is completed cleanly but every 3 or 4 days once, the restore is failing. We have tried everything from installing a patch that was supposed to fix it but it is not.

Error Message:

BackupIoRequest::ReportIoError: read failure on backup device 'VDI_7D17E958-2468-45A8-B7F0-EB73D0BF0F3A_3'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

The backup is getting validated successfully but failing while trying to read it. Any help would be greatly appreciated.

Thanks,

Sree

I am new here and hope this is the correct forum for my post.  There are so many different forum that it is difficult to distinguish which is correct for my particular question.

I keep getting this error andd would like to know how to resolve it:

PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language
Runtime : 4.0.30319.261
System.Deployment.dll : 4.0.30319.1
(RTMRel.030319-0100)
clr.dll : 4.0.30319.261
(RTMGDR.030319-2600)
dfdll.dll : 4.0.30319.1
(RTMRel.030319-0100)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)

ERROR DETAILS
Following errors were detected during this operation.
*
[3/9/2012 5:27:01 AM] System.IO.FileNotFoundException
- The system cannot
find the file specified. (Exception from HRESULT: 0x80070002)
- Source:
System.Deployment
- Stack trace:
at
System.Deployment.Internal.Isolation.IsolationInterop.GetUserStore(UInt32 Flags,
IntPtr hToken, Guid& riid)
at System.Deployment.Application.ComponentStore..ctor(ComponentStoreType storeType, SubscriptionStore subStore)
at
System.Deployment.Application.SubscriptionStore..ctor(String deployPath, String
tempPath, ComponentStoreType storeType)
at
System.Deployment.Application.SubscriptionStore.get_CurrentUser()
at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri
activationUri, Boolean isShortcut, String textualSubId, String
deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String&
errorPageUrl)
at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
state)

I have setup only 2 servers to participate in HA.  All setup appears to be OK.  For the various testing, I wanted to take an individual server down and ensure that job related backups will still perform.  In the backup priority, I made the secondary server (lets call B) with a priority of 51 and the primary server (A) with a priority of 50.  For the option of where should backups occur, I use 'Prefer Secondary (which reads if the secondary is not availability then backup on the primary). 

First test was to take down A.  Everything worked as expected and I was able to execute backup jobs on B (which became the primary as expected).

Next test was to bring A up again and take down B.  Server A becomes the primary. This is where I have an issue.  Server A is up as primary but when I run the fn_hadr_backup_is_preferred_replica, I get a return value of zero. My guess is due to the backup priority but shouldn't the fact that I have no secondary server supercede the backup priority?  My jobs on server A will not create backup files.  I am on version 11.0.2100.60.  Any assistance would be definitely appreciated.  Thanks

Hi,

As far as i'm aware, MSTC is not supported with always on high availability in SQL Server 2012/14.

Are there plans for these features to be supported together and if so, when? If not, what are the options for providing MSTC and high availability fail over?

Thank you.

 I have a 2 vm node cluster and had to manually failover the cluster. We had to power down one of the nodes and it will have to remain powered down until we get some other issues resolved. So now the quorum on the active node appears to be in a confused state and won't come online. The disk shows up in cluster manager and disk management, but doesn't show up in snap drive. I am needing to have the active node take over the quorum so is there a way force ownership of the quorum to the active node? Thanks!

Salvador Diaz III

Sql Server Clustering is regarded as a High Availability, not "load balancing", option. What Sql "load balancing" solutions are available? (Sql Server 2012 Enterprise supports up to 16 nodes in a Cluster. I suspect that multiple nodes in this cluster could be "Active" and wonder if this is the path to load balancing in Sql)

TIA,

edm2

Hi all,

I have an interesting scenario.  I run a 2 node cluster (Windows 2012) with SQL 2012 SP1, which uses a SAN.  I need to create an availability group to have a set of these databases online on a standalone SQL server.  I have actually done this exact task in the past, but am struggling with an error message.  According to the Microsoft Technical group, this is 1 scenario which AlwaysOn may be used for (http://msdn.microsoft.com/en-us/library/jj215886.aspx).

So, I add a node to my 2 node cluster.  I then go into SSMS to configure the availability replica.  I get through the initial validation.  On the last step, I get an error.

-------------------

TITLE: Microsoft SQL Server Management Studio
------------------------------

Attempting to add availability replicas to the availability group resulted in an error. (Microsoft.SqlServer.Management.HadrTasks)

------------------------------
ADDITIONAL INFORMATION:

Create failed for Availability Replica 'USTAWVSHAGEMAN1\SQLCAD'.  (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.3000.0+((SQL11_PCU_Main).121019-1325+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+AvailabilityReplica&LinkId=20476

------------------------------

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Failed to create, join or add replica to availability group 'ag8', because node 'standalone' is a possible owner for both replica 'cluster' and 'standalone\SQL'. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again. (Microsoft SQL Server, Error: 19405)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.3000&EvtSrc=MSSQLServer&EvtID=19405&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

I can't seem to get by this error.  My disk configuration matches,  my user accounts to run SQL server identical on all machines involved.  I read somewhere that the standalone machine needed to be a named instance and not the default, so I added a named instance as well.  Everything brings me back to this error.

Failed to create, join or add replica to availability group 'ag8', because node 'standalone' is a possible owner for both replica 'cluster' and 'standalone\SQL'. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again. (Microsoft SQL Server, Error: 19405)

If anybody could please help, I would greatly appreciate it.

I have an environment with three SQL instances running an application. Two of the instances are enterprise edition and one is standard. I am looking to move all instances up to SQL Server 2012 and hoping to put them on a 3 node Windows Failover Cluster. I understand that standard edition is limited to two nodes. What I want to know is what my options are?

Can install standard edition on the cluster but only on two of the three nodes?

Do I need to create a second Windows Cluster? Is this even possible?

Regards, Matt Bowler MCITP, My Blog

I am having some troubles with the Sql VSS writer. I am using a 3rd party backup solution, and it is failing because each time a snapshot is attempted the writer (SqlServerWriter) fails with a non-retryable error. The same thing happens with the built in Windows Server Backup utility. There are a few notable entries in the Event Logs on the server. One names error 0x800423f4, the other0x80070005, which is an access denied error. Trouble is, the writer is set to run under the local system account, and the local system account has SysAdmin privileges on the databases. I've spent quite a few hours over the past week or two attempting to solve this and have had no luck. Any ideas where this writer is failing? This is a SQL 2008r2 install.

Thanks,

Josh

Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 18210
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BackupVirtualDeviceSet::Initialize: CoCreateInstance failure on backup device '{730A7E71-C123-4F80-A1E3-DEF2BDE8E112}3'. Operating system error 0x80070005(Access is denied.).

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
 PrepareForSnapshot Event

Context:
 Execution Context: Writer
 Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
 Writer Name: SqlServerWriter
 Writer Instance Name: SQL Server 2008 R2:SQLWriter
 Writer Instance ID: {e37d5783-6dd3-4bde-ae44-c179982fb65b}
 Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
 Process ID: 8984

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This is what the 'vssadmin list writers' command turns up for the SQL Writer after an attempted snapshot. Only way to recover it is to restart the server.

Writer name: 'SqlServerWriter'
 Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
 Writer Instance Id: {ac3d731f-6a0f-4537-8d6f-1ffad6dd9d8f}
 State: [8] Failed
 Last error: Non-retryable error

Trying to get MSMQ working in a SQL 2012 Cluster. We have two nodes, OS server 2012 R2, and an instance of SQL 2012 on each node. I can send test messages to private and public queues. However when trying to send message through a stored procedure call the message doesn't arrive to the receiving server. I keep getting a message queue service is not available. Any insight or documentation would be greatly appreciated.

Thanks

Now i am searching any tool, which recover all over data MDF file and R2 from SQL server.

DECLARE @DBName VARCHAR(64) = 'databasename'

DECLARE @ErrorLog AS TABLE([LogDate] CHAR(24), [ProcessInfo] VARCHAR(64), [TEXT] VARCHAR(MAX))

INSERT INTO @ErrorLog
EXEC sys.xp_readerrorlog 0, 1, 'Recovery of database', @DBName

SELECT TOP 5
         [LogDate]
        ,SUBSTRING([TEXT], CHARINDEX(') is ', [TEXT]) + 4,CHARINDEX(' complete (', [TEXT]) - CHARINDEX(') is ', [TEXT]) - 4) AS PercentComplete
        ,CAST(SUBSTRING([TEXT], CHARINDEX('approximately', [TEXT]) + 13,CHARINDEX(' seconds remain', [TEXT]) - CHARINDEX('approximately', [TEXT]) - 13) AS FLOAT)/60.0 AS MinutesRemaining
        ,CAST(SUBSTRING([TEXT], CHARINDEX('approximately', [TEXT]) + 13,CHARINDEX(' seconds remain', [TEXT]) - CHARINDEX('approximately', [TEXT]) - 13) AS FLOAT)/60.0/60.0 AS HoursRemaining
        ,[TEXT]

Now I am using this : en.mdfrepair.net

When you create a listener the IP address and port number combination always has to be unique for every listener.

I created two SQL Server 2012 EE instances on one Windows 2012 server. They both have the same IP address and node name (because it is the same server). They are not using the same port numbers. The first instance is using port 1433 and the second instance is using port 1435. That is working fine.

I created an availability group with one listener. The listener has a unique name and is using port 1433. That is also working fine.

I created a second availability group with one listener. The listener has a unique name and is using port 1433. That generates the following error message: “Create failed for Availability Group Listener ‘ag-list02’. (Microsoft.SqlServer.Smo) …  The configuration changes to the availability group listener were completed, but the TCP provider of the instance of SQL Server failed to listen on the specified port [ag-list02:1433]. This TCP port is already in use. Reconfigure the availability group listener, specifying an available TCP port. For information about altering an availability group listener, see the “ALTER AVAILABILITY GROUP (Transact-SQL)” topic in SQL Server Books Online. (Microsoft SQL Server,  Error: 19486)”

I wanted to create the following listeners:

Name                   IP address           TCP Port          Description

SQLServ1            10.1.1.10             1433                 Listener of Instance 1

SQLServ1            10.1.1.10             1435                 Listener of Instance 2

Ag-list01             10.1.1.11             1433                 Listener of Availability Group 1

Ag-list02             10.1.1.12             1433                 Listener of Availability Group 2

Every listener is using a unique IP address and port number combination.

Why is this not working?

Is there something special about availability groups and listeners? Does the general rule that you can use the same port number on different IP addresses not apply for availability groups?

Can I only use a port number once per fail-over cluster?

Dear All,

            I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.

1.  I am receiving MSDTC Warning.  I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not.  I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?

http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/

2.  During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME".  Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.

3.  During the instance creation, one needs to provide "SQL Server Network Name".  As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this for all instances that I create or this is only required once in the cluster:

4.  During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features.  As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so which features should be selected? so that there is less workload on the server.

5.  All the instances use TempDB for databases that are present inside it.  What would be the best practice with respect to TempDB.  One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What should be the ideal size of the TempDB LUN?

6.  Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?

Thanks in advance. 

Some new and fast features required for new Office migration tool. It is following points

• It is important that software support with all Windows OS
• Software work with 64 bit and 32 bit OS
• Software have new and advance features

Now I am try this: migrategroupwisetooffice365.net please check all over features of this tool.