Showing posts with label active. Show all posts
Showing posts with label active. Show all posts

Thursday, March 8, 2012

Check connectivity Sql Server

Hello all, I am hoping this is the correct place for this. I have an application that depends on an active connection to Sql Server Express 2005. I am looking for a way is any to check for the existance ofthe server I defined and wether it is online or not. I know I can just catch the error on connection but it takes a bit and I have customers trying to cancel it before it's finished because they think it's locked up. I would like a quick way to check without trying to create a connection if it's online, then if it is, proceed, if not, let the customer know. I was hoping for something like a database server ping of sorts.

Thank you,

Jim

Still, the best/reliable way to check whether you can reach the server instance is connect to it. If you think the lock up time is too long considering that the server is down, you can adjust the connection timeout to be smaller than on-default value. There is caveat to this approach if your target machine is unreachable in the network, which may cause a single physical operation, tcp connection to take long time to finish.

Another way on top of my head is to check service manager of your targeted machine using console commmand "SC" and check the server status, an example is the following. The

>sc \\servername query mssqlserver

SERVICE_NAME: mssqlserver
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

-HTH

Wednesday, March 7, 2012

Check active SQL server 2000 users/connections

How can I check how many users are connected to my SQL 2000 db. Monitor how
many users are active on the database.
regards
simonOn Jul 4, 1:20 pm, Simon79 <Simo...@.discussions.microsoft.com> wrote:
> How can I check how many users are connected to my SQL 2000 db. Monitor ho
w
> many users are active on the database.
> regards
> simon
To check connected sessions
select * from master..sysprocesses where spid > 50
You can check
select spid, datediff(minute,last_batch ,getdate()) from
master..sysprocesses where spid > 50
for how many minutes the session was idle|||Pls try sp_who2 'active'
HTH,
Paul Ibison|||Hi
sp_who 'active'
"Simon79" <Simon79@.discussions.microsoft.com> wrote in message
news:E3126647-65E7-4CDA-B6C8-D4AC4505E165@.microsoft.com...
> How can I check how many users are connected to my SQL 2000 db. Monitor
> how
> many users are active on the database.
> regards
> simon|||Thanx, all your solutions worked great!

Check active SQL server 2000 users/connections

How can I check how many users are connected to my SQL 2000 db. Monitor how
many users are active on the database.
regards
simon
On Jul 4, 1:20 pm, Simon79 <Simo...@.discussions.microsoft.com> wrote:
> How can I check how many users are connected to my SQL 2000 db. Monitor how
> many users are active on the database.
> regards
> simon
To check connected sessions
select * from master..sysprocesses where spid > 50
You can check
select spid, datediff(minute,last_batch ,getdate()) from
master..sysprocesses where spid > 50
for how many minutes the session was idle
|||Pls try sp_who2 'active'
HTH,
Paul Ibison
|||Hi
sp_who 'active'
"Simon79" <Simon79@.discussions.microsoft.com> wrote in message
news:E3126647-65E7-4CDA-B6C8-D4AC4505E165@.microsoft.com...
> How can I check how many users are connected to my SQL 2000 db. Monitor
> how
> many users are active on the database.
> regards
> simon
|||Thanx, all your solutions worked great!

Check active SQL server 2000 users/connections

How can I check how many users are connected to my SQL 2000 db. Monitor how
many users are active on the database.
regards
simonOn Jul 4, 1:20 pm, Simon79 <Simo...@.discussions.microsoft.com> wrote:
> How can I check how many users are connected to my SQL 2000 db. Monitor how
> many users are active on the database.
> regards
> simon
To check connected sessions
select * from master..sysprocesses where spid > 50
You can check
select spid, datediff(minute,last_batch ,getdate()) from
master..sysprocesses where spid > 50
for how many minutes the session was idle|||Pls try sp_who2 'active'
HTH,
Paul Ibison|||Hi
sp_who 'active'
"Simon79" <Simon79@.discussions.microsoft.com> wrote in message
news:E3126647-65E7-4CDA-B6C8-D4AC4505E165@.microsoft.com...
> How can I check how many users are connected to my SQL 2000 db. Monitor
> how
> many users are active on the database.
> regards
> simon|||Thanx, all your solutions worked great!

