Best Practice SQL Alias with Named Instance

Hi
We have a SQL server, "MySQLServerName" with a named instance, "MySQLInstance", running on port "12345".
I've created an SQL alias of "MySQLAlias" pointing to "MySQLServerName" Port on "12345" and it works.
But should I have used "MySQLServerName\MySQLInstance" Port "12345"?
Which is best practice?
Thanks
TJ

As SQL Server named instance supports both static and dynamic ports, i think you can use the port number specified by you. By default, a named instance of SQL Server listens on a dynamic port. For a named instance of SQL Server, the SQL Server Browser service
for SQL Server 2008, SQL Server 2005, or the SQL Server Resolution Protocol (SSRP) for SQL Server 2000 is always used to translate the instance name to a port, regardless of whether the port is static or dynamic. The Browser service or SSRP is never used for
a default instance of SQL Server.
Refer http://support.microsoft.com/kb/823938
Regards, RSingh

Similar Messages

MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

Hi,
I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance. The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
DNS dynamic update is disabled and an "A" record is registered with the dns. While trying to connect to the instance using the management studio:
Successfuly able to connect using the instance name, the production hostname, production IP and backup IP.
but while trying to connect to the insance using the backup hostname getting the below error:
"Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
This is required for the backup tool to get connected using the backup FQDN of the server.
Should I need to create a host name alias, request you to kindly assist me with the best recommedation to fix this.
http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

Hi,
It might be a kerberos issue. Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
Thanks, Andrew
My blog...

ADMIRAL database on SQL 2008 R2 Named Instance

Hi,
we are running TES 6.1.0.133 (test Master) upon a remote SQL 2005 SP4 named instance database, all is right.
I need to move the ADMIRAL database to an SQL 2008 R2 SP1 named instance.
What JDBC, JRE and connection string do I need to succeed ?
The versions are JRE 1.6.0.30, Microsoft JDBC 4.0.
thank in advance you for your experience,
Frederic

You should probably ask Cisco to help you through this they can likely provide you with an updated document and jar file
You will need to update your master.props settings.
You will need potentially need a new jar
Perform on a maintenance weekend with a maximum amount of recovery time
I have a Cisco doc and Zip files from 2010 when we did this but it is likely a different JAR that you would want to apply now.
What I would think are the Sequence of events (disclaimer Cisco would be best source of sequence, order, etc)
set system queue to zero
close all client sessions
stop master services
kill all connections to Admiral database
backup admiral database
set database offline and rename
Restore admiral database backup to new target SQL server 2008 instances
Creare a backup of master.props
Apply Jar to update master / SQL scripts (if supplied by Cisco)
Update master.props with new settings
JdbcURL=jdbc:sqlserver://:;selectMethod=cursor;databaseName=Admiral (or Admiral DB name)
There could be other setting that may also need to chance
Start Tidal Master make sure it is running
Connect Client
Verify Connections
Turn on System Queue slowly ramp up from a few to your standard level

Sql server with multiple instance

hi All,
i want to install sql server with two instance and i want to assign two separate is ips for both default instance and named instance and both should work like
two different server
note: If i logged with one ip(default instance) it should show its own databases not both or named instance databases
thanks
chintala

Hi chintala,
According to your description, if you want to assign the two different IP to stand for default instance
and named instance, I recommend you set up aliases on a SQL Server with multiple instances. For example, a physical server is named WinServer and 2 instances of SQL Server named WinServer and WinServer\instance1.
We need to add 1 IP addresse to the WinServer, there is one IP address already assigned to WinServer, 192.168.1.1, by adding one new IP's, 192.168.1.2 .
We need to move into DNS to configure our host names and aliases. The physical machine must be steup as a static IP in DNS. SQLAlias1, which point to the default instance on WinServer, will be setup as a DNS with an address of 192.168.1.1.
SQLAlias2, which will point to WinServer\Instance1, will be setup as a new Host (A) record in DNS with an address of 192.168.1.2.
When everything has been completed on the DNS side, you need to open up SQL Server Configuration Manager on WinServer and configure the protocols for each instance one at a time, restart the 3 SQL services.
For more information about how to set up aliases on a SQL Server with multiple instances, you can review the similar article.
http://kevine323.blogspot.com/2013/08/setting-up-aliases-on-sql-server-with.html
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Error while Connecting report Best Practices v1.31 with SAP

