I am getting an error :

there is an insufficient memory to run this query Error: 701, Severity: 17, State: 42

The instance is SQL 2005 instance with SP2.

Please help.

Hi,

We have a cluster with 2 nodes. Everything works fine in Node1. When I try to failover TEST1 database to Node-2 it fails with this message.

Generic service 'Analysis Services (TEST1)' could not be brought online (with error '1060') during an attempt to open the service.  Possible causes include: the service is either not installed or the specified service name is invalid.

Any help is much appreciated.

Thanks

Dear All...................I have a two-2 node sql server 2012 sp1 failover cluster.........I need to turn "Always On" on one of the databases.

1.  Is it really applicable in this scenario?

2.  Would I get any benefit from it?

3.  Is it even possible?

thank in advance.

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

Hello,

I am using sql server 2012 Standard Edition in a test environment. It is a clustered env with faster san. Whenever I perform a failover of sql server services it takes about 30seconds and when I failback it takes around 35 seconds. I am only hosting 2 databases and they are 2gb and 500MB in size. This is a VM with 6GB memory. I reserved 4 gb max setting to SQL and left 2GB to OS.

I implemented instant file initialization and also reduced the number of vlf's to see if that helps to reduce the failover or fail back time.

Can some one please tell me how can I bring this time to less than 10 sec.

Thanks a bunch

I have 3 node SQL 2012 AlwaysOn Availability nodes with the 3rd node as Read-Only.

The backup job within SQL Maintenance plan is failing with the following error:

Failed:(-1073548784) Executing the query "declare @backupSetId as int
select @backupSetId =..." failed with the following error: "Cannot open backup device 'C:\\SQLDBName_backup_2014_06_08_170156_9292095.bak'. Operating system error 2(The system cannot find the file specified.).
VERIFY DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

I have verified the SQL AlwaysOn Backup preference to be "Prefer Secondary"

Is there any special steps/settings I need to do to setup and run the backups using maintenance plan in SQL AlwaysOn?

I have 2 SQL Server replicas configured on SQL Server 2012 AlwaysOn. e.g. SQL1 & SQL2.

I have configured backup job on both SQL Server with the following statement. and the job occurs every 10 minutes.

• declare @DBNAME sysname,@sqlstr varchar(500)
  set @DBNAME = 'dba'
  IF (sys.fn_hadr_backup_is_preferred_replica(@DBNAME)=0)
  BEGIN
        --Select 'This is not the preferred replica, exiting with success';
        RETURN -- This is a normal, expected condition, so the script returns success
  END
  --print '1'
  set @sqlstr = 'backup log dba to disk = ''E:\MSSQL\MSSQL11.MSSQLSERVER\MSSQL\Backup\dba_'+left(replace(replace(convert(varchar(30),getdate() ,126),'-',''),':',''),15)+'.trn'' with compression;';
  print @sqlstr;
  exec (@sqlstr)

I turned off SQL2 for Windows maintenance. So there is only SQL1 is online. Afterwards. I checked the backup folder and didn't see any new backup files was created after SQL2 was offline. I rerun the job. It still doesn't backup database on the Primary Replica.  Then I searched on SQL Server Book online. It says

Prefer Secondary
Specifies that backups should occur on a secondary replica except when the primary replica is the only replica online. In that case, the backup should occur on the primary replica. This is the default option.

According to what it says, it should backup on the Primary Replica. Does anyone experience this issue before?

Shawn

Hi ,

I have all my production databases in recovery model simple taking into account ,

• I am not using the normal backup strategy for recovery (third pary tool)
• My database is encrypted TDE

is there any value from changing the databases to recovery model full instead ??

I have SQL server 2012 enterprise installed according to Microsoft's installation guidelines on two Win Server 2012 machines with the AOAG functionality enabled. I've added several databases to an AOAG availability group.  The databases easily switch from one replica to another when I manually switch nodes between the SQL servers.  However, I'm having trouble with the Security Logins when switching databases between nodes.  They work fine when on the primary node/server but when I switch to the secondary node/server the Security Logins are not available.

What must I do to have the specific database security logins move (or be available) with the replica databases when switching nodes?

When adding a node to a SQL Server 2012 Standard edition cluster, how I do I identify the location for SQL server shared components and the rest of the SQL Server installation binaries?

I added a node to a one node SQL Server 2012 Standard edition cluster. The binaries went to the C: drive default location instead of the same location as on the first node. What did I do wrong?  The binaries/executes and share directory was suppose to go on a different drive.