Sunday, February 12, 2012

Char to Base64 conversion

Hello. Anyone know a way to convert a char string into
BASE64? I'm loading some data to Active Directory from
SQL Server using an LDIF script and since there are
carriage returns imbedded, I BELEIVE the only way to do
this is BASE64 encoding. We wrote a function that loops
thru every character and converts it, but when doing a
large select, that encoding function takes too long for
each row.
INPUT CHAR STRING = "Hello World"
OUTPUT BASE64 STRING = "SGVsbG8gV29ybGQ="
Any ideas or hidden functions that do this conversion in
SQL Server? THanks, BruceCheckout the "FOR XML, BINARY BASE64" of the Select statement and see if it
helps you!
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:427201c49029$2a59bec0$a301280a@.phx.gbl...
> Hello. Anyone know a way to convert a char string into
> BASE64? I'm loading some data to Active Directory from
> SQL Server using an LDIF script and since there are
> carriage returns imbedded, I BELEIVE the only way to do
> this is BASE64 encoding. We wrote a function that loops
> thru every character and converts it, but when doing a
> large select, that encoding function takes too long for
> each row.
> INPUT CHAR STRING = "Hello World"
> OUTPUT BASE64 STRING = "SGVsbG8gV29ybGQ="
> Any ideas or hidden functions that do this conversion in
> SQL Server? THanks, Bruce|||wow, NICE!!! I've been doing some reading on that, and it
doesn't appear that it will convert a CHAR type field into
BINARY BASE64 but if you do the convert something like
this below, then you get it back as BASE64, very cool!
BUT, I'd like to strip the XML tags off, probably a
command to get it with just the straight BASE64 code?
Thanks a LOT, that was a great help!!
select top 1 convert(varbinary(8000),name) as 'name_binary'
from sysobjects
for XML RAW, BINARY BASE64
Thanks, Bruce
>--Original Message--
>Checkout the "FOR XML, BINARY BASE64" of the Select
statement and see if it
>helps you!
>
>"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
>news:427201c49029$2a59bec0$a301280a@.phx.gbl...
>> Hello. Anyone know a way to convert a char string into
>> BASE64? I'm loading some data to Active Directory from
>> SQL Server using an LDIF script and since there are
>> carriage returns imbedded, I BELEIVE the only way to do
>> this is BASE64 encoding. We wrote a function that loops
>> thru every character and converts it, but when doing a
>> large select, that encoding function takes too long for
>> each row.
>> INPUT CHAR STRING = "Hello World"
>> OUTPUT BASE64 STRING = "SGVsbG8gV29ybGQ="
>> Any ideas or hidden functions that do this conversion in
>> SQL Server? THanks, Bruce
>
>.
>|||Hi Harman, Hi Bruce,
I am currently running into the same problem. I can convert it using the
technique you already mentione, but I can not put it into a variable to
strip off the XML-tags.
Do you have an idea how this could be done?
I tried to select it into a variable (not allowed) and tried to get it tino
a temp-table without success.
Maybe you could be so kind and give me a hint on that ;)
Thanks a lot in advance,
Andreas Bretl
andreas.bretl@.brainlab.com|||Andy, yes, the XML method was sooooooooo close... but no
cigar for the SAME reasons you mentioned! Amazing those
points you found that we did (and a zillion other did
also!). Maybe MS will fix that in the next release...
ANYWAY....... We ended up writing a SQL function, that
went thru the not-so-easy task of converting every
character to BASE64. There may be a better way with the
XML option, but we were ok with the function method for
our purposes. It's also pretty amazing that we have to
jump thru these hoops to stick a carriage return inside
an address block of lines, to send to AD, via an LDIF
script. BASE64 doesn't make for readable code at all,
strange that was needed, but it's working fine after we
figured out all the klooge... Bruce
>--Original Message--
>Hi Harman, Hi Bruce,
>I am currently running into the same problem. I can
convert it using the
>technique you already mentione, but I can not put it
into a variable to
>strip off the XML-tags.
>Do you have an idea how this could be done?
>I tried to select it into a variable (not allowed) and
tried to get it tino
>a temp-table without success.
>Maybe you could be so kind and give me a hint on that ;)
>Thanks a lot in advance,
>Andreas Bretl
>andreas.bretl@.brainlab.com
>
>.
>|||Hi Bruce,
I totally agree, that one was really close at all ;)
I ended up in a COM-DLL I installed on the server where I implemented the
Base64 algo. called via sp_OAMethod.
It works fine but it is strange that such a "simple" thing causes so much
workaround.
Do you think there is a chance to see how you handled it with the SQL
function?
I totally understand if you have to keep it "secret" but I just thought
asking could't harm anybody ;)
Seize the Day
Andy
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:114301c4a5c0$23054bb0$a601280a@.phx.gbl...
> Andy, yes, the XML method was sooooooooo close... but no
> cigar for the SAME reasons you mentioned! Amazing those
> points you found that we did (and a zillion other did
> also!). Maybe MS will fix that in the next release...
> ANYWAY....... We ended up writing a SQL function, that
> went thru the not-so-easy task of converting every
> character to BASE64. There may be a better way with the
> XML option, but we were ok with the function method for
> our purposes. It's also pretty amazing that we have to
> jump thru these hoops to stick a carriage return inside
> an address block of lines, to send to AD, via an LDIF
> script. BASE64 doesn't make for readable code at all,
> strange that was needed, but it's working fine after we
> figured out all the klooge... Bruce
> > >

