We currently have a (2) node active/active cluster with each node ideally
hosting (2) virtual servers and their instances. We want to split the
cluster into (2) active/passive clusters and move what normally resides on a
given node to it's own cluster. Here is the catch. We have cross
server/instances queries/procedures and Access database/queries with the
Virtual Server and instance name hard coded, and creating new names isn't
really an viable option.
Here is the current setup:
Current Cluster:
NODE01
VSQL1\sqlsrv01
VSQL1\sqlsrv02
NODE02
VSQL1\sqlsrv03
VSQL1\sqlsrv04
And here is the proposed setup::
New Cluster 1:
NODE01 - active
VSQL1\sqlsrv01
VSQL1\sqlsrv02
NODE02 - inactive
New Cluster 2:
NODE01 - active
VSQL1\sqlsrv03
VSQL1\sqlsrv04
NODE02 - inactive
Can we create the servers in a different domain, moving them to our
production domain when testing has been completed? And if so, how do we
handle the fact that the VSQLx and named instances already exists in Active
Directory? Can the old server just be turned off, the new one brought up and
added to the domain by resetting the current domain accounts and re-joining?
Of course. Does anyone have a good solution, I'm all ears. Thanks
> Here is the current setup:
> Current Cluster:
> NODE01
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
That can't be your current setup. Your current setup is probably more like:
NODE01
VSQL01\sqlsrv01
VSQL02\sqlsrv02
NODE02
VSQL03\sqlsrv03
VSQL04\sqlsrv04
I'd probably just do a switchover with the current cluster. First, get the
necessary database files to a staging server. Then, remove the cluster from
the network. But keep it as your rollback plan. Create two new clusters and
install SQL instances as follows:
New Cluster 1:
NODE01 - active
VSQL01\sqlsrv01
VSQL02\sqlsrv02
NODE02 - inactive
New Cluster 2:
NODE01 - active
VSQL03\sqlsrv03
VSQL04\sqlsrv04
And finally get the database files from the staging server to their
respective new servers.
Linchi
"randall_dh" wrote:
> We currently have a (2) node active/active cluster with each node ideally
> hosting (2) virtual servers and their instances. We want to split the
> cluster into (2) active/passive clusters and move what normally resides on a
> given node to it's own cluster. Here is the catch. We have cross
> server/instances queries/procedures and Access database/queries with the
> Virtual Server and instance name hard coded, and creating new names isn't
> really an viable option.
> Here is the current setup:
> Current Cluster:
> NODE01
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
>
> And here is the proposed setup::
> New Cluster 1:
> NODE01 - active
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02 - inactive
> New Cluster 2:
> NODE01 - active
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
> NODE02 - inactive
> Can we create the servers in a different domain, moving them to our
> production domain when testing has been completed? And if so, how do we
> handle the fact that the VSQLx and named instances already exists in Active
> Directory? Can the old server just be turned off, the new one brought up and
> added to the domain by resetting the current domain accounts and re-joining?
> Of course. Does anyone have a good solution, I'm all ears. Thanks
|||Yes, you are correct regarding the Virtual Server naming (careless cutting
and pasting on my part). Ideally, we would like to test the new cluster for
several days prior to bringing it live. My main concern is that the reusing
of the names doesn't cause a problem. Am I correct in my assumtions that AD
isn't involved in the virtual server or instance naming and that the only
network ties are through the DNS entries?
ALso, would you expect that any issues with restoring the master and msdb to
the new cluster instances (any references to the old nodes etc...)?
Thank you.
"Linchi Shea" wrote:
[vbcol=seagreen]
> That can't be your current setup. Your current setup is probably more like:
> NODE01
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
> NODE02
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
> I'd probably just do a switchover with the current cluster. First, get the
> necessary database files to a staging server. Then, remove the cluster from
> the network. But keep it as your rollback plan. Create two new clusters and
> install SQL instances as follows:
> New Cluster 1:
> NODE01 - active
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
> NODE02 - inactive
> New Cluster 2:
> NODE01 - active
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
> And finally get the database files from the staging server to their
> respective new servers.
> Linchi
> "randall_dh" wrote:
Showing posts with label active. Show all posts
Showing posts with label active. Show all posts
Friday, March 30, 2012
Monday, March 19, 2012
Moving SQL Server 2000 from an NT4 to Active Directory
Hi,
I'm afraid that I'm not very familiar with SQL Server so I was
wondering if anyone could point me in the right direction of what to
check?
We have just moved a SQL Server from NT4 to AD, all seems to go well
database started up ok and we were able to gain access to the data.
However we found a problem when running one of our internal web apps
which connects to SQL using a script file. The script file has changed
at all since we moved domains and we haven't changed the access rights
of the database user specified within the database. When we try to
login to the web app we get a page can't be displayed error, featuring
the following information
Error Type:
Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver] Timeout expired
/sar/includes/connection.asp, line 13
Page:
POST 51 byres to /sar/login/login_do.asp
Post Data:
txtUsername=TEST&txtPassword=Password&Submit=Login
I was wondering if it has anything to do with WINS, we haven't yet
migrated over the WINS Server as there are a couple of things we have
to do before we can change the domain.
Any help or pointers will be greatly appreciated.
Many Thanks
Jamie
It could be a name resolution problem. You can force the use of DNS by using
a fully qualified domain name in your connection string.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jamie" <jamie.m.garner@.gmail.com> wrote in message
news:1161105773.398539.112730@.k70g2000cwa.googlegr oups.com...
> Hi,
> I'm afraid that I'm not very familiar with SQL Server so I was
> wondering if anyone could point me in the right direction of what to
> check?
> We have just moved a SQL Server from NT4 to AD, all seems to go well
> database started up ok and we were able to gain access to the data.
> However we found a problem when running one of our internal web apps
> which connects to SQL using a script file. The script file has changed
> at all since we moved domains and we haven't changed the access rights
> of the database user specified within the database. When we try to
> login to the web app we get a page can't be displayed error, featuring
> the following information
> Error Type:
> Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> /sar/includes/connection.asp, line 13
> Page:
> POST 51 byres to /sar/login/login_do.asp
> Post Data:
> txtUsername=TEST&txtPassword=Password&Submit=Login
> I was wondering if it has anything to do with WINS, we haven't yet
> migrated over the WINS Server as there are a couple of things we have
> to do before we can change the domain.
> Any help or pointers will be greatly appreciated.
> Many Thanks
> Jamie
>
|||Thanks,
I'll give that a try
Jamie
Hilary Cotter wrote:[vbcol=seagreen]
> It could be a name resolution problem. You can force the use of DNS by using
> a fully qualified domain name in your connection string.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jamie" <jamie.m.garner@.gmail.com> wrote in message
> news:1161105773.398539.112730@.k70g2000cwa.googlegr oups.com...
I'm afraid that I'm not very familiar with SQL Server so I was
wondering if anyone could point me in the right direction of what to
check?
We have just moved a SQL Server from NT4 to AD, all seems to go well
database started up ok and we were able to gain access to the data.
However we found a problem when running one of our internal web apps
which connects to SQL using a script file. The script file has changed
at all since we moved domains and we haven't changed the access rights
of the database user specified within the database. When we try to
login to the web app we get a page can't be displayed error, featuring
the following information
Error Type:
Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver] Timeout expired
/sar/includes/connection.asp, line 13
Page:
POST 51 byres to /sar/login/login_do.asp
Post Data:
txtUsername=TEST&txtPassword=Password&Submit=Login
I was wondering if it has anything to do with WINS, we haven't yet
migrated over the WINS Server as there are a couple of things we have
to do before we can change the domain.
Any help or pointers will be greatly appreciated.
Many Thanks
Jamie
It could be a name resolution problem. You can force the use of DNS by using
a fully qualified domain name in your connection string.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jamie" <jamie.m.garner@.gmail.com> wrote in message
news:1161105773.398539.112730@.k70g2000cwa.googlegr oups.com...
> Hi,
> I'm afraid that I'm not very familiar with SQL Server so I was
> wondering if anyone could point me in the right direction of what to
> check?
> We have just moved a SQL Server from NT4 to AD, all seems to go well
> database started up ok and we were able to gain access to the data.
> However we found a problem when running one of our internal web apps
> which connects to SQL using a script file. The script file has changed
> at all since we moved domains and we haven't changed the access rights
> of the database user specified within the database. When we try to
> login to the web app we get a page can't be displayed error, featuring
> the following information
> Error Type:
> Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> /sar/includes/connection.asp, line 13
> Page:
> POST 51 byres to /sar/login/login_do.asp
> Post Data:
> txtUsername=TEST&txtPassword=Password&Submit=Login
> I was wondering if it has anything to do with WINS, we haven't yet
> migrated over the WINS Server as there are a couple of things we have
> to do before we can change the domain.
> Any help or pointers will be greatly appreciated.
> Many Thanks
> Jamie
>
|||Thanks,
I'll give that a try
Jamie
Hilary Cotter wrote:[vbcol=seagreen]
> It could be a name resolution problem. You can force the use of DNS by using
> a fully qualified domain name in your connection string.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jamie" <jamie.m.garner@.gmail.com> wrote in message
> news:1161105773.398539.112730@.k70g2000cwa.googlegr oups.com...
Moving SQL Server 2000 from an NT4 to Active Directory
Hi,
I'm afraid that I'm not very familiar with SQL Server so I was
wondering if anyone could point me in the right direction of what to
check?
We have just moved a SQL Server from NT4 to AD, all seems to go well
database started up ok and we were able to gain access to the data.
However we found a problem when running one of our internal web apps
which connects to SQL using a script file. The script file has changed
at all since we moved domains and we haven't changed the access rights
of the database user specified within the database. When we try to
login to the web app we get a page can't be displayed error, featuring
the following information
Error Type:
Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver] Timeout expired
/sar/includes/connection.asp, line 13
Page:
POST 51 byres to /sar/login/login_do.asp
Post Data:
txtUsername=TEST&txtPassword=Password&Submit=Login
I was wondering if it has anything to do with WINS, we haven't yet
migrated over the WINS Server as there are a couple of things we have
to do before we can change the domain.
Any help or pointers will be greatly appreciated.
Many Thanks
JamieIt could be a name resolution problem. You can force the use of DNS by using
a fully qualified domain name in your connection string.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jamie" <jamie.m.garner@.gmail.com> wrote in message
news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
> Hi,
> I'm afraid that I'm not very familiar with SQL Server so I was
> wondering if anyone could point me in the right direction of what to
> check?
> We have just moved a SQL Server from NT4 to AD, all seems to go well
> database started up ok and we were able to gain access to the data.
> However we found a problem when running one of our internal web apps
> which connects to SQL using a script file. The script file has changed
> at all since we moved domains and we haven't changed the access rights
> of the database user specified within the database. When we try to
> login to the web app we get a page can't be displayed error, featuring
> the following information
> Error Type:
> Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> /sar/includes/connection.asp, line 13
> Page:
> POST 51 byres to /sar/login/login_do.asp
> Post Data:
> txtUsername=TEST&txtPassword=Password&Submit=Login
> I was wondering if it has anything to do with WINS, we haven't yet
> migrated over the WINS Server as there are a couple of things we have
> to do before we can change the domain.
> Any help or pointers will be greatly appreciated.
> Many Thanks
> Jamie
>|||Thanks,
I'll give that a try
Jamie
Hilary Cotter wrote:
> It could be a name resolution problem. You can force the use of DNS by using
> a fully qualified domain name in your connection string.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jamie" <jamie.m.garner@.gmail.com> wrote in message
> news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
> > Hi,
> >
> > I'm afraid that I'm not very familiar with SQL Server so I was
> > wondering if anyone could point me in the right direction of what to
> > check?
> >
> > We have just moved a SQL Server from NT4 to AD, all seems to go well
> > database started up ok and we were able to gain access to the data.
> > However we found a problem when running one of our internal web apps
> > which connects to SQL using a script file. The script file has changed
> > at all since we moved domains and we haven't changed the access rights
> > of the database user specified within the database. When we try to
> > login to the web app we get a page can't be displayed error, featuring
> > the following information
> >
> > Error Type:
> > Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> > [Microsoft][ODBC SQL Server Driver] Timeout expired
> > /sar/includes/connection.asp, line 13
> >
> > Page:
> > POST 51 byres to /sar/login/login_do.asp
> >
> > Post Data:
> > txtUsername=TEST&txtPassword=Password&Submit=Login
> >
> > I was wondering if it has anything to do with WINS, we haven't yet
> > migrated over the WINS Server as there are a couple of things we have
> > to do before we can change the domain.
> >
> > Any help or pointers will be greatly appreciated.
> >
> > Many Thanks
> >
> > Jamie
> >
I'm afraid that I'm not very familiar with SQL Server so I was
wondering if anyone could point me in the right direction of what to
check?
We have just moved a SQL Server from NT4 to AD, all seems to go well
database started up ok and we were able to gain access to the data.
However we found a problem when running one of our internal web apps
which connects to SQL using a script file. The script file has changed
at all since we moved domains and we haven't changed the access rights
of the database user specified within the database. When we try to
login to the web app we get a page can't be displayed error, featuring
the following information
Error Type:
Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver] Timeout expired
/sar/includes/connection.asp, line 13
Page:
POST 51 byres to /sar/login/login_do.asp
Post Data:
txtUsername=TEST&txtPassword=Password&Submit=Login
I was wondering if it has anything to do with WINS, we haven't yet
migrated over the WINS Server as there are a couple of things we have
to do before we can change the domain.
Any help or pointers will be greatly appreciated.
Many Thanks
JamieIt could be a name resolution problem. You can force the use of DNS by using
a fully qualified domain name in your connection string.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jamie" <jamie.m.garner@.gmail.com> wrote in message
news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
> Hi,
> I'm afraid that I'm not very familiar with SQL Server so I was
> wondering if anyone could point me in the right direction of what to
> check?
> We have just moved a SQL Server from NT4 to AD, all seems to go well
> database started up ok and we were able to gain access to the data.
> However we found a problem when running one of our internal web apps
> which connects to SQL using a script file. The script file has changed
> at all since we moved domains and we haven't changed the access rights
> of the database user specified within the database. When we try to
> login to the web app we get a page can't be displayed error, featuring
> the following information
> Error Type:
> Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> /sar/includes/connection.asp, line 13
> Page:
> POST 51 byres to /sar/login/login_do.asp
> Post Data:
> txtUsername=TEST&txtPassword=Password&Submit=Login
> I was wondering if it has anything to do with WINS, we haven't yet
> migrated over the WINS Server as there are a couple of things we have
> to do before we can change the domain.
> Any help or pointers will be greatly appreciated.
> Many Thanks
> Jamie
>|||Thanks,
I'll give that a try
Jamie
Hilary Cotter wrote:
> It could be a name resolution problem. You can force the use of DNS by using
> a fully qualified domain name in your connection string.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jamie" <jamie.m.garner@.gmail.com> wrote in message
> news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
> > Hi,
> >
> > I'm afraid that I'm not very familiar with SQL Server so I was
> > wondering if anyone could point me in the right direction of what to
> > check?
> >
> > We have just moved a SQL Server from NT4 to AD, all seems to go well
> > database started up ok and we were able to gain access to the data.
> > However we found a problem when running one of our internal web apps
> > which connects to SQL using a script file. The script file has changed
> > at all since we moved domains and we haven't changed the access rights
> > of the database user specified within the database. When we try to
> > login to the web app we get a page can't be displayed error, featuring
> > the following information
> >
> > Error Type:
> > Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> > [Microsoft][ODBC SQL Server Driver] Timeout expired
> > /sar/includes/connection.asp, line 13
> >
> > Page:
> > POST 51 byres to /sar/login/login_do.asp
> >
> > Post Data:
> > txtUsername=TEST&txtPassword=Password&Submit=Login
> >
> > I was wondering if it has anything to do with WINS, we haven't yet
> > migrated over the WINS Server as there are a couple of things we have
> > to do before we can change the domain.
> >
> > Any help or pointers will be greatly appreciated.
> >
> > Many Thanks
> >
> > Jamie
> >
Moving SQL Server 2000 from an NT4 to Active Directory
Hi,
I'm afraid that I'm not very familiar with SQL Server so I was
wondering if anyone could point me in the right direction of what to
check?
We have just moved a SQL Server from NT4 to AD, all seems to go well
database started up ok and we were able to gain access to the data.
However we found a problem when running one of our internal web apps
which connects to SQL using a script file. The script file has changed
at all since we moved domains and we haven't changed the access rights
of the database user specified within the database. When we try to
login to the web app we get a page can't be displayed error, featuring
the following information
Error Type:
Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver] Timeout expired
/sar/includes/connection.asp, line 13
Page:
POST 51 byres to /sar/login/login_do.asp
Post Data:
txtUsername=TEST&txtPassword=Password&Submit=Login
I was wondering if it has anything to do with WINS, we haven't yet
migrated over the WINS Server as there are a couple of things we have
to do before we can change the domain.
Any help or pointers will be greatly appreciated.
Many Thanks
JamieIt could be a name resolution problem. You can force the use of DNS by using
a fully qualified domain name in your connection string.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jamie" <jamie.m.garner@.gmail.com> wrote in message
news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
> Hi,
> I'm afraid that I'm not very familiar with SQL Server so I was
> wondering if anyone could point me in the right direction of what to
> check?
> We have just moved a SQL Server from NT4 to AD, all seems to go well
> database started up ok and we were able to gain access to the data.
> However we found a problem when running one of our internal web apps
> which connects to SQL using a script file. The script file has changed
> at all since we moved domains and we haven't changed the access rights
> of the database user specified within the database. When we try to
> login to the web app we get a page can't be displayed error, featuring
> the following information
> Error Type:
> Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> /sar/includes/connection.asp, line 13
> Page:
> POST 51 byres to /sar/login/login_do.asp
> Post Data:
> txtUsername=TEST&txtPassword=Password&Submit=Login
> I was wondering if it has anything to do with WINS, we haven't yet
> migrated over the WINS Server as there are a couple of things we have
> to do before we can change the domain.
> Any help or pointers will be greatly appreciated.
> Many Thanks
> Jamie
>|||Thanks,
I'll give that a try
Jamie
Hilary Cotter wrote:[vbcol=seagreen]
> It could be a name resolution problem. You can force the use of DNS by usi
ng
> a fully qualified domain name in your connection string.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jamie" <jamie.m.garner@.gmail.com> wrote in message
> news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
I'm afraid that I'm not very familiar with SQL Server so I was
wondering if anyone could point me in the right direction of what to
check?
We have just moved a SQL Server from NT4 to AD, all seems to go well
database started up ok and we were able to gain access to the data.
However we found a problem when running one of our internal web apps
which connects to SQL using a script file. The script file has changed
at all since we moved domains and we haven't changed the access rights
of the database user specified within the database. When we try to
login to the web app we get a page can't be displayed error, featuring
the following information
Error Type:
Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver] Timeout expired
/sar/includes/connection.asp, line 13
Page:
POST 51 byres to /sar/login/login_do.asp
Post Data:
txtUsername=TEST&txtPassword=Password&Submit=Login
I was wondering if it has anything to do with WINS, we haven't yet
migrated over the WINS Server as there are a couple of things we have
to do before we can change the domain.
Any help or pointers will be greatly appreciated.
Many Thanks
JamieIt could be a name resolution problem. You can force the use of DNS by using
a fully qualified domain name in your connection string.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jamie" <jamie.m.garner@.gmail.com> wrote in message
news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
> Hi,
> I'm afraid that I'm not very familiar with SQL Server so I was
> wondering if anyone could point me in the right direction of what to
> check?
> We have just moved a SQL Server from NT4 to AD, all seems to go well
> database started up ok and we were able to gain access to the data.
> However we found a problem when running one of our internal web apps
> which connects to SQL using a script file. The script file has changed
> at all since we moved domains and we haven't changed the access rights
> of the database user specified within the database. When we try to
> login to the web app we get a page can't be displayed error, featuring
> the following information
> Error Type:
> Mircosoft OLE DB provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> /sar/includes/connection.asp, line 13
> Page:
> POST 51 byres to /sar/login/login_do.asp
> Post Data:
> txtUsername=TEST&txtPassword=Password&Submit=Login
> I was wondering if it has anything to do with WINS, we haven't yet
> migrated over the WINS Server as there are a couple of things we have
> to do before we can change the domain.
> Any help or pointers will be greatly appreciated.
> Many Thanks
> Jamie
>|||Thanks,
I'll give that a try
Jamie
Hilary Cotter wrote:[vbcol=seagreen]
> It could be a name resolution problem. You can force the use of DNS by usi
ng
> a fully qualified domain name in your connection string.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jamie" <jamie.m.garner@.gmail.com> wrote in message
> news:1161105773.398539.112730@.k70g2000cwa.googlegroups.com...
Monday, March 12, 2012
Moving SQL 6.5 from NT 4.0 to W2K3. Please help
Hello,
As part of Active Directory migration (from NT 4.0 to Server 2003
Enterprise), we will be replacing our current SQL server hardware with a
newer server which will be running windows 2003. Can anyone point me to any
document on how to go about doing this please. I am very new to SQL
migration, what are the things that I should be watching? The customer does
not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
doing that?
ThanksHi
SQL 6.5 is not supported on Windows 2003, and neither is SQL Server 7.0
SQL 6.5 is no longer supported since 31-Jan-2002 and SQL 7.0 dies
31-Dec-2005.
SQL 2000 is his only option.
http://support.microsoft.com/gp/lifesrvr
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"warsai" <warsai@.discussions.microsoft.com> wrote in message
news:842BB3B4-47AF-499C-B0BC-A91683255F7E@.microsoft.com...
> Hello,
> As part of Active Directory migration (from NT 4.0 to Server 2003
> Enterprise), we will be replacing our current SQL server hardware with a
> newer server which will be running windows 2003. Can anyone point me to
any
> document on how to go about doing this please. I am very new to SQL
> migration, what are the things that I should be watching? The customer
does
> not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
> doing that?
> Thanks
>
As part of Active Directory migration (from NT 4.0 to Server 2003
Enterprise), we will be replacing our current SQL server hardware with a
newer server which will be running windows 2003. Can anyone point me to any
document on how to go about doing this please. I am very new to SQL
migration, what are the things that I should be watching? The customer does
not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
doing that?
ThanksHi
SQL 6.5 is not supported on Windows 2003, and neither is SQL Server 7.0
SQL 6.5 is no longer supported since 31-Jan-2002 and SQL 7.0 dies
31-Dec-2005.
SQL 2000 is his only option.
http://support.microsoft.com/gp/lifesrvr
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"warsai" <warsai@.discussions.microsoft.com> wrote in message
news:842BB3B4-47AF-499C-B0BC-A91683255F7E@.microsoft.com...
> Hello,
> As part of Active Directory migration (from NT 4.0 to Server 2003
> Enterprise), we will be replacing our current SQL server hardware with a
> newer server which will be running windows 2003. Can anyone point me to
any
> document on how to go about doing this please. I am very new to SQL
> migration, what are the things that I should be watching? The customer
does
> not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
> doing that?
> Thanks
>
Moving SQL 6.5 from NT 4.0 to W2K3. Please help
Hello,
As part of Active Directory migration (from NT 4.0 to Server 2003
Enterprise), we will be replacing our current SQL server hardware with a
newer server which will be running windows 2003. Can anyone point me to any
document on how to go about doing this please. I am very new to SQL
migration, what are the things that I should be watching? The customer does
not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
doing that?
Thanks
Hi
SQL 6.5 is not supported on Windows 2003, and neither is SQL Server 7.0
SQL 6.5 is no longer supported since 31-Jan-2002 and SQL 7.0 dies
31-Dec-2005.
SQL 2000 is his only option.
http://support.microsoft.com/gp/lifesrvr
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"warsai" <warsai@.discussions.microsoft.com> wrote in message
news:842BB3B4-47AF-499C-B0BC-A91683255F7E@.microsoft.com...
> Hello,
> As part of Active Directory migration (from NT 4.0 to Server 2003
> Enterprise), we will be replacing our current SQL server hardware with a
> newer server which will be running windows 2003. Can anyone point me to
any
> document on how to go about doing this please. I am very new to SQL
> migration, what are the things that I should be watching? The customer
does
> not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
> doing that?
> Thanks
>
As part of Active Directory migration (from NT 4.0 to Server 2003
Enterprise), we will be replacing our current SQL server hardware with a
newer server which will be running windows 2003. Can anyone point me to any
document on how to go about doing this please. I am very new to SQL
migration, what are the things that I should be watching? The customer does
not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
doing that?
Thanks
Hi
SQL 6.5 is not supported on Windows 2003, and neither is SQL Server 7.0
SQL 6.5 is no longer supported since 31-Jan-2002 and SQL 7.0 dies
31-Dec-2005.
SQL 2000 is his only option.
http://support.microsoft.com/gp/lifesrvr
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"warsai" <warsai@.discussions.microsoft.com> wrote in message
news:842BB3B4-47AF-499C-B0BC-A91683255F7E@.microsoft.com...
> Hello,
> As part of Active Directory migration (from NT 4.0 to Server 2003
> Enterprise), we will be replacing our current SQL server hardware with a
> newer server which will be running windows 2003. Can anyone point me to
any
> document on how to go about doing this please. I am very new to SQL
> migration, what are the things that I should be watching? The customer
does
> not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
> doing that?
> Thanks
>
Moving SQL 6.5 from NT 4.0 to W2K3. Please help
Hello,
As part of Active Directory migration (from NT 4.0 to Server 2003
Enterprise), we will be replacing our current SQL server hardware with a
newer server which will be running windows 2003. Can anyone point me to any
document on how to go about doing this please. I am very new to SQL
migration, what are the things that I should be watching? The customer does
not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
doing that?
ThanksHi
SQL 6.5 is not supported on Windows 2003, and neither is SQL Server 7.0
SQL 6.5 is no longer supported since 31-Jan-2002 and SQL 7.0 dies
31-Dec-2005.
SQL 2000 is his only option.
http://support.microsoft.com/gp/lifesrvr
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"warsai" <warsai@.discussions.microsoft.com> wrote in message
news:842BB3B4-47AF-499C-B0BC-A91683255F7E@.microsoft.com...
> Hello,
> As part of Active Directory migration (from NT 4.0 to Server 2003
> Enterprise), we will be replacing our current SQL server hardware with a
> newer server which will be running windows 2003. Can anyone point me to
any
> document on how to go about doing this please. I am very new to SQL
> migration, what are the things that I should be watching? The customer
does
> not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
> doing that?
> Thanks
>
As part of Active Directory migration (from NT 4.0 to Server 2003
Enterprise), we will be replacing our current SQL server hardware with a
newer server which will be running windows 2003. Can anyone point me to any
document on how to go about doing this please. I am very new to SQL
migration, what are the things that I should be watching? The customer does
not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
doing that?
ThanksHi
SQL 6.5 is not supported on Windows 2003, and neither is SQL Server 7.0
SQL 6.5 is no longer supported since 31-Jan-2002 and SQL 7.0 dies
31-Dec-2005.
SQL 2000 is his only option.
http://support.microsoft.com/gp/lifesrvr
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"warsai" <warsai@.discussions.microsoft.com> wrote in message
news:842BB3B4-47AF-499C-B0BC-A91683255F7E@.microsoft.com...
> Hello,
> As part of Active Directory migration (from NT 4.0 to Server 2003
> Enterprise), we will be replacing our current SQL server hardware with a
> newer server which will be running windows 2003. Can anyone point me to
any
> document on how to go about doing this please. I am very new to SQL
> migration, what are the things that I should be watching? The customer
does
> not want to upgrade to SQL2000 (prefers to stay with 6.5). Any issues with
> doing that?
> Thanks
>
Subscribe to:
Posts (Atom)