I have a database that is around 2 to 4 GB.If I were to estimate some numbers like 4x growth oreven 10x, the database size could reach 40GB.The new server will be running SQL Server 2005.I am not sure which configuration option to take.I've gathered some information from different places:Configuration #1:OS - Raid1 2x36GBLogs - Raid1 2x36GBData - Raid 5 4x73GBConfiguration #2:OS - Raid1 2x36GBLogs - Raid5 (not sure how many drives)Data - Raid5 (not sure how many drives)Now if I am using a separate RAID array disksfor the database's transaction log, should I also put theTempDB in this RAID also?Here's the configuration I am thinking of right now.Please give me your comments:OS - Raid1 2x36GBLogs & TempDB - Raid5 3x36GB = 2x36GB usable spaceData - Raid5 3x73GB = 2x73GB usable spaceIf you have other configurations you recommend please letme know.Thank you
am trying to install sql 2005 with cluster option in win 2003 R2 servers and keep getting sql database setup failed error.Summary log show that it failed with error number 67. It doesn't even create a SQLSetup0004_M2MTPONE_SQL.log file. core log shows
Complete: DetectLocalBootstrapAction at: 2006/5/1 18:15:31, returned true Running: LaunchLocalBootstrapAction at: 2006/5/1 18:15:31 Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 67 Aborting queue processing as nested installer has completed Message pump returning: 67
We have two machines in running enterprises version of R2 in a cluster. I tried running the setup from both machines and got the same error.
I am trying to find a solution for more than week but no luck. Any help is appreciated.
thanks - Kailash
Part of Summary log: --------------------------------------------------------------------------------
Machine : M2MTPONE Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_M2MTPONE_BackwardsCompat_1.log --------------------------------------------------------------------------------
Installing SQl2005 into on Win2003 2 node cluster, at the very end of the setup receive a message 'Remote Setup failed'. Referred to some sql logs and found this; Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1603 Aborting queue processing as nested installer has completed Message pump returning: 1603
I've seen some similar errors on the web and suggestions about the Task Scheduler being started on both nodes, but I ensured these were both started before the install. SQL2005 does seem to be ok on the node1 where the install was made, but fails when trying to failover to node 2.
Curious on how this will work.. if i install sql 2005 standard edition on one virtual server.. to a fixed disk (actually 2 fixed disks.. one for C, one for D).. then install another 2005 standard edition on another virtual server.. do i just rerun the setup and suddenly the failover cluster option will NOT be greyed out?
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We  run the below commands but didn’t get any resolution & got the same above error .  1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).Â
2. net stop winmgmtÂ
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).Â
4. net start winmgmt
2<sup>nd</sup>Â Method..
1. Disable and stop the WMI service.
a) Command : - sc config winmgmt start= disabled
b. Command : - Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â net stop winmgmt
Can I build a cluster by adding the cluster service, then the SQL instances, then add the other nodes and their passive SQL instances?I would lean to building the cluster first, the add the SQL instances.
I would like to have some clarification about index-related recommendation from Database Tuning Advisor.
Let me describe the scenario first:
There is a table with clustered index defined on ID column of type INT and there are other columns of varchar/int types as well. Now when I run tuning advisor I get recommendations related to creating statistics as well as non-clustered indexes. When I view the syntax for recommended non-clustered index, sometime it explicitly add ID column as well which already has clustered index defined on it. e.g
CREATE NONCLUSTERED INDEX idx_TableName_IndexName ON dbo.TableName
(
ColName1 ASC,
ColName2 ASC,
ID ASC
)
My understanding is that for each non-clustered index, clustered index is automatically a part of it and that is how non-clustered index retrieve the actual data. I have seen it more often than not in DTA's recommendation to include clustered index column somewhere among columns for indexing for so many of my tables.
I can understand if the recommendation was to INCLUDE clustered-index column.
I would appreciate if someone out there could help me to understand what I am missing here.
We are on SQL Server 2000 A/A cluster and are moving to SQL Server 2005 cluster.
Following are the list of things before proceeding, please let me know if it needs any corrections and add-ons:
(side-by-side) Planning for new installation of SQL Server 2005 ( SQL2005INST1 and SQL2005INST2) on node1 and node2 and restoring the databases on SQL2005INST1 and SQL2005INST2 from respective 2000 instances.
1) SQL2005INST1
SQL Network Name
SQL IP address
2) SQL2005INST2
SQL Network Name
SQL IP address
As 2000 is already existing on the cluster.Want some clarity on following questions.
Can I keep the data files on the same disk as 2000 was using ?
Do I need to have new disk for the Quoram drive?
Under "Virtual Server Configuration" wizard during the setup under "Network to use"--- for "private cluster network" and "public cluster network" do that IP Address and network address and network subnet will be different from what we gave for SQL 2000.
Ok Here is the story with hopefully all the details. I had a single node cluster Itanium server running W2k3 IA 64 Ent. SP2 with 2 x sql2000 ent sp4 and 1 sql2005 sp1 instances installed and a clustered file share. All is well with them. I attempted to add an additional node to my cluster which started out fine but when I tried to run the sql2000 setup to add this node, there are no warning or errors. Its a silent failure. I tried many different scenarios but the results are the same. I evicted the node and then tried to run the setup on the evicted node. The setup ran without error. I tried to run setup on my single node cluster and it fails in the same manner. I read and read and from the sqlstp.log this is what I find. Does anyone have a clue what is wrong? i have check all my permissions but I can't put my finger on what it could be.Help Help.
Does anyone know how to install SQL 2005 integration services on a cluster machine?
I have an a-a cluster machine. Both nodes are using SQL 2005 naming instance. During the SQL installation, I did include integration services option as one of my setup items. The setup process was running fine but I can€™t connect to integration services via MS SQL Server management studio. I see below errors:
€œInvalid server name "TESTServerB123". SSIS service does not support multi-instance, use just server name instead of "server nameinstance".
Looks like I must use default instance for 2005 integration services. I re-ran the setup program and added a default instance on the same cluster node. (On that node I have one default instance and one naming instance). Now I can connect to the default SQL Server but when I click on €œstored packages€?, I don€™t see file system and MSDB. It shows nothing at all. Any idea how to make integration services running on a cluster machine?
I am using SQL 2012 SE with clustering on Windows server 2008 R2. Now I want migrate it to windows server 2012 with minimal down time. So I want to evict the passive node and add a new node with windows server 2012 and install sql server 2012 SE on the new passive node and perform a failover(make the node with 2012 OS as active) and then evict the new passive node and add another node with windows 2012 and then do the same thing?
I tried installing SQL Mail but it didnt work. What happened was, when I was entering the SQLMail profile for an Exchange User name. It took those values. Now when we ran/initialize SQLMail service, the Cluster Services kept rebooting/re-initializing all the services. Therefore, system crash and will not provide any services any longer. We tried resolving it by running the SQL services in node 2 and we got MSSQLServer v6.5 service running but the SQLExecutive service will not start. I tried to reset the permissions on the services and have that SQLExecutive run on the NT Administrator account.
After reading a few technotes from MS and applying them. None seem to have worked so far. Here are some of the technotes: Q195761 Q158585 Q155697 Q155283
(1) How can we fix the SQLExecutive so it will autostart with bringing down the cluster (2) What can we do to successfully run SQL mail on the cluster server with this all the variables in this situation.
I appologize if I am posting this msg twice (newby), but I am getting this error msg in the app log.
MS DTC setup failed to populate the shared cluster registry. The DTC resource will not be able to come online.Error Specifics: d:srv03rtmcomcomplusdtcsharedmtxclumtxcluse tuphelper .cpp:120, CmdLine: "C:WINDOWScluster esrcmon.exe" -e 1208 -m 1212 -p 2132, Pid: 3636
Have anybody seen this msg and any ideas on what to do in this situation? Your timely assistance is much appreciated. Thanks,
We have an existing SQL Server 2012 Enterprise cluster with 2 nodes (active-active) and uses Windows 2008 R2 OS. We are looking for a way to increase HA as well as offload backups to secondary server and it was suggested that AlwayOn could be an option.
The questions I have are:
1) Is it possible to turn on AalwaysOn feature on an existing cluster?
2) If yes to above, does the secondary replica need to exist as a node on the same cluster or can it be on a completely different cluster?
3) If the secondary replica is on the same cluster (i.e. we add a 3rd node to existing 2 node cluster), can that node be provisioned with storage from a completely different SAN? (i.e. Node 1 and Node 2 accesses LUNs on SAN1 and Node 3 accesses LUNs on SAN2).
when i install sql server 2005 in cluster. I have error at Setup process screen --> the selected components are being configured.all the components are failed.I am using domain account with administrator account privilege on both server.OS : windows server 2008 on virtual machine..when i install sql server agent is enable to select during setup..
I saw following point on Technet article about RBS.The local FILESTREAM provider is supported only when it is used on local hard disk drives or an attached Internet Small Computer System Interface (iSCSI) device. You cannot use the local RBS FILESTREAM provider on remote storage devices such as network attached storage (NAS).It looks like that we cannot use FILESTREAM on Failover Cluster because to setup Failover Cluster we need to have NAS. But then the NAS is made available locally for Failover Cluster so FILESTREAM should work right?Found another article which talks about setting up FILESTREAM on Failover Cluster. URL...
I'm trying to do a SQL 2008 cluster installation.I installed one node and now I'm trying to add a failover cluster node.in the "add Node Rules" I get following message:
Rule Check Result...Rule "SQL Server Database Services feature state" failed.The SQL Server Database Services feature failed when it was initially installed. The feature must be removed before the current scenario can proceed.
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
We have successfully been using MSCS with MSSQL7 (SP1) running under NT4 EE (SP6a), installed in an active/active configuration using, two DELL PowerEdge 6350 machines. Recently I installed MSSQL7 (SP2), I followed the instructions that came with SP2, and unclustered the SQL nodes using the Failover Cluster Wizard, and installed SP2, this was uneventful, and appeared to install correctly. Next I tried to recluster the SQL nodes using the Failover Cluster Wizard as directed. This failed with: "Could not run setup on remote machine. SQL Cluster Setup failed." So I began the usual research using the usual resources, and have found articles that discusses this error, and the things to look for when it happens. I have exhausted all suggestions without success. I appear to have everything correctly configured. I have enabled Cluster Logging (level 3), following are the two things I have found that indicate something is wrong:
1. In the SQL Error Log the following gets logged when I run the wizard: "Attempting to initialize Distributed Transaction Coordinator." "Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE"
2. In the Cluster Log I see the following message repeatedly: "[ClRtlCopySecurityDescriptor] MakeSelfRelativeSD failed, 0x00000551"
3. In the sqlclstr.log I see the following, without an indication of which file is missing: "[reghelp.h:235] : 2 (0x2): The system cannot find the file specified." "[clushelp.cpp:166] : 259 (0x103): No more data is available." "[validate.cpp:147] DeleteTestGroup:OpenClusterResource: 5007 (0x138f): The cluster resource could not be found." "~~~ XXX InstallRemote failed"
Does anyone have any ideas about what could be causing this problem? Many thanks in advance.
i setup a 2 node sql cluster but 1433 is not listening. I check sql configuration manager and entered 1433 for all ip addresses restarted services but still not 1433
I ran into problem while trying to install SQL Server 2008 to join to another node in a failover cluster ,you will find here the configuration doc and installation details. URL...
I have been facing following Error in Failover cluster setup as below. I have prepared 2 node and 2 instance sql server failover cluster on top of windows failover.I have deleted MTCBJINS07 in AD and recreated even after, problem is not solved. MTCBJINS07 is my 2nd sql instance sql server network name.
Cluster network name resource 'SQL Network Name (MTCBJINS07)' failed registration of one or more associated DNS name(s) for the following reason:
DNS bad key.Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
I found errors frequently in cluster events at  logs as below
"Cluster network interface 'Node1 - 10.X.XXX.1' for cluster node 'Node1' on network 'Cluster Network 1' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
How to fix this issues? is it missing any patch OS or cluster side?
I have destroyed the cluster in failover cluster manager and then i am trying to remove node from the sql server installation centre.I am facing the cluster node and cluster service verification errors.I am not able to start the cluster service in services as well.
Hi all, I am trying to setup the cluster SQL server, say ServerA and ServerB. While I start the setup in ServerA, it prompts, 'Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.'
But I found that there is no remote logon to both nodes and the service task scheduler is running in both node.
On the other hand, I try to install the SQL via ServerB, it prompts for valid Native client package 'sqlncli.msi' and caused the setup failed finally. However, the Native client was setup successfully as a prerequisite once starting the setup.
I have copied install files to both local and remote locations
I know the response €“ Installshield cannot find the silent response file, but SQL setup creates this on its own. Short of bringing this production system down and re-installing on both nodes ( I did test this on a non-prod box by the way, no issues), I am at a loss
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?