Char to Base64 conversion

Hello. Anyone know a way to convert a char string into
BASE64? I'm loading some data to Active Directory from
SQL Server using an LDIF script and since there are
carriage returns imbedded, I BELEIVE the only way to do
this is BASE64 encoding. We wrote a function that loops
thru every character and converts it, but when doing a
large select, that encoding function takes too long for
each row.
INPUT CHAR STRING = "Hello World"
OUTPUT BASE64 STRING = "SGVsbG8gV29ybGQ="
Any ideas or hidden functions that do this conversion in
SQL Server? THanks, BruceCheckout the "FOR XML, BINARY BASE64" of the Select statement and see if it
helps you!
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:427201c49029$2a59bec0$a301280a@.phx.gbl...
> Hello. Anyone know a way to convert a char string into
> BASE64? I'm loading some data to Active Directory from
> SQL Server using an LDIF script and since there are
> carriage returns imbedded, I BELEIVE the only way to do
> this is BASE64 encoding. We wrote a function that loops
> thru every character and converts it, but when doing a
> large select, that encoding function takes too long for
> each row.
> INPUT CHAR STRING = "Hello World"
> OUTPUT BASE64 STRING = "SGVsbG8gV29ybGQ="
> Any ideas or hidden functions that do this conversion in
> SQL Server? THanks, Bruce|||wow, NICE!!! I've been doing some reading on that, and it
doesn't appear that it will convert a CHAR type field into
BINARY BASE64 but if you do the convert something like
this below, then you get it back as BASE64, very cool!
BUT, I'd like to strip the XML tags off, probably a
command to get it with just the straight BASE64 code?
Thanks a LOT, that was a great help!!
select top 1 convert(varbinary(8000),name) as 'name_binary'
from sysobjects
for XML RAW, BINARY BASE64
Thanks, Bruce