Hello experts,
I'm facing an issue while trying to connect some of my reports from Best Practices for BI with SAP.
It only happens when it's about info sets, the other ones that are with SAP tables go smoothly without a problem.
The most interesting is I have already one of the reports connected to SAP info sets.
I have already verified the document of steps of creation of additional database that comes with BP pack. They seem ok.
Here goes what Crystal Reports throws to me after changing the data source to SAP:
For report "GL Statement" one of the Financial Analysis one which uses InfoSet: /KYK/IS_FIGL_I3:
- Failed to retrieve data from the database; - click ok then...
- Database connector error: It wasn't indicated any variant for exercise (something like this after translating) - click ok then
- Database connector error: RFC_INVALID_HANDLE
For report "Cost Analysis: Planned vs. Actual Order Costs" one of the Financial Analysis one which uses InfoSet: ZBPBI131_INFO_ODVR and ZBPBI131_INFO_COAS; and also the Query CO_OM_OP_20_Q1:
- Failed to retrieve data from the database; - click ok then...
- Database connector error: check class for selections raised errors - click ok then
- Database connector error: RFC_INVALID_HANDLE
Obs.: Those "Z" infosets are already created in SAP environment.
The one that works fine is one of the Purchasing Analysis reports:
- Purchasing Group Analysis -> InfoSet: /KYK/IS_MCE1
I'm kind of lost to solve this, because I'm not sure if it can be in the SAP JCO or some parameter that was done wrongly in SAP and I have already check possible solutions for both.
Thanks in advance,
Carlos Henrique Matos da Silva - SAP BusinessObjects BI - Brazil.

I re-checked step 3.2.3 - Uploading Crystal User Roles (transaction PFCG) - of the manual where it talks about CRYSTAL_ENTITLEMENT and CRYSTAL_DESIGNER roles, I noticed in the Authorizations tab that the status was saying it hadn't been generated and I had a yellow sign, so then that was what I did (I generated) as it says in the manual.
Both statuses are now saying "Authorization profile is generated" and the sign is now green on the tab.
I had another issue in the User tab (it was yellow as Authorizations one before generating)....all I needed to do to change to green was comparing user (User Comparison button).
After all that, I tried once more to refresh the Crystal report and I still have the error messages being thrown.
There's one more issue in one of the tabs of PFCG transaction, it is on the Menu one where it is with a red sign, but there's nothing talking about it in the manual. I just have a folder called "Role menu" without anything in it.
Can it be the reason why I'm facing errors when connecting the report to SAP infoSets? (remember one of my reports which is connected to an infoSet works good)
Thanks in advance,
Carlos Henrique Matos da Silva - SAP BusinessObjects BI - Brazil.

Best practice for dealing with Recordsets

Hi all,
I'm wondering what is best practice for dealing with data retrieved via JDBC as Recordsets without involving third part products such as Hibernate etc. I've been told to NOT use RecordSets throughout in my applications since they are taking up resources and are expensive. I'm wondering which collection type is best to convert RecordSets into. The apps I'm building are webbased using JSPs as presentation layer, beans and servlets.
Many thanks
Erik

There is no requirement that DAO's have a direct mapping to Database Tables. One of the advantages of the DAO pattern is that the business layer isn't directly aware of the persistence layer. If the joined data is used in the business code as if it were an unnormalized table, then you might want to provide a DAO for the joined data. If the joined data provides a subsiduray object within some particular object, you might add the access method to the DAO for the outer object.
eg:
In a user permissioning system where:
1 user has many userRoles
1 role has many userRoles
1 role has many rolePermissions
1 permission has many rolePermissions
ie. there is a many to many relationship between users and roles, and between roles and permissions.
The administrator needs to be able to add and delete permissions for roles and roles for users, so the crud for the rolePermissions table is probably most useful in the RoleDAO, and the crud for the userRoles table in the UserDAO. DOA's also can call each other.
During operation the system needs to be able to get all permissions for a user at login, so the UserDAO should provide a readPermissions method that does a rather complex join across the user, userRole, rolePermission and permission tables..
Note that f the system I just described were done with LDAP, a Hierarchical database or an Object database, the userRoles and rolePermissions tables wouldn't even exist, these are RDBMS artifacts since relational databases don't understand many to many relationships. This is good reason to avoid providing DAO's that give access to those tables.

Best practices in Internal table naming convention GT , GS , LT , LS ??

