I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and
another instance. While the default services is disabled and the other
instance is running, Server B runs the default instance and has the other
instance disabled. This basically acts like a 2 way cluster
(active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the
nodes come up the correct way? What are the steps to achieve this?http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-
C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||This is not going to help me. I have explicitly mentioned that I have a 2
way cluster in my original email. So a standard article like you have given
me is NOT going to help.
"Ole Kristian Bangås" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns981DB671F914Folekristianbangaas@.207.46.248.16...
> http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-
> C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ole Kristian Bangås
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
> This is not going to help me. I have explicitly mentioned that I have
> a 2 way cluster in my original email. So a standard article like you
> have given me is NOT going to help.
Yes, and I don't quite get the problem. Let me quote point two in the
article I gave a link to:
"Run the service pack from the node that owns the group containing the
virtual server that you plan to upgrade. This installs the service pack
files on all nodes in the failover cluster."
Can you please explain what your problem is? As I understand your scenario
you have a two-node two-instance active-passive SQL cluster. An upgrade of
that cluster should be rather straightforward.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
Correction to my previous post, You actually have an active/active
confuguration, with one instance on each server, but the upgrade procedure
is still valid.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP
Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts
Tuesday, March 20, 2012
Applying SP4 on an active/passive 2 way cluster
I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and another instance. While the default services is disabled and the other instance is running, Server B runs the default instance and has the other instance disabled. This basically acts like a 2 way cluster (active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the nodes come up the correct way? What are the steps to achieve this?Since SQL Server is a shared resource on a clustered server, installing SP4 on one server is automatically done on the other. Everything is transparent to the user/admin.sql
Applying SP4 on an active/passive 2 way cluster
I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and
another instance. While the default services is disabled and the other
instance is running, Server B runs the default instance and has the other
instance disabled. This basically acts like a 2 way cluster
(active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the
nodes come up the correct way? What are the steps to achieve this?http://download.microsoft.com/downl...584E-4DE0-B36F-
C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||This is not going to help me. I have explicitly mentioned that I have a 2
way cluster in my original email. So a standard article like you have given
me is NOT going to help.
"Ole Kristian Bangs" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns981DB671F914Folekristianbangaas@.
207.46.248.16...
> http://download.microsoft.com/downl...584E-4DE0-B36F-
> C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ole Kristian Bangs
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
> This is not going to help me. I have explicitly mentioned that I have
> a 2 way cluster in my original email. So a standard article like you
> have given me is NOT going to help.
Yes, and I don't quite get the problem. Let me quote point two in the
article I gave a link to:
"Run the service pack from the node that owns the group containing the
virtual server that you plan to upgrade. This installs the service pack
files on all nodes in the failover cluster."
Can you please explain what your problem is? As I understand your scenario
you have a two-node two-instance active-passive SQL cluster. An upgrade of
that cluster should be rather straightforward.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
Correction to my previous post, You actually have an active/active
confuguration, with one instance on each server, but the upgrade procedure
is still valid.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP
Basically, I have 2 servers. Server A runs a default instance and
another instance. While the default services is disabled and the other
instance is running, Server B runs the default instance and has the other
instance disabled. This basically acts like a 2 way cluster
(active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the
nodes come up the correct way? What are the steps to achieve this?http://download.microsoft.com/downl...584E-4DE0-B36F-
C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||This is not going to help me. I have explicitly mentioned that I have a 2
way cluster in my original email. So a standard article like you have given
me is NOT going to help.
"Ole Kristian Bangs" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns981DB671F914Folekristianbangaas@.
207.46.248.16...
> http://download.microsoft.com/downl...584E-4DE0-B36F-
> C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ole Kristian Bangs
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
> This is not going to help me. I have explicitly mentioned that I have
> a 2 way cluster in my original email. So a standard article like you
> have given me is NOT going to help.
Yes, and I don't quite get the problem. Let me quote point two in the
article I gave a link to:
"Run the service pack from the node that owns the group containing the
virtual server that you plan to upgrade. This installs the service pack
files on all nodes in the failover cluster."
Can you please explain what your problem is? As I understand your scenario
you have a two-node two-instance active-passive SQL cluster. An upgrade of
that cluster should be rather straightforward.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
Correction to my previous post, You actually have an active/active
confuguration, with one instance on each server, but the upgrade procedure
is still valid.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP
Monday, March 19, 2012
Applying SP2a to SQL 2000/Win 2003
I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon Shargorodsky
Leon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com
|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon Shargorodsky
Leon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com
|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Applying SP2a to SQL 2000/Win 2003
I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard tha
t
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard tha
t
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Applying SP2a to SQL 2000/Win 2003
I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
--
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> > I'm getting this error message while trying to apply SP3a to SQL
> > Server 2000 Standard that runs on Windows Server 2003:
> >
> > "Setup was unable to verify the state of the server for an upgrade.
> > Verify the server is able to start and that you provided a valid sa
> > password and restart setup"
> >
> > My sa password is definitely valid (verified), I'm able to stop and
> > restart SQL Server service manually with no problem. Please advise,
> > this problem happens every time I try to run SP3 or SP3a for SQL
> > Server 2000 Standard that runs on Windows Server 2003.
> >
> > Thanks you in advance for your help,
> >
> > Leon Shargorodsky
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
--
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> > I'm getting this error message while trying to apply SP3a to SQL
> > Server 2000 Standard that runs on Windows Server 2003:
> >
> > "Setup was unable to verify the state of the server for an upgrade.
> > Verify the server is able to start and that you provided a valid sa
> > password and restart setup"
> >
> > My sa password is definitely valid (verified), I'm able to stop and
> > restart SQL Server service manually with no problem. Please advise,
> > this problem happens every time I try to run SP3 or SP3a for SQL
> > Server 2000 Standard that runs on Windows Server 2003.
> >
> > Thanks you in advance for your help,
> >
> > Leon Shargorodsky
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Thursday, March 8, 2012
application with sql server database failing
Hi all,
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql serve
r
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql ser
ver
> database while application is running through a scheduled process it is ju
st
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are
in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give m
e
> some advices why this canb happen?
> Thank you,
> BaniSQL.
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql serve
r
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql ser
ver
> database while application is running through a scheduled process it is ju
st
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are
in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give m
e
> some advices why this canb happen?
> Thank you,
> BaniSQL.
application with sql server database failing
Hi all,
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql server
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql server
> database while application is running through a scheduled process it is just
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give me
> some advices why this canb happen?
> Thank you,
> BaniSQL.
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql server
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql server
> database while application is running through a scheduled process it is just
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give me
> some advices why this canb happen?
> Thank you,
> BaniSQL.
Saturday, February 25, 2012
Application needs replication
Hi
We have an MS Access application which runs on the server but some laptop
users need the app to work offline. Our solution has been to use Access
replication which automatically syncs data (both ways) when laptop is
connected to the network. We are looking to rewrite the app to vb.net/sql
server. My question is how does replication work in sql server specially in
context of a vb.net front end i.e. what sort of coding/configuration we are
we looking at?
Thanks
RegardsWell since you will have disconnected users; you will need to have a local
instance of the SQL Server installed on the computer. Then you can SQL
Server 2005 Merge Replication Topology to do what yaa needed. Read up on it
at ..
http://technet.microsoft.com/en-us/sqlserver/bb331775.aspx
Thanks!
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John" wrote:
> Hi
> We have an MS Access application which runs on the server but some laptop
> users need the app to work offline. Our solution has been to use Access
> replication which automatically syncs data (both ways) when laptop is
> connected to the network. We are looking to rewrite the app to vb.net/sql
> server. My question is how does replication work in sql server specially in
> context of a vb.net front end i.e. what sort of coding/configuration we are
> we looking at?
> Thanks
> Regards
>
>|||Am I right to believe I need to code as if my app is connected to the same
single sql server and various sql server installs would automatically take
care of the sync between themselves without intervention by app when laptops
are connected to the network?
Thanks
Regards
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:D4FD10E6-2DF6-486A-B6F9-88000C5A076A@.microsoft.com...
> Well since you will have disconnected users; you will need to have a local
> instance of the SQL Server installed on the computer. Then you can SQL
> Server 2005 Merge Replication Topology to do what yaa needed. Read up on
> it
> at ..
> http://technet.microsoft.com/en-us/sqlserver/bb331775.aspx
> Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "John" wrote:
>> Hi
>> We have an MS Access application which runs on the server but some laptop
>> users need the app to work offline. Our solution has been to use Access
>> replication which automatically syncs data (both ways) when laptop is
>> connected to the network. We are looking to rewrite the app to vb.net/sql
>> server. My question is how does replication work in sql server specially
>> in
>> context of a vb.net front end i.e. what sort of coding/configuration we
>> are
>> we looking at?
>> Thanks
>> Regards
>>|||In a sense yes, but actually no. What I mean is, since you will have a
local install of SQL Server on each laptop; you can code the application to
connect to localhost and no coding required for developer for connecting
parts. But in fact; these are all different instances of SQL Server on
different computer, everyone will have different names.
I haven't coded for replication enviornment, but few challanges that face
you developers is handling merge conflicts. Three possible cases can happen:
1) Record is updated, but no longer exists.
2) Insert a record; and causes a duplicate primary key.
3) Updating same records in two locations, both valid but are in conflict.
Replication is usually timed event; so onces the server is on the network,
the local server will talk to the distributor and the publitioning database
to update information as needed. I hope this gives you some ideas. Thanks!
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John" wrote:
> Am I right to believe I need to code as if my app is connected to the same
> single sql server and various sql server installs would automatically take
> care of the sync between themselves without intervention by app when laptops
> are connected to the network?
> Thanks
> Regards
> "Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
> news:D4FD10E6-2DF6-486A-B6F9-88000C5A076A@.microsoft.com...
> > Well since you will have disconnected users; you will need to have a local
> > instance of the SQL Server installed on the computer. Then you can SQL
> > Server 2005 Merge Replication Topology to do what yaa needed. Read up on
> > it
> > at ..
> > http://technet.microsoft.com/en-us/sqlserver/bb331775.aspx
> >
> > Thanks!
> > --
> > Mohit K. Gupta
> > B.Sc. CS, Minor Japanese
> > MCTS: SQL Server 2005
> >
> >
> > "John" wrote:
> >
> >> Hi
> >>
> >> We have an MS Access application which runs on the server but some laptop
> >> users need the app to work offline. Our solution has been to use Access
> >> replication which automatically syncs data (both ways) when laptop is
> >> connected to the network. We are looking to rewrite the app to vb.net/sql
> >> server. My question is how does replication work in sql server specially
> >> in
> >> context of a vb.net front end i.e. what sort of coding/configuration we
> >> are
> >> we looking at?
> >>
> >> Thanks
> >>
> >> Regards
> >>
> >>
> >>
>
>|||John,
You have at least two possiblilties, use a replication of the SQL server
using by instance SQL Client, or make your application in a way that it uses
DataSets from the needed information.
The latter is very easy to do and the way I would go in your situation.
Cor|||And you don't need SQL Server installed on the client(s). Another
alternative is SQL Server Compact Edition on the clients. It can also act as
a Subscriber to a SQL Server Publisher. Note that a SQL Server Publisher
must be Workgroup or better--SQL Express does not support this
functionality. In addition, you might consider using the new ADO.NET 3.5
Sync Services due out with Orcas (before the end of the year). In this case
you don't need SQL Server to act as a Publisher.
I discuss most of these options in my Ebook on SQL CE.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"John" <John@.nospam.infovis.co.uk> wrote in message
news:O4l0ZMECIHA.324@.TK2MSFTNGP04.phx.gbl...
> Hi
> We have an MS Access application which runs on the server but some laptop
> users need the app to work offline. Our solution has been to use Access
> replication which automatically syncs data (both ways) when laptop is
> connected to the network. We are looking to rewrite the app to vb.net/sql
> server. My question is how does replication work in sql server specially
> in context of a vb.net front end i.e. what sort of coding/configuration we
> are we looking at?
> Thanks
> Regards
>|||Hi Cor
Thanks. How does one keep data persistent on client side when using
datasets, bearing in mind that clients (laptops) will be disconnected from
the network/sql server often but would need access to sql server data
offline? If you can point to some reading that would be great.
Many Thanks
Regards
"Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
news:14F13D20-64C8-46CB-BEF1-CC700A4A6474@.microsoft.com...
> John,
> You have at least two possiblilties, use a replication of the SQL server
> using by instance SQL Client, or make your application in a way that it
> uses DataSets from the needed information.
> The latter is very easy to do and the way I would go in your situation.
> Cor
>|||Take a look at Sybase SQL Anywhere. It's replication capabilities are truly
amazing.
"John" <John@.nospam.infovis.co.uk> wrote in message
news:O4l0ZMECIHA.324@.TK2MSFTNGP04.phx.gbl...
> Hi
> We have an MS Access application which runs on the server but some laptop
> users need the app to work offline. Our solution has been to use Access
> replication which automatically syncs data (both ways) when laptop is
> connected to the network. We are looking to rewrite the app to vb.net/sql
> server. My question is how does replication work in sql server specially
> in context of a vb.net front end i.e. what sort of coding/configuration we
> are we looking at?
> Thanks
> Regards
>|||John,
The nature from a dataset is to work ofline, it is build for that.
When you do an update, there is looked if there has been a change (this is
called optimistic concurrency). The way as the data is organised makes that
the chanch for that is low or high.
By instance as you are adding and subtrackting values from tablerows,
instead of adding mutation rows, then you can probably forget it.
Cor|||Ah, I expect he means you can serialize the DataTable(s) to an XML file or
somesuch.
Again, the SQL Server Compact Edition (which supports several kinds of
replication) is a better option.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
news:522F9B5D-D648-4D7B-99F1-58EAB1B33923@.microsoft.com...
> John,
> The nature from a dataset is to work ofline, it is build for that.
> When you do an update, there is looked if there has been a change (this is
> called optimistic concurrency). The way as the data is organised makes
> that the chanch for that is low or high.
> By instance as you are adding and subtrackting values from tablerows,
> instead of adding mutation rows, then you can probably forget it.
> Cor|||Thanks Bill.
Regards
"William Vaughn" <billvaNoSPAM@.betav.com> wrote in message
news:OYv3bNdCIHA.6012@.TK2MSFTNGP03.phx.gbl...
> Ah, I expect he means you can serialize the DataTable(s) to an XML file
> or somesuch.
> Again, the SQL Server Compact Edition (which supports several kinds of
> replication) is a better option.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
> news:522F9B5D-D648-4D7B-99F1-58EAB1B33923@.microsoft.com...
>> John,
>> The nature from a dataset is to work ofline, it is build for that.
>> When you do an update, there is looked if there has been a change (this
>> is called optimistic concurrency). The way as the data is organised makes
>> that the chanch for that is low or high.
>> By instance as you are adding and subtrackting values from tablerows,
>> instead of adding mutation rows, then you can probably forget it.
>> Cor
>|||Bill,
I disagree this with you, for extra database you need replication, with a
dataset you just needs common updates. The logical problems stays exactly
the same.
The serialization is completely automaticaly done by Dataset.ReadXML(...)
and Dataset.WriteXML(...), you write it as if this is a problem.
Cor|||Cor, you missed the point. Replication in this case is used for data
sharing--not just data persistence.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
news:C859F647-3DB1-404A-AC9E-10213DDFA7AC@.microsoft.com...
> Bill,
> I disagree this with you, for extra database you need replication, with a
> dataset you just needs common updates. The logical problems stays exactly
> the same.
> The serialization is completely automaticaly done by Dataset.ReadXML(...)
> and Dataset.WriteXML(...), you write it as if this is a problem.
> Cor|||> Cor, you missed the point. Replication in this case is used for data
> sharing--not just data persistence.
I did not miss that Bill, however why would you do that if there are now
simple methods possible in ADONET and not only replication. Using a dataset
is in my idea much easier to handle conflicts by your own program.
Cor
We have an MS Access application which runs on the server but some laptop
users need the app to work offline. Our solution has been to use Access
replication which automatically syncs data (both ways) when laptop is
connected to the network. We are looking to rewrite the app to vb.net/sql
server. My question is how does replication work in sql server specially in
context of a vb.net front end i.e. what sort of coding/configuration we are
we looking at?
Thanks
RegardsWell since you will have disconnected users; you will need to have a local
instance of the SQL Server installed on the computer. Then you can SQL
Server 2005 Merge Replication Topology to do what yaa needed. Read up on it
at ..
http://technet.microsoft.com/en-us/sqlserver/bb331775.aspx
Thanks!
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John" wrote:
> Hi
> We have an MS Access application which runs on the server but some laptop
> users need the app to work offline. Our solution has been to use Access
> replication which automatically syncs data (both ways) when laptop is
> connected to the network. We are looking to rewrite the app to vb.net/sql
> server. My question is how does replication work in sql server specially in
> context of a vb.net front end i.e. what sort of coding/configuration we are
> we looking at?
> Thanks
> Regards
>
>|||Am I right to believe I need to code as if my app is connected to the same
single sql server and various sql server installs would automatically take
care of the sync between themselves without intervention by app when laptops
are connected to the network?
Thanks
Regards
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:D4FD10E6-2DF6-486A-B6F9-88000C5A076A@.microsoft.com...
> Well since you will have disconnected users; you will need to have a local
> instance of the SQL Server installed on the computer. Then you can SQL
> Server 2005 Merge Replication Topology to do what yaa needed. Read up on
> it
> at ..
> http://technet.microsoft.com/en-us/sqlserver/bb331775.aspx
> Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "John" wrote:
>> Hi
>> We have an MS Access application which runs on the server but some laptop
>> users need the app to work offline. Our solution has been to use Access
>> replication which automatically syncs data (both ways) when laptop is
>> connected to the network. We are looking to rewrite the app to vb.net/sql
>> server. My question is how does replication work in sql server specially
>> in
>> context of a vb.net front end i.e. what sort of coding/configuration we
>> are
>> we looking at?
>> Thanks
>> Regards
>>|||In a sense yes, but actually no. What I mean is, since you will have a
local install of SQL Server on each laptop; you can code the application to
connect to localhost and no coding required for developer for connecting
parts. But in fact; these are all different instances of SQL Server on
different computer, everyone will have different names.
I haven't coded for replication enviornment, but few challanges that face
you developers is handling merge conflicts. Three possible cases can happen:
1) Record is updated, but no longer exists.
2) Insert a record; and causes a duplicate primary key.
3) Updating same records in two locations, both valid but are in conflict.
Replication is usually timed event; so onces the server is on the network,
the local server will talk to the distributor and the publitioning database
to update information as needed. I hope this gives you some ideas. Thanks!
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John" wrote:
> Am I right to believe I need to code as if my app is connected to the same
> single sql server and various sql server installs would automatically take
> care of the sync between themselves without intervention by app when laptops
> are connected to the network?
> Thanks
> Regards
> "Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
> news:D4FD10E6-2DF6-486A-B6F9-88000C5A076A@.microsoft.com...
> > Well since you will have disconnected users; you will need to have a local
> > instance of the SQL Server installed on the computer. Then you can SQL
> > Server 2005 Merge Replication Topology to do what yaa needed. Read up on
> > it
> > at ..
> > http://technet.microsoft.com/en-us/sqlserver/bb331775.aspx
> >
> > Thanks!
> > --
> > Mohit K. Gupta
> > B.Sc. CS, Minor Japanese
> > MCTS: SQL Server 2005
> >
> >
> > "John" wrote:
> >
> >> Hi
> >>
> >> We have an MS Access application which runs on the server but some laptop
> >> users need the app to work offline. Our solution has been to use Access
> >> replication which automatically syncs data (both ways) when laptop is
> >> connected to the network. We are looking to rewrite the app to vb.net/sql
> >> server. My question is how does replication work in sql server specially
> >> in
> >> context of a vb.net front end i.e. what sort of coding/configuration we
> >> are
> >> we looking at?
> >>
> >> Thanks
> >>
> >> Regards
> >>
> >>
> >>
>
>|||John,
You have at least two possiblilties, use a replication of the SQL server
using by instance SQL Client, or make your application in a way that it uses
DataSets from the needed information.
The latter is very easy to do and the way I would go in your situation.
Cor|||And you don't need SQL Server installed on the client(s). Another
alternative is SQL Server Compact Edition on the clients. It can also act as
a Subscriber to a SQL Server Publisher. Note that a SQL Server Publisher
must be Workgroup or better--SQL Express does not support this
functionality. In addition, you might consider using the new ADO.NET 3.5
Sync Services due out with Orcas (before the end of the year). In this case
you don't need SQL Server to act as a Publisher.
I discuss most of these options in my Ebook on SQL CE.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"John" <John@.nospam.infovis.co.uk> wrote in message
news:O4l0ZMECIHA.324@.TK2MSFTNGP04.phx.gbl...
> Hi
> We have an MS Access application which runs on the server but some laptop
> users need the app to work offline. Our solution has been to use Access
> replication which automatically syncs data (both ways) when laptop is
> connected to the network. We are looking to rewrite the app to vb.net/sql
> server. My question is how does replication work in sql server specially
> in context of a vb.net front end i.e. what sort of coding/configuration we
> are we looking at?
> Thanks
> Regards
>|||Hi Cor
Thanks. How does one keep data persistent on client side when using
datasets, bearing in mind that clients (laptops) will be disconnected from
the network/sql server often but would need access to sql server data
offline? If you can point to some reading that would be great.
Many Thanks
Regards
"Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
news:14F13D20-64C8-46CB-BEF1-CC700A4A6474@.microsoft.com...
> John,
> You have at least two possiblilties, use a replication of the SQL server
> using by instance SQL Client, or make your application in a way that it
> uses DataSets from the needed information.
> The latter is very easy to do and the way I would go in your situation.
> Cor
>|||Take a look at Sybase SQL Anywhere. It's replication capabilities are truly
amazing.
"John" <John@.nospam.infovis.co.uk> wrote in message
news:O4l0ZMECIHA.324@.TK2MSFTNGP04.phx.gbl...
> Hi
> We have an MS Access application which runs on the server but some laptop
> users need the app to work offline. Our solution has been to use Access
> replication which automatically syncs data (both ways) when laptop is
> connected to the network. We are looking to rewrite the app to vb.net/sql
> server. My question is how does replication work in sql server specially
> in context of a vb.net front end i.e. what sort of coding/configuration we
> are we looking at?
> Thanks
> Regards
>|||John,
The nature from a dataset is to work ofline, it is build for that.
When you do an update, there is looked if there has been a change (this is
called optimistic concurrency). The way as the data is organised makes that
the chanch for that is low or high.
By instance as you are adding and subtrackting values from tablerows,
instead of adding mutation rows, then you can probably forget it.
Cor|||Ah, I expect he means you can serialize the DataTable(s) to an XML file or
somesuch.
Again, the SQL Server Compact Edition (which supports several kinds of
replication) is a better option.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
news:522F9B5D-D648-4D7B-99F1-58EAB1B33923@.microsoft.com...
> John,
> The nature from a dataset is to work ofline, it is build for that.
> When you do an update, there is looked if there has been a change (this is
> called optimistic concurrency). The way as the data is organised makes
> that the chanch for that is low or high.
> By instance as you are adding and subtrackting values from tablerows,
> instead of adding mutation rows, then you can probably forget it.
> Cor|||Thanks Bill.
Regards
"William Vaughn" <billvaNoSPAM@.betav.com> wrote in message
news:OYv3bNdCIHA.6012@.TK2MSFTNGP03.phx.gbl...
> Ah, I expect he means you can serialize the DataTable(s) to an XML file
> or somesuch.
> Again, the SQL Server Compact Edition (which supports several kinds of
> replication) is a better option.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
> news:522F9B5D-D648-4D7B-99F1-58EAB1B33923@.microsoft.com...
>> John,
>> The nature from a dataset is to work ofline, it is build for that.
>> When you do an update, there is looked if there has been a change (this
>> is called optimistic concurrency). The way as the data is organised makes
>> that the chanch for that is low or high.
>> By instance as you are adding and subtrackting values from tablerows,
>> instead of adding mutation rows, then you can probably forget it.
>> Cor
>|||Bill,
I disagree this with you, for extra database you need replication, with a
dataset you just needs common updates. The logical problems stays exactly
the same.
The serialization is completely automaticaly done by Dataset.ReadXML(...)
and Dataset.WriteXML(...), you write it as if this is a problem.
Cor|||Cor, you missed the point. Replication in this case is used for data
sharing--not just data persistence.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Cor Ligthert[MVP]" <notmyfirstname@.planet.nl> wrote in message
news:C859F647-3DB1-404A-AC9E-10213DDFA7AC@.microsoft.com...
> Bill,
> I disagree this with you, for extra database you need replication, with a
> dataset you just needs common updates. The logical problems stays exactly
> the same.
> The serialization is completely automaticaly done by Dataset.ReadXML(...)
> and Dataset.WriteXML(...), you write it as if this is a problem.
> Cor|||> Cor, you missed the point. Replication in this case is used for data
> sharing--not just data persistence.
I did not miss that Bill, however why would you do that if there are now
simple methods possible in ADONET and not only replication. Using a dataset
is in my idea much easier to handle conflicts by your own program.
Cor
Friday, February 24, 2012
Application
Does anyone know of an agent/application that runs on SQL Server that will
allow me to do some sort of process billing? Used to be quite common in the
old days, to bill back users for their usage. Since I have a hosted
application, I want to bill for CPU usage.
I know that I can use SQL Profiler, but was hoping for an agent or service
that would allow me to bill based on DB or User.
See my post in the microsoft.public.sqlserver.server thread.
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23IBOkgH3EHA.1192@.tk2msftngp13.phx.gbl...
> Does anyone know of an agent/application that runs on SQL Server that will
> allow me to do some sort of process billing? Used to be quite common in
the
> old days, to bill back users for their usage. Since I have a hosted
> application, I want to bill for CPU usage.
> I know that I can use SQL Profiler, but was hoping for an agent or service
> that would allow me to bill based on DB or User.
>
allow me to do some sort of process billing? Used to be quite common in the
old days, to bill back users for their usage. Since I have a hosted
application, I want to bill for CPU usage.
I know that I can use SQL Profiler, but was hoping for an agent or service
that would allow me to bill based on DB or User.
See my post in the microsoft.public.sqlserver.server thread.
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23IBOkgH3EHA.1192@.tk2msftngp13.phx.gbl...
> Does anyone know of an agent/application that runs on SQL Server that will
> allow me to do some sort of process billing? Used to be quite common in
the
> old days, to bill back users for their usage. Since I have a hosted
> application, I want to bill for CPU usage.
> I know that I can use SQL Profiler, but was hoping for an agent or service
> that would allow me to bill based on DB or User.
>
Application
Does anyone know of an agent/application that runs on SQL Server that will
allow me to do some sort of process billing? Used to be quite common in the
old days, to bill back users for their usage. Since I have a hosted
application, I want to bill for CPU usage.
I know that I can use SQL Profiler, but was hoping for an agent or service
that would allow me to bill based on DB or User.I would set up a server side trace that logged the the events that you need
to a sql server table. Here is an article I wrote on the subject that
might help you get started with server side tracing:
http://www.dbazine.com/larsen6.shtml
--
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23M5QpgH3EHA.1524@.TK2MSFTNGP09.phx.gbl...
> Does anyone know of an agent/application that runs on SQL Server that will
> allow me to do some sort of process billing? Used to be quite common in
the
> old days, to bill back users for their usage. Since I have a hosted
> application, I want to bill for CPU usage.
> I know that I can use SQL Profiler, but was hoping for an agent or service
> that would allow me to bill based on DB or User.
>
allow me to do some sort of process billing? Used to be quite common in the
old days, to bill back users for their usage. Since I have a hosted
application, I want to bill for CPU usage.
I know that I can use SQL Profiler, but was hoping for an agent or service
that would allow me to bill based on DB or User.I would set up a server side trace that logged the the events that you need
to a sql server table. Here is an article I wrote on the subject that
might help you get started with server side tracing:
http://www.dbazine.com/larsen6.shtml
--
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23M5QpgH3EHA.1524@.TK2MSFTNGP09.phx.gbl...
> Does anyone know of an agent/application that runs on SQL Server that will
> allow me to do some sort of process billing? Used to be quite common in
the
> old days, to bill back users for their usage. Since I have a hosted
> application, I want to bill for CPU usage.
> I know that I can use SQL Profiler, but was hoping for an agent or service
> that would allow me to bill based on DB or User.
>
Application
Does anyone know of an agent/application that runs on SQL Server that will
allow me to do some sort of process billing? Used to be quite common in the
old days, to bill back users for their usage. Since I have a hosted
application, I want to bill for CPU usage.
I know that I can use SQL Profiler, but was hoping for an agent or service
that would allow me to bill based on DB or User.
I would set up a server side trace that logged the the events that you need
to a sql server table. Here is an article I wrote on the subject that
might help you get started with server side tracing:
http://www.dbazine.com/larsen6.shtml
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23M5QpgH3EHA.1524@.TK2MSFTNGP09.phx.gbl...
> Does anyone know of an agent/application that runs on SQL Server that will
> allow me to do some sort of process billing? Used to be quite common in
the
> old days, to bill back users for their usage. Since I have a hosted
> application, I want to bill for CPU usage.
> I know that I can use SQL Profiler, but was hoping for an agent or service
> that would allow me to bill based on DB or User.
>
allow me to do some sort of process billing? Used to be quite common in the
old days, to bill back users for their usage. Since I have a hosted
application, I want to bill for CPU usage.
I know that I can use SQL Profiler, but was hoping for an agent or service
that would allow me to bill based on DB or User.
I would set up a server side trace that logged the the events that you need
to a sql server table. Here is an article I wrote on the subject that
might help you get started with server side tracing:
http://www.dbazine.com/larsen6.shtml
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23M5QpgH3EHA.1524@.TK2MSFTNGP09.phx.gbl...
> Does anyone know of an agent/application that runs on SQL Server that will
> allow me to do some sort of process billing? Used to be quite common in
the
> old days, to bill back users for their usage. Since I have a hosted
> application, I want to bill for CPU usage.
> I know that I can use SQL Profiler, but was hoping for an agent or service
> that would allow me to bill based on DB or User.
>
Thursday, February 9, 2012
Anything wrong with the connection?
Dear all,
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
Ivan
On Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:
> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL server
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
Rudi Bruchez
MCDBA
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
Ivan
On Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:
> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL server
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
Rudi Bruchez
MCDBA
Anything wrong with the connection?
Dear all,
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
IvanOn Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:
> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;Use
r
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL serve
r
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
Rudi Bruchez
MCDBA
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
IvanOn Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:
> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;Use
r
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL serve
r
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
Rudi Bruchez
MCDBA
Anything wrong with the connection?
Dear all,
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
IvanOn Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:
> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL server
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
--
Rudi Bruchez
MCDBA
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
IvanOn Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:
> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL server
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
--
Rudi Bruchez
MCDBA
Subscribe to:
Posts (Atom)