Hey. I've 2 nodes in this activeactive cluster. Both of them have 20gb memory. Right now, both are configured to use 12gb each. Is that the right way to configure it? I was thinking we'll have IO issues if we ever failed over to a server. I've to migrate to SQL 2005 and needed some help regarding using accounts.
Should I use the same account for the cluster service and the SQL Server/Agent service? If not what are the permissions I've to give to the cluster service account in SQL? I've a cluster with 2 nodes. What permissions should the SQL account be given on the box? Should it be a local admin or when installing, I give it the account and let SQL worry about giving permissions to the box?
OK so I am aware that the SSIS service can be clustered relatively easily but my problem is a bit more complex I believe.
I have an ActiveActiveActive 3 node cluster running Windows 2003 sp1 all running SSIS packages. What I need is a solution to having an instance fail to another node and still be able to run scheduled SSIS packages through the SQL Agent.
The solution that I have come up with is to have a single network share for all three instances of SSIS running locally on the individual nodes. I have removed the ability for SSIS to look in MSDB by altering the config file and reference only the Packages share on the network for accessability. They all share the same config file on the share as well. The share structure looks something like this simplified example.
\server1SSISConfiguration
\server1SSISPackages
\server1SSISPackagesInstance1
\server1SSISPackagesInstance2
\server1SSISPackagesInstance3
Once I change the registry to point to the config file all three instances can access the Instance1, 2 or 3 directories.
This works ok for the jobs, and I can access the stored packages under the file system folder only if I'm remotely connected to that particular physical server hosting the service or on the console. The problem I am having though is when users or I attempt to access the SSIS Engine through SSMS from our locale machines. It seems as though SSMS is having trouble with the passthrough of the directory information. On the share I obviously have permissiosn to access the directory structure (full control to be exact) because I can get to it when I access it from SSMS on the server.
This is the error I get...
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
The storage location for the folder "File System" cannot be accessed. (MsDtsSrvr)
DETAILS:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------ Program Location:
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(INodeInformation source, INavigableItem sourceItem, IFilterProvider filter) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.GetChildren() at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren()
===================================
The storage location for the folder "File System" cannot be accessed. (MsDtsSrvr)
------------------------------ Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.GetDtsServerPackageInfos(String sPackageFolder, String sServerName) at Microsoft.SqlServer.Dts.SmoEnum.PackageEnum.GetData(EnumResult erParent) at Microsoft.SqlServer.Management.Smo.Environment.GetData() at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci) at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
Any work around or suggestion would be appreciated.
Ideally we'd like to configure our SQL cluster w/ the databases on one drive and the logs on another. Is this feasable in a cluster solution.. Will it basically just be 2 drives that are failed over vs. 1?
I have SQL 7 running on an Active/Passive Cluster configuration. My problem is that I can not see any SQL objects listed on perfmon. Can this be because of the Cluster configuration? I trying to run perfmon directly from the main system console.
I know that it is possible with 2 machines with the clasical solution of Machine1: active-passive, Machine2: passive-active, this way if one of the machines goes down the other one will take the job of both instances, but I dont know if this solution is possible in SQL server 2000 with 3 instances at the same time.
I have a 2 node cluster in an active/active configuration. Install is SQL 2005 Enterprise Edition x64, patched to KB934458
If I try and run SQL Server Configuration Manager on node 1 the application does not start and I get the following message: "Connection to target machine could not be made in a timely fashion." This happens for both SQL Server instances (SQL01 and SQL02). I can connect fine on the 2nd node with both instances.
Further to this, if I try and run the Surface Area Configuration tool on node 1 - I can't connect to either SQL Instance (SQL01 and SQL02) If I run the SAC tool on the second node, I can connect to the instance SQL02 that is active on node 2. If I fail that SQL Instance over to node 1, I can no longer connect I think there is clearly something not quite right about node 1.
I have installed SQL Server 2012 on Node1 successfully and trying add node on Node2 and its failing with below message. I attached the screen shot.
Here we are not doing multi-subnet failover clustering. Why we are getting extra and asking for IP and what IP should we enter there?Add Node option should automatically detect the IP we configured on Node1.
[Error Message] To support SQL Server multi-subnet failover clustering, you must select at least one valid IP address for every subnet in the cluster.
[Details] Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicValidationException: To support SQL Server multi-subnet failover clustering, you must select at least one valid IP address for every subnet in the cluster.
I have two MS Windows 2003 Server Ent Ed. SP2 in cluster. They have MS SQL Server 2005 in cluster.
I have created and endpoint and when I try to access I get the attached error in client machine. This problem only occurs in cluster configuration, because the same installation in an SQL (no cluster) works fine.
EventID: 4 Source: Kerberos The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/fra-lille-hel03.ea.holcim.net. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (EA.HOLCIM.NET), and the client realm. Please contact your system administrator.
Hi, We are having SQL SERVER 7.0 on NT cluster.We have a problem registring server with enterprise manager. Actually it was fine for some time. But actually today to install servicepack we unclustered.It went with some errrors. Actualy we tried to recluster the servers .Every thing is fine but intially at the end it said that it can't connect to the virtual server host name.Now every thing seems to be fine but when we try to register the server with EM we can't do it now.But by using IP address we can register the server.We are able to connect by using SQL Query analyzer.Can anyone suggest me any thing.i greatly appreciate your help. regards MM
I have to configure the drives i.e numbers of drives and sizes of each drives for the new server which will replacement for the existing server. Current server has following : Drives Total Size C: 18 GB D :( DATA) 15.8 GB G :( TEMPDB) 750 GB H: (LOG) 64.9 GB I: (DATA) 751 GB J: (BACKUPS) 450 GB
In these i have one database of size (1TB) which doesn't need to there in new server. So what do i recommend for the drives. Thanks for SQL experts in advance
I am trying to install the MS SQL Server 2012 Failover Cluster on Windows Server 2012 . I successfully Installed the Failover cluster instance on my primary node.
But when I am running the installation process on passive node to add node in the failover cluster I am stuck with very unique kind of issue.
I am following the Standard process of Installation and I am getting the same windows for each next process, but after License Agreement window when I get the Cluster Node Configuration window, then in "SQL Server Instance Name" drop down box I am not getting the Name of Instance which is already installed on the primary node. But this Instance complete information is appearing in below given box.
Only issue is Instance name is not appearing in the drop down list, that's why I am not able to select and when I click on next it trough error and do not proceed.
I have a Sql Server cluster set up in an active/active configuration. It is running NT4.0 SP6 and SQL Server 7.0. The problem is that node 2 has failed over to node 1 and whatever I try, I cannot get node 2 to failback. I think I have tried just about everything. Any SQL Cluster gurus out there ? Any help would be very much appreciated. Thanks in Advance
I am having an existing sql 2005 cluster on an active passive cluster. I need to add analysis service to this as a new component. I am having enough space available in the cluster disks. Following are my queries,
1) do i need a new virtual ip and virtual server name for the analysis services ?
2) do i need a seperate cluster resource group for analysis services with an additional disk added ?
I have just finished installing SQL 2005 Ent Edition on Win 2000 Adv Server, SQL2005 SP2, and SP2 Hotfix KB934458. After the installation, I could see and configure all services via SQL Configuration Manager and SQL Server Surface Area Configuration tools. This worked for a couple of days and now both configuration tools no longer detect SQL2005 components. SQL Server Surface Area Configuration issued an error that said "No SQL Server 2005 components were found on specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLAC)". SQL Configuration Manager did not list any installed services. I don��t know what caused this. Anyone has any idea? Please help! Below is the Installation Report which shows installed components.
===================================
The following components are installed on this server
Hi --I was wondering if this is a bug when I add new data in my table SSIS Confiurations and give wizard a new Configuration filter the package configuration wizard can not see the new values --the old values from the previous configuration are still showing---is there any known workaround or forced refresh I can do
thanks in advance Dave
Background:
SQL Package Configurations are most important because they provide the possibility of a central configuration store for your entire enterprise!!!!!!!! and is in my mind the only way to go
USE [ETLConfiguration] GO /****** Object: Table [dbo].[SSIS Configurations] Script Date: 05/23/2006 13:34:35 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[SSIS Configurations]( [ConfigurationFilter] [nvarchar](255) COLLATE Latin1_General_CI_AS NOT NULL, [ConfiguredValue] [nvarchar](255) COLLATE Latin1_General_CI_AS NULL, [PackagePath] [nvarchar](255) COLLATE Latin1_General_CI_AS NOT NULL, [ConfiguredValueType] [nvarchar](20) COLLATE Latin1_General_CI_AS NOT NULL ) ON [PRIMARY]
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).
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.
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 have following script which i am planning to run to drop all non-clustered primary keys on a database and then created as clustered. I am using someone else's script so don't know how to modify this. Some of primary key columns are used in references in other tables.
is there anyway i can drop the existing primary keys and using their original script then create again as clustered including restoring all foreign and reference keys and unique or no unique.
DECLARE @table NVARCHAR(512), @tablename NVARCHAR(512), @sql NVARCHAR(MAX), @sql2 NVARCHAR(MAX), @sql3 NVARCHAR(MAX), @column NVARCHAR(MAX); DECLARE @indexname NVARCHAR(512); SELECT name As 'Table'
We are planning to change all IPs of PRODUCTION Failover Cluster Setup. In my cluster setup ... we have 2 Physical Nodes with windows-2008, Roles are MSDTC and SQL-2008R2.
IP change for:
1. Both Nodes(Physical) 2. MSDTC 3. SQL Server 4. windows Cluster
So Almost... All IPs are going to change.
Im DBA here, I need to take care of SQL cluster and MSDTC. But I haven't performed this activity before.So I'm worrying about Impacts and consequences of this change. steps how should I perform this activity.
It seems to me, that the best way is to have one Environment Varible containing the name of the SQL Server, so that you can look up the configuration in the SSIS Configuration Table when you run the package.
Is this the preferable way of doing it ? I would like to hear some positive/negative comment of why chosing a configuration type instead of another.
It seems to me that putting all of the configuration in the Environment variable is harder work but most secure (server breakdown vs table corruption/database error...)
We have many tables which have cluster index on column with datatype 'Char(200)'. Does anyone have script to change cluster index to noncluster for all user tables which have clustered index on a column with 'char(200)' datatype.
I am trying to upgrade a SQL Server 6.5(Cluster) to SQL Serevr 7.0 (Cluster)..I already have an intsllation of 7.0(On a Cluster),so this means that 6.5 and sql 7 are on seperate cluster's ,if i try to upgrade from 6.5 Cluster to 7.0 Cluster is asks me to uncluster 6.5 and 7.0 is this correct ,assume i cannot break the cluster then what???.. what is the best way i can achieve this functinality.....
This morning I can not connect to our SQL Server 7.0 whatever from client or server. The error message which I list below:
++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++ A connection could not be estabished to server--Timeout expired Please verfy SQL Server is running and check your SQL Server registration properties and try again. ++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++
We use windows NT authentication. We did not do any change on NT. The SQL Server daily schedule job usally stoped at 10:00AM, but today from the Window NT Task Manager, we can see that the SQL Server is still running untill now.
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?