What needs to be done so both nodes have the binaries/executables on the same drives and folders?

Context SQL 2005 used by TFS 2008.

Some weeks ago i setup a weekly full backup and a nightly differential backup. Things were going OK until i ran out of disk space which is because of huge xx_log.ldf files.

We don't actively use logs for roll backs, we can live with the rare event of loosing a day's data.

We are getting errors in the logs, details below ...

I urgently need to know how to control this log beast to get things back on track ?
i.e. delete / disable / control the size of these log files.

Thanks

===================================

Errors

Attempt to truncate logs

Typical T-SQL script

use TfsIntegration
go
backup log TfsIntegration
with truncate_only
dbcc shrinkfile (TfsIntegration_log, 1)
go

Not all but some with errors

Failed:(-1073548784) Executing the query "backup log TfsActivityLogging
with truncate_only
dbcc shrinkfile (TfsActivityLogging_log, 1)
" failed with the following error: "Could not locate file 'TfsActivityLogging_log' for database 'master' in sys.database_files. The file either does not exist, or was dropped. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Failed:(-1073548784) Executing the query "backup log TfsIntegration
with truncate_only
dbcc shrinkfile (TfsIntegration_log, 1)
" failed with the following error: "Could not locate file 'TfsIntegration_log' for database 'master' in sys.database_files. The file either does not exist, or was dropped. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Failed:(-1073548784) Executing the query "backup log TfsVersionControl
with truncate_only
dbcc shrinkfile (TfsVersionControl_log, 1)
" failed with the following error: "Could not locate file 'TfsVersionControl_log' for database 'master' in sys.database_files. The file either does not exist, or was dropped. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Failed:(-1073548784) Executing the query " backup log TFSWarehouse
with truncate_only
 dbcc shrinkfile (TFSWarehouse_log, 1)
" failed with the following error: "Could not locate file 'TFSWarehouse_log' for database 'master' in sys.database_files. The file either does not exist, or was dropped. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Failed:(-1073548784) Executing the query " backup log TfsWorkItemTracking
with truncate_only 
dbcc shrinkfile (TfsWorkItemTracking_log, 1)
" failed with the following error: "Could not locate file 'TfsWorkItemTracking_log' for database 'master' in sys.database_files. The file either does not exist, or was dropped. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Failed:(-1073548784) Executing the query "backup log TfsWorkItemTrackingAttachments
with truncate_only
dbcc shrinkfile (TfsWorkItemTrackingAttachments_log, 1)
" failed with the following error: "Could not locate file 'TfsWorkItemTrackingAttachments_log' for database 'master' in sys.database_files. The file either does not exist, or was dropped. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Failed:(-1073548784) Executing the query "backup log STS_Content_TFS
with truncate_only
dbcc shrinkfile (STS_Content_TFS_log, 1)
" failed with the following error: "Could not locate file 'STS_Content_TFS_log' for database 'master' in sys.database_files. The file either does not exist, or was dropped. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Full Backup Weekly Task

Check DB Integrity

Rebuild Index

Backup ALL databases
  Type: Full
  Overwrite Existing
  Destination Backup Device

Backup reporting services key

Truncate Transaction logs
e.g.
  use TfsActivityLogging backup log TfsActivityLogging with truncate_only dbcc shrinkfile (TfsActivityLogging_log, 1)
  (Note single line format, is this valid ?)

Errors

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_tbl_Namespace] ON [dbo].[tbl_Namespace] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF, ONLINE = OFF )
" failed with the following error: "The transaction log for database 'TfsVersionControl' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
The statement has been terminated.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Daily Diff Backups

Databases: All user databases
Type: Differential
Overwrite Existing
Destination Backup device

This seems to run without error

What recommendatations does anyone have for what login we should use to add databases for AlwaysOn AG and as a result it would become the owner of the databases? 

• Should we login with the 'sa' sql server login and have them all owned by 'sa'.  If we use 'sa', would there be issues it when it comes time to reset the 'sa' password?  (We had issues when using 'sa' for log shipping, log shipping broke when we chnaged the password.)
• Should we use the service account for the SQL Server service.
• Should we use a dedicated windows authenticated login in the sysadmin role on each of the instances participating in the group?

First off, thanks for taking the time to look at this, i've opened a ticket /w MS, but while i wait ...i though i'd pose the question to the forums as well

I have an issue whereby when my link between facilities drops for more than (not entirely sure, not long at all, minutes?) both cluster configurations I have seem to loose quorum and access to the desired "primary" databases is lost.