Hi Gurus,
 Are GT_ , GS_ , LT_ , LS_ --- the Best practices in Internal table naming convention ????
 I have seen this naming convetions adhered in standard programs .
 What each one of the below signify
 GT_ , GS_ , LT_ , LS_ ???????
Regards
Jaman
Message was edited by:
 ABAP Techie

Hello
I use the following naming conventions:
- G = global variable
- L = local variable
- T = internal table
- S = structure
- D = field
That's how the combinations look like:
- GT_ITAB = global itab
- GS_STRUC = global structure
- GD_FIELD = global field
- LT_ITAB = local itab
- LS_STRUC = local structure
- LD_FIELD = local field
Function module parameters have to stick to the following rules:
- I = importing
- E = exporting
- [C = changing -> never used]
- IT_ITAB = imported table type (itab)
- IS_STRUC = imported structure
- ID_FIELD = imported field
- ET_ITAB = exported table type (itab)
- ES_STRUC = exported structure
- ED_FIELD = exported field
Depending on their semantics TABLES parameters look like:
- IT_ITAB = imported data
- ET_ITAB = exported data
- XT_ITAB = changing data (import & export)
Here are the conventions for FORM routine parameters:
- UT_ITAB = using itab (data are usually treated like constants; no changes will be transfer - although possible - to the calling program)
- CT_ITAB = changing itab (if it is semantically an exporting itab then one of the very
first statements in the routine is: REFRESH ct_itab. )
- US_STRUCT
- UD_FIELD
- CS_STRUCT
- CS_FIELD
Conventions for class/interface parameters:
- IT_ITAB = importing table type
- IS_STRUC = importing structure
- ID_FIELD = importing field
- ET_ITAB = exporting table type
- ES_STRUC = exporting structure
- ED_FIELD = exporting field
- RT_ITAB = returning table type
- RS_STRUC = returning structure
- RD_FIELD = returning field
Conventions for class/interface attributes:
- MT_ITAB = table type
- MS_STRUC = structure
- MD_FIELD = field
- MC_CONST = constant
Question: Are there any advantages of such elaborated naming conventions?
My answer to this question is: Yes, definitively.
I believe that the advantage of semantically differentiating TABLES parameters of function modules is quite obvious:
CALL FUNCTION 'Z_BAD_NAMING'
 TABLES
 itab1 = ...
 itab2 = ...
 itab3 = ... .
CALL FUNCTION 'Z_GOOD_NAMING'
 TABLES
 it_itab1 = ...
 et_itab2 = ...
 xt_itab3 = ... .
I also believe that my naming conventions clearly enhance readability and maintainability of my programs.
Regards
Uwe

Best practice to deal with computer or departed employee

Dear All,
I would like to inquire about the best practice to deal with computer and computer account of a departed employee. should be disabled, reset, deleted, or just kept as it is until it is needed by another user?
Regards
hiam
Hiam

Ultimately your needs for their identities and equipment after they leave are what dictate how you should design this policy.
First off, I recommend disabling the account immediatly following the employee's departure. This prevents the user from using their credentials to log on again. Personally I have a "Disabled Users" OU in Active Directory. When I disable accounts
I move them here for easy future retrieval.
It is possible the user may return, or if they have access to certain systems you may need the account again. I would keep the accounts for a specific amount of time (e.g. 6 months, but this depends on your needs) and then delete them after this period of
time.
If the employee knows the passwords to any shared accounts (not a good idea though many organizations have these) or has accounts in other systems that do not use Active Directory authentication, immediately change the passwords to these accounts again following
the employee's departure.
If the employee had administrative access to their computer (not a good idea, though is the reality in most cases) you should disable the computer account and remove it from the network. This will prevent the employee from remotely accessing the machine
until you are able to rebuild or inspect it for unapproved changes.
Ask the user's manager, team members, and subordinates if there are any files that the employee would have stored on their computer. Back these up as necessary.
Most likely you will reuse the computer for another employee. For best results you should use an image so you can re-image their machine and not have to worry whether they had installed any unwanted software (backdoors, viruses, illegal software, etc).
Hope this helps.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Best practices of integration with SAP Netweaver

