[SQL 2012] Sql 2010 AlwaysOn Availability Group |
- Sql 2010 AlwaysOn Availability Group
- EXTERNAL REFERENCE OF EXECUTE PACKAGE TASK OF 2012 ISSUE
- AlwaysOn: automatically add new databases to SQL 2012 AlwaysOn by script/T-SQL or PowerShell
Sql 2010 AlwaysOn Availability Group Posted: 17 Apr 2013 05:48 PM PDT Hello Guys,I am about to implement sql server 2012 AwalysOn Availability group and my question is around storage. Does AlwaysOn availability group work with Shareddisk or only disk that are local to the computer(node)?Thank you |
EXTERNAL REFERENCE OF EXECUTE PACKAGE TASK OF 2012 ISSUE Posted: 17 Apr 2013 05:30 PM PDT while using execte pakage task in 2012 i face a problem. The project reference in this task works fine but external reference is showing error and i have to use this external reference if i try to call a child pkg from parent pkg when both the pkg are in different project solutions. pls give me solution of above issue..... |
AlwaysOn: automatically add new databases to SQL 2012 AlwaysOn by script/T-SQL or PowerShell Posted: 17 Apr 2013 06:34 AM PDT Greetings! I've installed and successfully configured our SQL 2012 AlwaysOn 2-node servers for our new "Intranet" that is coming out. I've gotten AlwaysOn working great, and our Front End servers for the Intranet will be using SharePoint 2013. The glitch is that SharePoint 2013 is configured to add databases automatically to our SQL Server 2012 back end, but NOT to AlwaysOn. In reading about this and in contacting Microsoft MSDN support, the default answer is "you must manually find, select, back-up and then add those new databases individually to get them into AlwaysOn." But wait; that can be quite a task, constantly checking the SQL Back-end servers to see what databases were created, then having to add them into AlwaysOn, 7/24! I'm looking for a script or process that will check for new databases, back those new databases up in FULL mode, (for being added to AlwaysOn, of course) then add those databases to AlwaysOn, all automatically. Or have this run every...1-2 hours? (without user intervention)What I've come up with so far is this script that actually identifies the newly-added databases, (not yet in AlwaysOn), and then backs them up to a shared location. My next task is to find those newly-added databases and through the various processes needed, get them added to AlwaysOn. This will involve some sort of looping action, I imagine. I'm not a T-SQL/scripting guru; is there any solution or script that I might access that would do this? (add databases to AlwaysOn automatically)? Please advise, I'm sure I'm not the first person to have this issue. I have seen previous posts on various Internet Sites, and the solution is "sure, go ahead and just script that!". Thanks, but I need just a little more detail there.Thanks again, -AllenDECLARE @name VARCHAR(50) -- database name DECLARE @path VARCHAR(256) -- path for backup files DECLARE @fileName VARCHAR(256) -- filename for backup -- specify database backup directorySET @path = '\\atel-web-be2\backups\' DECLARE db_cursor CURSOR FOR select name from sys.databaseswhere group_database_id is null and replica_id is null and name not in('master','model','msdb','tempdb') OPEN db_cursor FETCH NEXT FROM db_cursor INTO @name WHILE @@FETCH_STATUS = 0 BEGIN SET @fileName = @path + @name + '.BAK' BACKUP DATABASE @name TO DISK = @fileName FETCH NEXT FROM db_cursor INTO @name END CLOSE db_cursor DEALLOCATE db_cursor |
You are subscribed to email updates from SQLServerCentral / SQL Server 2012 / SQL 2012 - General To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |
No comments:
Post a Comment