Recovery :: AG Multiple Instances On Each AG Member
Jul 15, 2015
I am looking for information on setting up multiple instances of SQL 2014 on a single server and then adding each of those instances into availability groups. Is this supported?
Currently I have a test environment with 3 SQL 2014 servers and a domain controller. The 3 SQL servers are in a WSFC and I have an availability group setup for 3 databases. This setup works great. Now to add another level of complexity to this, I would like to install another SQL instance on each of the 3 SQL servers and then build another availability group for this new instance. Is this possible?
My environment has a 4 node cluster , 2 in primary and 2 in sec dc. Storage is sperate for both.
Need to setup always on for 4 Instances there on the 2 nodes of the primary dc. Is there any restriction in setting up always on for multiple instances for a cluster.
Is it possible to have more than one instance of SQL Server on a failover Active/Passive cluster? What are the concerns/ramifications if that indeed is possible?
My ambition is to run ASPStateInMemory with durability on, supplementing the in-memory database with an on-disk version to give session state persistence when and if the clustered instance of SQL runs into, say a network card failure and needs to fail to a partner node. I understand that DAG's are usually run between standalone instances of SQL running on different machines. But, can I combine the DAG with the FCI? Instead of using a remote standalone SQL server, can I just another instance in the same cluster?
I have a 2012 AlwaysOn DB Mirroring environment set up with two nodes. Both have 5 installs of SQL named instances.
The issue we are having is when we patch one server and fail everything over, some of the applications will error. Some of the applications had to have their web.config files updated with hostinstance name because it seems to not work with DNS.
We are running with a 2 node windows cluster having three SQL instances on it.
OS: Windows server 2008R2 SP1 SQL : SQL server 2008R2 (10.50.6529)
Currently both nodes have 256 GB or memory and we are having multiple auto failover for resources. What will be the best practice for OS memory reservation (OS+tools) so that we can set SQL max memory settings accordingly?
I think this is a question for the specialists among us.
Can I use one general reporting server (installed on instance MAINREPORTING) for multiple customers who all have their own sql instance (CUST1, CUST2, CUST3, ..) I would use UserAuthenciation on the reportserver url to display the specific reports customers can use.
Is this possible, and what do i have to take care off concerning installation and/or configuration (especially on the reporting side) ?
A very basic MDX question. Using the following from AdventureWorks as an example:
Code Snippet WITH MEMBER [Measures].[Big Cities] AS ( [Geography].[City].&[New York]&[NY] , [Measures].[Internet Order Count] ) SELECT [Measures].[Big Cities] ON COLUMNS , [Customer].[Total Children].Children ON ROWS FROM [Adventure Works]
How would I re-write the [Measures].[Big Cities] calculated member so it included both [Geography].[City].&[New York]&[NY] and [Geography].[City].&[Los Angeles]&[CA]? Assuming there is no logical connection between these members, and that they are non-contiguous. Also, in my real example, I cannot move [Measures].[Internet Order Count] to the WHERE clause, it must remain within the calculated member.
I installed SQL 2005 SP2 + ReportServices Add-in for Sharepoint (WSS 3.0). All it's OK until I try to grant database access in the Sharepoint Central Admin site.
I setup the Reporting Services Integration (Manage integration settings). I use the default SQL instance, I put the USERNAME and the PASSWORD of my ADMIN account in the ENTER CREDENTIALS windows.. When I click the "OK" button, I receive always the error ...
"A new member could not be added to a local group because the member has the wrong account type"
I installed SQL 2005 SP2 + ReportServices Add-in for Sharepoint (WSS 3.0). All it's OK until I try to grant database access in the Sharepoint Central Admin site.
I setup the Reporting Services Integration (Manage integration settings). I use the default SQL instance, I put the USERNAME and the PASSWORD of my ADMIN account in the ENTER CREDENTIALS windows.. When I click the "OK" button, I receive always the error ...
"A new member could not be added to a local group because the member has the wrong account type"
i have sql server 2005 express running. during install, i had issues with a system dll that i found answers online and resolved. i am still very green, but i know much more now than i did at the time. i believe that as a result of the partial then failed installs i have multiple instances either fully or partially installed. when i am in the sql server mgmt express environment, it lists two sql engines. i only ever use one, and would like to safely remove the second without damaging or corrupting anything done with the other instance. my reasons for wanting to do this are twofold. first, i would like to free up the drive space taken up by the second instance. (i am a stickler for clean harddrive mgmt and maintenance). second, now that i have used the software and am somewhat more familiar with it, i would consider installing a second, intentional instance so that i may attempt to better customize some of the install-time settings and configurations. can anybody give me any pointers/ guide me in the direction of information on how to SAFELY go about this? thank you in advance for any help.
I created a second SQL2000 instance on a Windows 2000 server. The strange thing is that I can create an ODBC connection to the default instance but cannot for the new named instance. If I try from a client that has SQL installed on it, I can see both instances. Any idea why this is happening?
We're trying to decide if we should use a single large instance of SQL Server or multiple instances on the same server. This is for a dev environment.Have to limit max RAM per instance so no instance grabs it all.There will be I/O contention and CPU contention between instances since the different instances won't coordinate with each other.It limits the available RAM for In-Memory tables..It sets lower limits to the amount of RAM available for any given query, causing artificial "contention" even when there's nothing else running at the time.
According to the Task Manager, on my SBS 2003 Server, I'm running multiple instances of SQL. How do I determine which instance(s) are required to maintain server stability, and which are not. My Server resource use continues to be a perennial problem. Please advise.
Is it possible to have multiple instances attach the same database?
I have a scenario where I want to have on one node, a clustered instance and a non clustered instance and both instances attach the same singular DB on a filer.
If I want to install 2 instances of SQL2000, will it install the SQL2K executable files (inn folder) onto 2 different folders, or all instances in one folder but the databases are in different folders.
Please Help me on this. I installed the two instances SQL on one box. ONe is default instance called ACSQL1(actually machine name) and the other one is called ACSQL1/DEVELOPMENT. THrought the my client site of SQL 2000 I can access both instances. When I try to get connection from VB. I can access the default instance but I can not access the second instance. Any ideas about this??? Qun Lu
I am running SQL 7.0 as the default instance and SQL 2K as a named instance. Each is using a different port....7.0 is using port 1433 and 2K is using 1024. Everything appears to be up and running fine on the server. However, I am not able to access the 2K instance from a client. I have tried to use both TCP IP and named pipes setting them up using the server network utility and the client network utility. No luck anywhere. I continue to get connection errors...check network documentation...
Currently, I am running SQL Server 2000 with the default instance. I know SQL2K can run up to 16 instances simultaneously. I would like to add another instance but am unable to find documentation on how to add it. Books online tells me "about" multiple instances, but not how to set it up. I've obviously missed something somewhere. Can someone please direct me to a document that will help explain "how" to add another instance?
We have a DTS package that is submitted every minute by a SQL Agent job (2000). We see instances where before the first job is completed, the second one starts running.
Has anyone encountered this type of behavior before?
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
Is there any limit on SQL server Multiple Instances? if we require to run 60+ Instances on single machine what will be the minimum hardware requirements.
Has anyone run SQL 2005 Standard Edition, 2 or more instances on one server... where you got the extended memory up to 2.8 GB on EACH instance of SQL Server? I've done the 2.8GB game on boxes with ONE instance, but don't think I tried it on a multi-instance box, to get the 2.8GB RAM each. Thanks, Bruce
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
Himy first post in the data access forums, I really hope, someone can enlighten me here...I have a windows server 2003 running with 15 MSDE instances. No I would like to upgrade to SQL Server 2000 without crashing the existing instances... My perfect scenario woudl be- install sql server as new instance- move existing databases via detach / attach to the new instanceWill that work?
I need to put sql server 2000 enterprise and sql server 7 on the same box. For multiple instancing is it better to run with Win 2k Pro Server or Advanced Server. Please Elaborate.
Hi everybody. One of department want to place db application from one server somewhere else on corparation network for 3 month period. Problem is they want to keep it with max security. Company does not want set up another server , so we want to create another Instance and place database on it. 1. Is safe to keep 2 instances on same server ? 2. How remove access to this instance from members of local and domain admin role(If we deny acces to BuildInAdministrators how it is going to affect security?) Thank you
1.) Is it possible to install Analysis Services on multiple SQL Server 2000 instances? If it is, then can you instruct me as to how to perform the install. If it is not possible, then does one restrict access to cube data via the Database Role Manager?
ie. The host box is - DOILAB30 with Analysis Services & SP2 Instance - DOILAB30/DOILAB30_FIN (Can AS be installed here?)
Do I severely restrict the membership of OLAP Admins?
2). Re. AS maintenance. - How do I backup and restore OLAP dbs/cubes etc. Following a restore, what issues, such as cube users/permissions should I be aware of? (if any).