>--Original Message--
>Checkout the "FOR XML, BINARY BASE64" of the Select
statement and see if it
>helps you!
>
>"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
>news:427201c49029$2a59bec0$a301280a@.phx.gbl...
>
>.
>|||Hi Harman, Hi Bruce,
I am currently running into the same problem. I can convert it using the
technique you already mentione, but I can not put it into a variable to
strip off the XML-tags.
Do you have an idea how this could be done?
I tried to select it into a variable (not allowed) and tried to get it tino
a temp-table without success.
Maybe you could be so kind and give me a hint on that ;)
Thanks a lot in advance,
Andreas Bretl
andreas.bretl@.brainlab.com|||Andy, yes, the XML method was sooooooooo close... but no
cigar for the SAME reasons you mentioned! Amazing those
points you found that we did (and a zillion other did
also!). Maybe MS will fix that in the next release...
ANYWAY....... We ended up writing a SQL function, that
went thru the not-so-easy task of converting every
character to BASE64. There may be a better way with the
XML option, but we were ok with the function method for
our purposes. It's also pretty amazing that we have to
jump thru these hoops to stick a carriage return inside
an address block of lines, to send to AD, via an LDIF
script. BASE64 doesn't make for readable code at all,
strange that was needed, but it's working fine after we
figured out all the klooge... Bruce

>--Original Message--
>Hi Harman, Hi Bruce,
>I am currently running into the same problem. I can
convert it using the
>technique you already mentione, but I can not put it
into a variable to
>strip off the XML-tags.
>Do you have an idea how this could be done?
>I tried to select it into a variable (not allowed) and
tried to get it tino
>a temp-table without success.
>Maybe you could be so kind and give me a hint on that ;)
>Thanks a lot in advance,
>Andreas Bretl
>andreas.bretl@.brainlab.com
>
>.
>|||Hi Bruce,
I totally agree, that one was really close at all ;)
I ended up in a COM-DLL I installed on the server where I implemented the
Base64 algo. called via sp_OAMethod.
It works fine but it is strange that such a "simple" thing causes so much
workaround.
Do you think there is a chance to see how you handled it with the SQL
function?
I totally understand if you have to keep it "secret" but I just thought
asking could't harm anybody ;)
Seize the Day
Andy
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:114301c4a5c0$23054bb0$a601280a@.phx.gbl...[vbcol=seagreen]
> Andy, yes, the XML method was sooooooooo close... but no
> cigar for the SAME reasons you mentioned! Amazing those
> points you found that we did (and a zillion other did
> also!). Maybe MS will fix that in the next release...
> ANYWAY....... We ended up writing a SQL function, that
> went thru the not-so-easy task of converting every
> character to BASE64. There may be a better way with the
> XML option, but we were ok with the function method for
> our purposes. It's also pretty amazing that we have to
> jump thru these hoops to stick a carriage return inside
> an address block of lines, to send to AD, via an LDIF
> script. BASE64 doesn't make for readable code at all,
> strange that was needed, but it's working fine after we
> figured out all the klooge... Bruce

Char to Base64 conversion

Hello. Anyone know a way to convert a char string into
BASE64? I'm loading some data to Active Directory from
SQL Server using an LDIF script and since there are
carriage returns imbedded, I BELEIVE the only way to do
this is BASE64 encoding. We wrote a function that loops
thru every character and converts it, but when doing a
large select, that encoding function takes too long for
each row.
INPUT CHAR STRING = "Hello World"
OUTPUT BASE64 STRING = "SGVsbG8gV29ybGQ="
Any ideas or hidden functions that do this conversion in
SQL Server? THanks, Bruce
Checkout the "FOR XML, BINARY BASE64" of the Select statement and see if it
helps you!
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:427201c49029$2a59bec0$a301280a@.phx.gbl...
> Hello. Anyone know a way to convert a char string into
> BASE64? I'm loading some data to Active Directory from
> SQL Server using an LDIF script and since there are
> carriage returns imbedded, I BELEIVE the only way to do
> this is BASE64 encoding. We wrote a function that loops
> thru every character and converts it, but when doing a
> large select, that encoding function takes too long for
> each row.
> INPUT CHAR STRING = "Hello World"
> OUTPUT BASE64 STRING = "SGVsbG8gV29ybGQ="
> Any ideas or hidden functions that do this conversion in
> SQL Server? THanks, Bruce
|||wow, NICE!!! I've been doing some reading on that, and it
doesn't appear that it will convert a CHAR type field into
BINARY BASE64 but if you do the convert something like
this below, then you get it back as BASE64, very cool!
BUT, I'd like to strip the XML tags off, probably a
command to get it with just the straight BASE64 code?
Thanks a LOT, that was a great help!!
select top 1 convert(varbinary(8000),name) as 'name_binary'
from sysobjects
for XML RAW, BINARY BASE64
Thanks, Bruce