Hi All,
I'm totally new to SAP Netweaver but I have a task to integrate our system with SAP ECC (R/3). We are using SAP Netweaver 6.4. The goal of integration is to provide for user list of available modules (Sales and Distribution, Human Resource, Payroll, etc) and when user selected for example Payroll we need to display list of available BAPIs. In general weare able to create Enterprise Web Service for some BAPI and consume it. But the problem is that everytime when administrator changed BAPI process (for example added new field to Business Object) we need to regenerate wsdl and change our client application. Does Netweaver provide some Web Service which can retrieve list of applications, list of BAPI processes and can retrieve meta data of some BAPI? Something like Partner Web Service interface?
We are looking for best practices of integration with SAP Netweaver. We are trying to develop something like adapter which will be able to pull data into SAP ECC system is there any generic way to develop this adapter?
Thanks in advance for your help.
Yura.

Hi Yura !!
As far as I know, this is not possible yet. Using SAP Netweaver XI/PI, although it adds value to the webservice scenario exposing BAPI functionality, it also needs to maintain a refreshed version of the BAPI definition in its repository. Depeding the complexity of the change in the BAPI structure, maybe PI may allow you to continue working without changes.
Maybe a good practice is not to make too much changes to a production BAPI, instead make a review in development environment, and once it is stable, use it in production. Other good practice is to keep older versions of BAPIs and add the changed ones as new versions to have back-compatibility
Regards,
Matias.

What is the recommended static port range for SQL Server 2008 to SQL Server 2014 named instance?

I want to assign a static port to SQL Server 2008 to SQL Server 2014 named instance. Should the port be greater than 49151? The following links give contradicting information:
https://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx
Avoid numbers greater than 49151 which Windows might select for other purposes.
https://technet.microsoft.com/en-us/library/ms345327(v=sql.100).aspx
Port numbers should be assigned from numbers 49152 through 65535
Thanks..

I would still pick a port number below the ephemeral list (dynamic port usage [41952-65535]) as it'll reduce the chances of having a port collision when SQL Server starts up.
Also, I'd stick to lower numbers if possible (<25,000) as some firewalls skew higher port numbers to be more malicious (if heuristics are used).
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

SCCM central site and primary site use the same SQL SERVER with two Instance.

Hi Guys,
I want deploy SCCM 2012 central site and primary site in my domain. But Only one Sql server for me. Any one can tell me how to install the central site server and primary site server with the same SQL SERVER with two instance.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Sean Xiao
TechNet Community Support

Although you can install like the configuration you said above, we do not recommend you do it this way. If your SQL box has problems, all the data will go away and you will not have data redundancy.
You need to configure the different SQL Port and SQL Broke service port e.g.
SQL port 4023 SQL Broke Service port 4022 for CAS instance
SQL port 4024 SQL Broke Service port 4021 for PRI instance
Juke Chou
TechNet Community Support
I agree with Johan and this configuration should not be used. But I want to clarify that the default ports for "SQL port" (actually, SQL over TCP) is 1433 and the SQL Broker Service uses 4022. The configuration above should work but the "correct" would be
to use 1433 and 4022 for the CAS and 10434 and 4023 for the Primary :)
You can read more about Network Ports used by Configuration Manager here
http://technet.microsoft.com/en-us/library/hh427328.aspx#BKMK_CommunicationPorts
/Tim
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

Best practice for dealing with Recordsets, JDBC and JSP?

I've spent the last three years developing web apps using JSP, Struts and Kodo JDO for persistence. All of the content for the apps was created as Java objects using model classes and saved to an Oracle db. Thus, data retrieved from the db was as instances of the model classes and then put into Struts form beans, etc.
I changed jobs last month and am now having to use Servlets with JDBC to retrieve records from db tables and returning it into Recordsets. Oh, and I can't use Struts in my JSPs either. I'm beginning to think that I had it easy at my previous job but maybe that's just because I was used to it.
So here are my problems/questions:
I have two tables with a one to many relationship that I need to retrieve data from, show in a jsp and be able to update eventually.
So here's what I am doing:
a) In a servlet, I use a SQL statement to join the tables and retrieve the results into a Recordset.
b) I created a class with a bunch of String attributes to copy the Recordset data into, one Recordset row per each instance of the bean and then close the Recordset
c) I then add the beans to an ArrayList and save the ArrayList into the session.
d) Then, in the JSP, I retrieve the ArrayList from the session and iterate over each bean instance, printing the data out to the jsp. There are some logic statements to determine when not to print redundant data caused by the one to many join.
e) I have not written the code to update the data yet but was planning on having separate jsps for updating the (one) table and the (many) table.
Would most of you do something similar? Would you use one SQL statement to retrieve all of the data for display and use logic to avoid printing the redundant part of the data? Or would you have used separate SQL queries, one for each table? Would you have saved the results into something other than an instance of a bean class that represents one record in the RecordSet? Would you have had a bean class with attributes other than Strings - like had a collection attribute to hold the results from the "many" table? The way that I am doing everything just seems so cumbersome and difficult compared to using Struts and JDO before.
Your help/opinion will be greatly appreciated!

