For a SQL client, there is no such thing as 'logged into teh cluster'. You
connect to a SQL instance that may be running on any of the configured nodes.
Any change you make within a database is independent of which node the
instance may be running since the change is stored inside a database, and
thus in a database file(s). Note that there is only one set of the database
files per instance regardless which node may be accessing them. Even if you
make a change that is stored in a SQL Server registry key/value, there
shouldn't be any difference between the nodes either because the cluster
service should replicate the registry changes among all the participating
nodes.
[quoted text, click to view] >I have found some differences between the settings
> when I failover between both SQL servers.
What are these differences?
Linchi
[quoted text, click to view] "DC" wrote:
> I currently have active/passive SQL 2005 STD SP2 servers. I have found some
> differences between the settings when I failover between both SQL servers. I
> think that one of the DBA's made setting changes as well as created
> maintenance plans while logged into the specific server (SQL1) instead of the
> cluster. Would that cause differences between having SQL1 as the active node
> vs. SQL2 active? If you make changes while logging into the specific SQL
> server instead of the cluster make it available only to that server when it
Thanks for your response. Do you know of any reason what could cause
differences when the active server is SQL1 vs. SQL2. For example, the
following was setup when SQL1 was the active node and was different when SQL2
was active:
1. Linked servers SQL2
2. Maintenance Plan did not work on SQL2
3. SQL1 (when active) shows mixed authentication while SQL2 (while active)
was set for Windows authentication.
Everything else was not an issue regardless of the active server.
Thanks for your help.
[quoted text, click to view] "Linchi Shea" wrote:
> For a SQL client, there is no such thing as 'logged into teh cluster'. You
> connect to a SQL instance that may be running on any of the configured nodes.
> Any change you make within a database is independent of which node the
> instance may be running since the change is stored inside a database, and
> thus in a database file(s). Note that there is only one set of the database
> files per instance regardless which node may be accessing them. Even if you
> make a change that is stored in a SQL Server registry key/value, there
> shouldn't be any difference between the nodes either because the cluster
> service should replicate the registry changes among all the participating
> nodes.
>
> >I have found some differences between the settings
> > when I failover between both SQL servers.
>
> What are these differences?
>
> Linchi
>
> "DC" wrote:
>
> > I currently have active/passive SQL 2005 STD SP2 servers. I have found some
> > differences between the settings when I failover between both SQL servers. I
> > think that one of the DBA's made setting changes as well as created
> > maintenance plans while logged into the specific server (SQL1) instead of the
> > cluster. Would that cause differences between having SQL1 as the active node
> > vs. SQL2 active? If you make changes while logging into the specific SQL
> > server instead of the cluster make it available only to that server when it
Linked servers may depend on aliases which are local to each noded.
Maintenance plans used to require SSIS prior to SP2. SSIS installer is not
cluster-aware. Check and see if Integration Services is installed on Node 2
Authentication mode should not change.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
[quoted text, click to view] "DC" <DC@discussions.microsoft.com> wrote in message
news:DBB190E2-7B76-43DB-AA37-7C662FF7E6A8@microsoft.com...
> Thanks for your response. Do you know of any reason what could cause
> differences when the active server is SQL1 vs. SQL2. For example, the
> following was setup when SQL1 was the active node and was different when
> SQL2
> was active:
> 1. Linked servers SQL2
> 2. Maintenance Plan did not work on SQL2
> 3. SQL1 (when active) shows mixed authentication while SQL2 (while active)
> was set for Windows authentication.
>
> Everything else was not an issue regardless of the active server.
>
> Thanks for your help.
>
>
> "Linchi Shea" wrote:
>
>> For a SQL client, there is no such thing as 'logged into teh cluster'.
>> You
>> connect to a SQL instance that may be running on any of the configured
>> nodes.
>> Any change you make within a database is independent of which node the
>> instance may be running since the change is stored inside a database, and
>> thus in a database file(s). Note that there is only one set of the
>> database
>> files per instance regardless which node may be accessing them. Even if
>> you
>> make a change that is stored in a SQL Server registry key/value, there
>> shouldn't be any difference between the nodes either because the cluster
>> service should replicate the registry changes among all the participating
>> nodes.
>>
>> >I have found some differences between the settings
>> > when I failover between both SQL servers.
>>
>> What are these differences?
>>
>> Linchi
>>
>> "DC" wrote:
>>
>> > I currently have active/passive SQL 2005 STD SP2 servers. I have found
>> > some
>> > differences between the settings when I failover between both SQL
>> > servers. I
>> > think that one of the DBA's made setting changes as well as created
>> > maintenance plans while logged into the specific server (SQL1) instead
>> > of the
>> > cluster. Would that cause differences between having SQL1 as the
>> > active node
>> > vs. SQL2 active? If you make changes while logging into the specific
>> > SQL
>> > server instead of the cluster make it available only to that server
>> > when it
>> > is active?
Don't see what you're looking for? Try a search.