>--Original Message--
>Checkout the "FOR XML, BINARY BASE64" of the Select
statement and see if it
>helps you!
>
>"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
>news:427201c49029$2a59bec0$a301280a@.phx.gbl...
>
>.
>
|||Hi Harman, Hi Bruce,
I am currently running into the same problem. I can convert it using the
technique you already mentione, but I can not put it into a variable to
strip off the XML-tags.
Do you have an idea how this could be done?
I tried to select it into a variable (not allowed) and tried to get it tino
a temp-table without success.
Maybe you could be so kind and give me a hint on that ;)
Thanks a lot in advance,
Andreas Bretl
andreas.bretl@.brainlab.com
|||Andy, yes, the XML method was sooooooooo close... but no
cigar for the SAME reasons you mentioned! Amazing those
points you found that we did (and a zillion other did
also!). Maybe MS will fix that in the next release...
ANYWAY....... We ended up writing a SQL function, that
went thru the not-so-easy task of converting every
character to BASE64. There may be a better way with the
XML option, but we were ok with the function method for
our purposes. It's also pretty amazing that we have to
jump thru these hoops to stick a carriage return inside
an address block of lines, to send to AD, via an LDIF
script. BASE64 doesn't make for readable code at all,
strange that was needed, but it's working fine after we
figured out all the klooge... Bruce

>--Original Message--
>Hi Harman, Hi Bruce,
>I am currently running into the same problem. I can
convert it using the
>technique you already mentione, but I can not put it
into a variable to
>strip off the XML-tags.
>Do you have an idea how this could be done?
>I tried to select it into a variable (not allowed) and
tried to get it tino
>a temp-table without success.
>Maybe you could be so kind and give me a hint on that ;)
>Thanks a lot in advance,
>Andreas Bretl
>andreas.bretl@.brainlab.com
>
>.
>
|||Hi Bruce,
I totally agree, that one was really close at all ;)
I ended up in a COM-DLL I installed on the server where I implemented the
Base64 algo. called via sp_OAMethod.
It works fine but it is strange that such a "simple" thing causes so much
workaround.
Do you think there is a chance to see how you handled it with the SQL
function?
I totally understand if you have to keep it "secret" but I just thought
asking could't harm anybody ;)
Seize the Day
Andy
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:114301c4a5c0$23054bb0$a601280a@.phx.gbl...[vbcol=seagreen]
> Andy, yes, the XML method was sooooooooo close... but no
> cigar for the SAME reasons you mentioned! Amazing those
> points you found that we did (and a zillion other did
> also!). Maybe MS will fix that in the next release...
> ANYWAY....... We ended up writing a SQL function, that
> went thru the not-so-easy task of converting every
> character to BASE64. There may be a better way with the
> XML option, but we were ok with the function method for
> our purposes. It's also pretty amazing that we have to
> jump thru these hoops to stick a carriage return inside
> an address block of lines, to send to AD, via an LDIF
> script. BASE64 doesn't make for readable code at all,
> strange that was needed, but it's working fine after we
> figured out all the klooge... Bruce

Friday, February 10, 2012

Chaning login name