We are using AlwaysOn as a DR strategy, and I "THINK" my issue is that i need to change the vote level to 0 for anything but the primary SQL servers. 

Regardless if the replicas are online or not, i NEVER want the cluster to put the databases on the primary servers innacessible

I have two seperate Failover Clusters configured...

Cluster 1 = node majority

Server 1   > replicating to Server 3

Server 2   > replicating to server 3

When the wan link between facilities goes down (Server 1 and 2 are in one location, Server 3 is in a remote location) the quorum looses majority and ACCESS to server 1 and server 2's databases seems to go offline while its resolving

Custer 2 = Node and File Share Majority

Server 1 > replicating to server 2

Same scenario, Server 1 and Server 2 are in different facilities, when that link goes down, even with Server 1 and the File share being in the same site, the cluster looses quorum, and access to databases on Server 1 stops

I currently have three traditional FCI SQL 2012 instances within WSFC configured between two physical servers.  I am looking to add AlwaysOn Availability Groups functionality to one of these instances to be used for DR purposes.  The new SQL server will be a virtual node located at a site remote to the current FCIs on the physical nodes.  I am running into something which seem like it would be problematic but may just be making a mountain out of a mole hill.

Obviously the new virtual node needs to be added to the same WSFC containing the two physical nodes that run the three current FCIs.  When I join the virtual node to the WSFC, the virtual node is added as a selected possible owner to most of the resources in the three current FCIs (e.g. SQL Server (INSTANCE), SQL Server Name and IP address, Cluster Name and IP Address, etc.)  The virtual node is also added as an unselected possible owner on the shared disks, unselected obviously because it doesn't have access to the physical storage that presents those disks.  For obvious reasons, this virtual node should never ever own any of the existing FCIs' resources.  I just want the virtual node in the WSFC for AlwaysOn AG purposes.  Should I go through all the existing FCI resources and deselect the virtual node as possible owner, even the Cluster Name and IP Address?  It seems bad that a new node to a WSFC should automatically be added to resources of the existing FCI services when there is no way that the new node could ever own those services.

hello,

I implemented log shipping in our server the process of implementation went fine but when I view job history I found

Message
2014-06-11 12:00:01.53    *** Error: Could not retrieve backup settings for primary ID '99817903-626e-4380-bcf1-c09ca6f48b6d'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2014-06-11 12:00:01.53    *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2014-06-11 12:00:01.53    *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2014-06-11 12:00:01.53    ----- END OF TRANSACTION LOG BACKUP   -----

Exit Status: 1 (Error)

also I check for database ID using select * from msdb..log_shipping_primary_databases

your help is appreciated.

Please Mark it as Answered if it answered your question
OR mark it as Helpful if it help you to solve your problem
Elmozamil Elamir Hamid

MCSE Data Platform
MCITP: SQL Server 2008 Administration/Development
MCSA SQL Server 2012
MCTS: SQL Server Administration/Development

MyBlog

Hi

We have created a new sql cluster server.After configuration we have created a db on the server.

After some days we tried to create the db and restore the db.But we are getting the below errors.

While restoring from a drive observed below error.

Error:cannot access the specified path or file on th eserver.verify that you have necessary security privileges and that the path or file exist

While creating new db

cannot use file 'path:*****.mdf' for cluster server.only formatted files on which the cluster resource of the server has a dependency can be used.Either the disk resource containing the file is not present in the cluster group or the cluster resource of the sql doesnot have a dependency on it.
create database failed .some file names listed could not be created.check related errors.(microsoft sql server,error:5184)

On active node c drive and quorum drives are offline.On passive node both are online.Remaining other drives are in online on active node.We have kept the user and sys db  files on other drives.

Is this causing issue.please share if there are any links related to this issue.

Initially there was an error for .NetFX3.5. Although installation successful with some error because .NetFX3.5 was not installed. After installing .NetFX3.5 I was trying to install SQL but below error comes and does not allow to proceed.

Please help.

Hello,

I am upgrading from SQL 2008 R2 SE to SQL 2012 SE. I am backing up databases, scripting out logins, linked servers and sql agent jobs. However I plan on detach and attach the databases.

Also, I have a transaction replication setup in sql 2008 r2 with subscriber and publisher and distribution on the same server. How do I move this setup after I upgrade to SQL 2012 SE?

Any steps that I shd follow are highly appreciated.

Thanks a bunch in advance