Would you use one SQL statement to retrieve all of the data for display Yes.
and use logic to avoid printing the redundant part of the dataNo.
I believe in minimising the number of queries. If it is a simple one-many join on a db table, then one query is better than one + n queries.
However I prefer to store the objects in a bean class with attributes other than strings - ie one object, with a collection attribute to hold the related "many" records.
Does the fact you are not using Struts mean that you have to use scriptlet code? (shudder)
Or are you using JSTL, or other custom tags?
How about tools like Ant? Junit testing?
The way that I am doing everything just seems so cumbersome and difficult
compared to using Struts and JDO before.Anything different takes adjusting to. Sounds like you know what you're doing for the most part. I agree, in terms of best practices what you have described so far sounds like a step backwards from what you were previously doing.
However I wouldn't go complaining about it too loudly, too quickly. If you're new on the block theres nothing like making a pain of yourself, and complaining how backwards the work they have done is to put your new workmates' backs up
Look on it as a challenge. Maybe discuss it quietly with a team leader, to see if they understand how much easier/better/less error prone such approaches can be?
Struts, cumbersome as it can be, definitely has the advantage of pushing you to follow good MVC practice.
Good luck,
evnafets

Question about Best Practices - Redwood Landscape/Object Naming Conventions

Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

Hi Paul,
As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
As you have confirmed, you are using OEM and hence you have only one process server.
Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
So in a nutshell, it is highly recommend
Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1).
Hope this answers your queries. Please write if you need some more information / help in this regard.
Best regards,
Vithal

DNS Alias to named instance

Hi, I have been recommended to create DNS aliases for the sql server instances so it be much more flexible for us to later migrated databases from server/instances to other server/instances... I really like this approach, but my SQL server consist of several
named intances, one for every service/application.
Its easy to create a dns alias for a server name, but is it even possible to create DNS aliases for each named instance?
And question two, is it possible to run all named instances on port 1433?
Thanks in advance.

Its easy to create a dns alias for a server name, but is it even possible to create DNS aliases for each named instance?
A DNS entry will resolve the host name to an IP address, but the instance name (or port number) will still need to be specified in client connection strings. This will allow you to move a named instance to a different server without changing client
connection strings as long as you retain the same instance name (or port number if you use a port number instead of instance name).
For example, if you have 2 named instances on SERVERA named INSTANCE1 and INSTANCE2, you could create DNS records INSTANCE1.EXAMPLE.COM and INSTANCE2.EXAMPLE.COM both pointing to SERVERA. The client connection string will still need to specify
the instance name (e.g. INSTANCE1.EXAMPLE.COM\INSTANCE1 and INSTANCE2.EXAMPLE.COM\INSTANCE2). That would allow you to move a named instance to different host transparently with only a DNS change (e.g. move INSTANCE1 to SERVERB and change INSTANCE1.EXAMPLE.COM
to point to SERVERB.
And question two, is it possible to run all named instances on port 1433?
No (assuming the same IP address). Each instance on a host must listen on a different port number. It is ultimately the IP address and port number that uniquely identify an instance.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Can we install a new mssql cluster on the same windows cluster which already containes a mssql cluster with named instance

We have a MSSQL 2008R2 Enterprise edition with a two node active passive fail-over cluster running on 2008R2 windows cluster with out any issues,
Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setup

hi,
>>Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
Yes it is possible .You need to add new drives as cluster aware and install SQL server and put data and log files on thse drives.YOu would need to create named instance of SQL server and need to create different resource group.Both old installation and new
onw would work separately.
>>Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
Good point indeed.You are about to create Multi instance cluster and should plan for scenario where one node is down and other node is handling load for both instances.Memory and CPU should be enough to handle the load.
>>Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setup .
Just for collation if you are installing new instance seems little wierd to me.You can manage collation at column ,database and at server level.
http://technet.microsoft.com/en-us/library/aa174903(v=sql.80).aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Best Practice SQL Alias with Named Instance

Similar Messages

Maybe you are looking for