There have been some major changes here at work, and in order to keep up we
need to change some of the Group names in Active directory. Will the
changes that are made in Active Directory cascade down into SQL Server?
What is the protocol for this type of change?
Thanks,
DrewNo. On 2005, you can rename a login (to reflect the name change) using ALTER LOGIN.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Drew" <drew.laing@.swvtc.dmhmrsas.virginia.gov> wrote in message
news:OQx$0ftqIHA.5096@.TK2MSFTNGP02.phx.gbl...
> There have been some major changes here at work, and in order to keep up we need to change some of
> the Group names in Active directory. Will the changes that are made in Active Directory cascade
> down into SQL Server? What is the protocol for this type of change?
> Thanks,
> Drew
>|||What is the protocol for SQL Server 2000?
Thanks,
Drew
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C42BDB9F-51A2-424C-8C25-58B905FB94E4@.microsoft.com...
> No. On 2005, you can rename a login (to reflect the name change) using
> ALTER LOGIN.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Drew" <drew.laing@.swvtc.dmhmrsas.virginia.gov> wrote in message
> news:OQx$0ftqIHA.5096@.TK2MSFTNGP02.phx.gbl...
>> There have been some major changes here at work, and in order to keep up
>> we need to change some of the Group names in Active directory. Will the
>> changes that are made in Active Directory cascade down into SQL Server?
>> What is the protocol for this type of change?
>> Thanks,
>> Drew
>|||You can't change the name for a login in 2000. You'd have to delete and re-create the login...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Drew" <drew.laing@.swvtc.dmhmrsas.virginia.gov> wrote in message
news:%234%233Q7tqIHA.2292@.TK2MSFTNGP03.phx.gbl...
> What is the protocol for SQL Server 2000?
> Thanks,
> Drew
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:C42BDB9F-51A2-424C-8C25-58B905FB94E4@.microsoft.com...
>> No. On 2005, you can rename a login (to reflect the name change) using ALTER LOGIN.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Drew" <drew.laing@.swvtc.dmhmrsas.virginia.gov> wrote in message
>> news:OQx$0ftqIHA.5096@.TK2MSFTNGP02.phx.gbl...
>> There have been some major changes here at work, and in order to keep up we need to change some
>> of the Group names in Active directory. Will the changes that are made in Active Directory
>> cascade down into SQL Server? What is the protocol for this type of change?
>> Thanks,
>> Drew
>>
>

Changing Windows Domain

I have a 2 node Windows 2000 Active/Passive Cluster running SQL Server 2000
Enterprise Edition. The cluster supports a 24x365, mission critical
application.
The nodes are currently members of a Windows NT4 domain which trusts a
Windows 2003 Active Directory Domain. All user and service accounts
(including SQLServer and SQLServer Agent accounts) are "ADDomain" accounts.
I am planning on using the procedure described in KBs 269196 and 319016 to
move the cluster from "NT4Domain" to the trusted "ADDomain". The TCP/IP
names and addresses will not change, and to reiterate, the user and service
accounts are already logging into the trusted domain "ADDomain", not
"NT4Domain".
When I look at 319016, however, I get the impression that that KB was
written more to address a changed TCP/IP domain as opposed to a changed
Windows domain. My questions are:
1) Does 319016 even apply in this situation?
For example, step 1 of 319016 calls for a rerun of SQLServer setup. Since
1) the TCP/IP address is not changing and 2) the SQL service account is not
changing, do I need to perform step 1? I'm not sure what all setup might be
doing there.
Also, step 2 of 319016 calls for the new TCP/IP address to be entered for
each instance. Again, the IP address is not changing. As info, there is
only the default instance.
2) I think that I need to move both nodes into the new domain and restart
the cluster service on both (with SQLServer resources kept offline) before
any SQL changes. Is that correct?
3) Assuming there are no GP changes, are there other concerns I'm
overlooking? I saw a similar question in which the admin was leaning toward
rebuilding from scratch instead of moving the cluster. That seems like a lot
more work (rebuilding systems, cluster resources, and
reinstalling/configuring applications) than moving as described above.
Thanks for any feedback
There are two major considerations involved in changing domains. First is
the security issue. The SQL Setup program rewrites the account login
information on each node. If that is not changing, you should be OK without
having to go through setup. Worst case, you can manually change the service
account information on each node. DO NOT attempt to start the service
manually on any particular node. Make sure the service accounts have the
same permissions on the host nodes after changing domains. Be aware that
the machines will now be subject to Group Policies which may change things
in unexpected ways.
The second is changing the FQDN of the system. If the IP domain is
different after the change, you may run into problems with client
connections. A DNS alias record can fix this faster than any other method.
If the actual host names change, then a cluster rebuild may actually be
faster. The other way to handle node renaming is to kick out each node one
at a time, change the host name, add it back to the cluster, reinstall SQL,
reapply hotfixes.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"CarolinaKB" <CarolinaKB@.discussions.microsoft.com> wrote in message
news:CB00A57B-A0E5-450D-9C83-9818B7883595@.microsoft.com...
>I have a 2 node Windows 2000 Active/Passive Cluster running SQL Server 2000
> Enterprise Edition. The cluster supports a 24x365, mission critical
> application.
> The nodes are currently members of a Windows NT4 domain which trusts a
> Windows 2003 Active Directory Domain. All user and service accounts
> (including SQLServer and SQLServer Agent accounts) are "ADDomain"
> accounts.
> I am planning on using the procedure described in KBs 269196 and 319016 to
> move the cluster from "NT4Domain" to the trusted "ADDomain". The TCP/IP
> names and addresses will not change, and to reiterate, the user and
> service
> accounts are already logging into the trusted domain "ADDomain", not
> "NT4Domain".
> When I look at 319016, however, I get the impression that that KB was
> written more to address a changed TCP/IP domain as opposed to a changed
> Windows domain. My questions are:
> 1) Does 319016 even apply in this situation?
> For example, step 1 of 319016 calls for a rerun of SQLServer setup. Since
> 1) the TCP/IP address is not changing and 2) the SQL service account is
> not
> changing, do I need to perform step 1? I'm not sure what all setup might
> be
> doing there.
> Also, step 2 of 319016 calls for the new TCP/IP address to be entered for
> each instance. Again, the IP address is not changing. As info, there is
> only the default instance.
>

> 2) I think that I need to move both nodes into the new domain and restart
> the cluster service on both (with SQLServer resources kept offline) before
> any SQL changes. Is that correct?
> 3) Assuming there are no GP changes, are there other concerns I'm
> overlooking? I saw a similar question in which the admin was leaning
> toward
> rebuilding from scratch instead of moving the cluster. That seems like a
> lot
> more work (rebuilding systems, cluster resources, and
> reinstalling/configuring applications) than moving as described above.
> Thanks for any feedback
>
|||I just did this last night for a customer. If you are already using the new
domain's service account, it's pretty easy. I take it your cluster & SQL
service accounts are already in the local administrators group on each node.
Take all cluster groups offline. Join one node at a time to the new domain,
reboot, when both are back up in and in the new domain start the groups.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
http://msmvps.com/clustering/archive.../20/58233.aspx NYC Clustering
class
"CarolinaKB" <CarolinaKB@.discussions.microsoft.com> wrote in message
news:CB00A57B-A0E5-450D-9C83-9818B7883595@.microsoft.com...
>I have a 2 node Windows 2000 Active/Passive Cluster running SQL Server 2000
> Enterprise Edition. The cluster supports a 24x365, mission critical
> application.
> The nodes are currently members of a Windows NT4 domain which trusts a
> Windows 2003 Active Directory Domain. All user and service accounts
> (including SQLServer and SQLServer Agent accounts) are "ADDomain"
> accounts.
> I am planning on using the procedure described in KBs 269196 and 319016 to
> move the cluster from "NT4Domain" to the trusted "ADDomain". The TCP/IP
> names and addresses will not change, and to reiterate, the user and
> service
> accounts are already logging into the trusted domain "ADDomain", not
> "NT4Domain".
> When I look at 319016, however, I get the impression that that KB was
> written more to address a changed TCP/IP domain as opposed to a changed
> Windows domain. My questions are:
> 1) Does 319016 even apply in this situation?
> For example, step 1 of 319016 calls for a rerun of SQLServer setup. Since
> 1) the TCP/IP address is not changing and 2) the SQL service account is
> not
> changing, do I need to perform step 1? I'm not sure what all setup might
> be
> doing there.
> Also, step 2 of 319016 calls for the new TCP/IP address to be entered for
> each instance. Again, the IP address is not changing. As info, there is
> only the default instance.
> 2) I think that I need to move both nodes into the new domain and restart
> the cluster service on both (with SQLServer resources kept offline) before
> any SQL changes. Is that correct?
> 3) Assuming there are no GP changes, are there other concerns I'm
> overlooking? I saw a similar question in which the admin was leaning
> toward
> rebuilding from scratch instead of moving the cluster. That seems like a
> lot
> more work (rebuilding systems, cluster resources, and
> reinstalling/configuring applications) than moving as described above.
> Thanks for any feedback
>
|||I think we should be okay. The IP address will not change (domains, subnets
all remain exactly the same), I'M TOLD that there are no GP changes, and the
same service account is already being used.
Also, you wrote,
> DO NOT attempt to start the service manually on any particular node.
By this, are you saying to not start SQL through the Services applet as
opposed to starting it through Cluster Administrator after completing the
migration? Just looking for clarification of the above statement.
"Geoff N. Hiten" wrote:

> There are two major considerations involved in changing domains. First is
> the security issue. The SQL Setup program rewrites the account login
> information on each node. If that is not changing, you should be OK without
> having to go through setup. Worst case, you can manually change the service
> account information on each node. DO NOT attempt to start the service
> manually on any particular node. Make sure the service accounts have the
> same permissions on the host nodes after changing domains. Be aware that
> the machines will now be subject to Group Policies which may change things
> in unexpected ways.
> The second is changing the FQDN of the system. If the IP domain is
> different after the change, you may run into problems with client
> connections. A DNS alias record can fix this faster than any other method.
> If the actual host names change, then a cluster rebuild may actually be
> faster. The other way to handle node renaming is to kick out each node one
> at a time, change the host name, add it back to the cluster, reinstall SQL,
> reapply hotfixes.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "CarolinaKB" <CarolinaKB@.discussions.microsoft.com> wrote in message
> news:CB00A57B-A0E5-450D-9C83-9818B7883595@.microsoft.com...
>
>
>
|||Great news; thanks. Like you said, the account is already in Administrators
so that's already done.
"Rodney R. Fournier [MVP]" wrote:

> I just did this last night for a customer. If you are already using the new
> domain's service account, it's pretty easy. I take it your cluster & SQL
> service accounts are already in the local administrators group on each node.
> Take all cluster groups offline. Join one node at a time to the new domain,
> reboot, when both are back up in and in the new domain start the groups.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> http://msmvps.com/clustering/archive.../20/58233.aspx NYC Clustering
> class
> "CarolinaKB" <CarolinaKB@.discussions.microsoft.com> wrote in message
> news:CB00A57B-A0E5-450D-9C83-9818B7883595@.microsoft.com...
>
>
|||Piece of cake then! Good Luck!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
http://msmvps.com/clustering/archive.../20/58233.aspx NYC Clustering
class
"CarolinaKB" <CarolinaKB@.discussions.microsoft.com> wrote in message
news:769D2D4F-D9D4-4209-8E88-356FDD592842@.microsoft.com...[vbcol=seagreen]
> Great news; thanks. Like you said, the account is already in
> Administrators
> so that's already done.
> "Rodney R. Fournier [MVP]" wrote:
|||Do not start SQL through the Services applet. Let the Cluster service
manage the SQL service startup. You can use Enterprise Mangler or the SQL
Server Service Manager tool to stop/start SQL clustered instances but I
prefer to use the Cluster admin tool.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"CarolinaKB" <CarolinaKB@.discussions.microsoft.com> wrote in message
news:7E8687AC-02C3-467E-8226-846B657BBCDD@.microsoft.com...[vbcol=seagreen]
>I think we should be okay. The IP address will not change (domains,
>subnets
> all remain exactly the same), I'M TOLD that there are no GP changes, and
> the
> same service account is already being used.
> Also, you wrote,
> By this, are you saying to not start SQL through the Services applet as
> opposed to starting it through Cluster Administrator after completing the
> migration? Just looking for clarification of the above statement.
> "Geoff N. Hiten" wrote: