I've got this SQL2K/WIN2K setup and a database having merge replication
setup. It's been running there for more than couple of years. Now due to
strategic changes we don't need this replication on the database.
When I tried to remove it, it started blocking normal user activity that is
mostly on the same tables which are published. After 15-20 minutes I had to
cancle it. The database is serving 24/7 and I want to remove replication with
minimal disruption to regular opration. Is there any easier way to remove
replication and metadata generated by it.?
I would appreciate any help/pointers.
Have you tried to call sp_removedbreplication? This proc should remove the
replication from the database.
Yi
"adi" <adi@.discussions.microsoft.com> wrote in message
news:7B04463C-FFA2-4BEA-8339-EB3340FEE5A2@.microsoft.com...
> I've got this SQL2K/WIN2K setup and a database having merge replication
> setup. It's been running there for more than couple of years. Now due to
> strategic changes we don't need this replication on the database.
> When I tried to remove it, it started blocking normal user activity that
> is
> mostly on the same tables which are published. After 15-20 minutes I had
> to
> cancle it. The database is serving 24/7 and I want to remove replication
> with
> minimal disruption to regular opration. Is there any easier way to remove
> replication and metadata generated by it.?
> I would appreciate any help/pointers.
Showing posts with label win2k. Show all posts
Showing posts with label win2k. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
Remotely update database
Hi,
We have a SQL Server 2000 database on an Win2k server. I'd like to
offer the facility for our customers to add records to our database
from their programs. They just want to make one function call to
create a new record on our database.
This call would return a success or failure code number.
They are not (currently) connected to our system. I had felt that a
VPN would be the best method, but am open to alternative suggestions.
Their programs run on about 100 PC's on their lan, so I figured I'd
need to write a DLL for their server which is constantly connected to
our server, then their function call would invoke a function within
this DLL. For this I'd be using VB6 (sorry, not upgraded to .NET yet).
The idea being that we would then only have one connection to our
server rather than 100.
Security is a key concern - I don't really want to provide their
programmers with the logins to our system, just a compiled DLL that
does it for them.
Do you think this is a workable plan? What would be better?
TIA
PhilHow about creating a Web Service that their programs can access. Then you
don't need a VPN at all.
Andrew J. Kelly SQL MVP
"RS200Phil" <philsowden@.dataservicesltd.co.uk> wrote in message
news:1143819451.670277.13120@.e56g2000cwe.googlegroups.com...
> Hi,
> We have a SQL Server 2000 database on an Win2k server. I'd like to
> offer the facility for our customers to add records to our database
> from their programs. They just want to make one function call to
> create a new record on our database.
> This call would return a success or failure code number.
> They are not (currently) connected to our system. I had felt that a
> VPN would be the best method, but am open to alternative suggestions.
> Their programs run on about 100 PC's on their lan, so I figured I'd
> need to write a DLL for their server which is constantly connected to
> our server, then their function call would invoke a function within
> this DLL. For this I'd be using VB6 (sorry, not upgraded to .NET yet).
> The idea being that we would then only have one connection to our
> server rather than 100.
> Security is a key concern - I don't really want to provide their
> programmers with the logins to our system, just a compiled DLL that
> does it for them.
> Do you think this is a workable plan? What would be better?
> TIA
> Phil
>|||Sounds like a brilliant solution, thanks, Andrew. Please excuse my
ignorance - where would I look for information on how to develop and
implement a web service?
I'm not afraid to get my hands dirty or read manuals. I develop
primarily in ASP and VB.
Cheers
Phil|||I think you would want .Net for this, in which case the tools do 90 percent
of the codign for you. All you need to do is write a single function that
takes parameters and .Net will code the interface. Then you could write a
DLL that would access the web service (again, .net does all the work) which
could run from their desktops or a webserver in their domain. You can do it
without .Net, it is just a lot more work.
However, they still need to be able to access your web server, on your
network, and you still need to make sure that random people on the internet
cannot access your server. So you need to have some security built in to
control access.
"RS200Phil" <philsowden@.dataservicesltd.co.uk> wrote in message
news:1143840697.760335.245570@.t31g2000cwb.googlegroups.com...
> Sounds like a brilliant solution, thanks, Andrew. Please excuse my
> ignorance - where would I look for information on how to develop and
> implement a web service?
> I'm not afraid to get my hands dirty or read manuals. I develop
> primarily in ASP and VB.
> Cheers
> Phil
>|||http://www.google.com/search?hl=en&...vice+sql+server
Andrew J. Kelly SQL MVP
"RS200Phil" <philsowden@.dataservicesltd.co.uk> wrote in message
news:1143840697.760335.245570@.t31g2000cwb.googlegroups.com...
> Sounds like a brilliant solution, thanks, Andrew. Please excuse my
> ignorance - where would I look for information on how to develop and
> implement a web service?
> I'm not afraid to get my hands dirty or read manuals. I develop
> primarily in ASP and VB.
> Cheers
> Phil
>
We have a SQL Server 2000 database on an Win2k server. I'd like to
offer the facility for our customers to add records to our database
from their programs. They just want to make one function call to
create a new record on our database.
This call would return a success or failure code number.
They are not (currently) connected to our system. I had felt that a
VPN would be the best method, but am open to alternative suggestions.
Their programs run on about 100 PC's on their lan, so I figured I'd
need to write a DLL for their server which is constantly connected to
our server, then their function call would invoke a function within
this DLL. For this I'd be using VB6 (sorry, not upgraded to .NET yet).
The idea being that we would then only have one connection to our
server rather than 100.
Security is a key concern - I don't really want to provide their
programmers with the logins to our system, just a compiled DLL that
does it for them.
Do you think this is a workable plan? What would be better?
TIA
PhilHow about creating a Web Service that their programs can access. Then you
don't need a VPN at all.
Andrew J. Kelly SQL MVP
"RS200Phil" <philsowden@.dataservicesltd.co.uk> wrote in message
news:1143819451.670277.13120@.e56g2000cwe.googlegroups.com...
> Hi,
> We have a SQL Server 2000 database on an Win2k server. I'd like to
> offer the facility for our customers to add records to our database
> from their programs. They just want to make one function call to
> create a new record on our database.
> This call would return a success or failure code number.
> They are not (currently) connected to our system. I had felt that a
> VPN would be the best method, but am open to alternative suggestions.
> Their programs run on about 100 PC's on their lan, so I figured I'd
> need to write a DLL for their server which is constantly connected to
> our server, then their function call would invoke a function within
> this DLL. For this I'd be using VB6 (sorry, not upgraded to .NET yet).
> The idea being that we would then only have one connection to our
> server rather than 100.
> Security is a key concern - I don't really want to provide their
> programmers with the logins to our system, just a compiled DLL that
> does it for them.
> Do you think this is a workable plan? What would be better?
> TIA
> Phil
>|||Sounds like a brilliant solution, thanks, Andrew. Please excuse my
ignorance - where would I look for information on how to develop and
implement a web service?
I'm not afraid to get my hands dirty or read manuals. I develop
primarily in ASP and VB.
Cheers
Phil|||I think you would want .Net for this, in which case the tools do 90 percent
of the codign for you. All you need to do is write a single function that
takes parameters and .Net will code the interface. Then you could write a
DLL that would access the web service (again, .net does all the work) which
could run from their desktops or a webserver in their domain. You can do it
without .Net, it is just a lot more work.
However, they still need to be able to access your web server, on your
network, and you still need to make sure that random people on the internet
cannot access your server. So you need to have some security built in to
control access.
"RS200Phil" <philsowden@.dataservicesltd.co.uk> wrote in message
news:1143840697.760335.245570@.t31g2000cwb.googlegroups.com...
> Sounds like a brilliant solution, thanks, Andrew. Please excuse my
> ignorance - where would I look for information on how to develop and
> implement a web service?
> I'm not afraid to get my hands dirty or read manuals. I develop
> primarily in ASP and VB.
> Cheers
> Phil
>|||http://www.google.com/search?hl=en&...vice+sql+server
Andrew J. Kelly SQL MVP
"RS200Phil" <philsowden@.dataservicesltd.co.uk> wrote in message
news:1143840697.760335.245570@.t31g2000cwb.googlegroups.com...
> Sounds like a brilliant solution, thanks, Andrew. Please excuse my
> ignorance - where would I look for information on how to develop and
> implement a web service?
> I'm not afraid to get my hands dirty or read manuals. I develop
> primarily in ASP and VB.
> Cheers
> Phil
>
Tuesday, March 20, 2012
Remote Server Login
As a Sys Admin, I was wondering - if I have admin rights to a Win2k machine
that is hosting SQL Server 2000, do I have the ability using any
command-line tools such as OSQL or ISQL (that can be accessed remotely) to
add, delete, or change accounts
registered in SQL Server for the various databases if I don't have access to
a specific account within SQL Server?
I ask, because the question that came up was - what if we have a DBA leave
under less than amicable circumstances? Could I, someone who has admin
rights on the machine, be able to log into that machine remotely and somehow
via command line (I don't maintain active SQL clients centrally), change the
SA password, remove an account, and/or add an account with sysadmin rights,
etc?
Thanks in advance for any help -IF that person continues to have a valid login to SQL Server with
administrative priveleges, then he can do anything via OSQL he can do via
Query Analyzer or SQL Enterprise Manager..
So when someone leaves, we delete their login ( in SQL and/or Windows )
immediately and they can do us no harm..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"ScottT" <jbell@.vitria.com> wrote in message
news:10ddv86i6ng5e47@.news.supernews.com...
> As a Sys Admin, I was wondering - if I have admin rights to a Win2k
machine
> that is hosting SQL Server 2000, do I have the ability using any
> command-line tools such as OSQL or ISQL (that can be accessed remotely) to
> add, delete, or change accounts
> registered in SQL Server for the various databases if I don't have access
to
> a specific account within SQL Server?
> I ask, because the question that came up was - what if we have a DBA leave
> under less than amicable circumstances? Could I, someone who has admin
> rights on the machine, be able to log into that machine remotely and
somehow
> via command line (I don't maintain active SQL clients centrally), change
the
> SA password, remove an account, and/or add an account with sysadmin
rights,
> etc?
> Thanks in advance for any help -
>
that is hosting SQL Server 2000, do I have the ability using any
command-line tools such as OSQL or ISQL (that can be accessed remotely) to
add, delete, or change accounts
registered in SQL Server for the various databases if I don't have access to
a specific account within SQL Server?
I ask, because the question that came up was - what if we have a DBA leave
under less than amicable circumstances? Could I, someone who has admin
rights on the machine, be able to log into that machine remotely and somehow
via command line (I don't maintain active SQL clients centrally), change the
SA password, remove an account, and/or add an account with sysadmin rights,
etc?
Thanks in advance for any help -IF that person continues to have a valid login to SQL Server with
administrative priveleges, then he can do anything via OSQL he can do via
Query Analyzer or SQL Enterprise Manager..
So when someone leaves, we delete their login ( in SQL and/or Windows )
immediately and they can do us no harm..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"ScottT" <jbell@.vitria.com> wrote in message
news:10ddv86i6ng5e47@.news.supernews.com...
> As a Sys Admin, I was wondering - if I have admin rights to a Win2k
machine
> that is hosting SQL Server 2000, do I have the ability using any
> command-line tools such as OSQL or ISQL (that can be accessed remotely) to
> add, delete, or change accounts
> registered in SQL Server for the various databases if I don't have access
to
> a specific account within SQL Server?
> I ask, because the question that came up was - what if we have a DBA leave
> under less than amicable circumstances? Could I, someone who has admin
> rights on the machine, be able to log into that machine remotely and
somehow
> via command line (I don't maintain active SQL clients centrally), change
the
> SA password, remove an account, and/or add an account with sysadmin
rights,
> etc?
> Thanks in advance for any help -
>
Remote Server Login
As a Sys Admin, I was wondering - if I have admin rights to a Win2k machine
that is hosting SQL Server 2000, do I have the ability using any
command-line tools such as OSQL or ISQL (that can be accessed remotely) to
add, delete, or change accounts
registered in SQL Server for the various databases if I don't have access to
a specific account within SQL Server?
I ask, because the question that came up was - what if we have a DBA leave
under less than amicable circumstances? Could I, someone who has admin
rights on the machine, be able to log into that machine remotely and somehow
via command line (I don't maintain active SQL clients centrally), change the
SA password, remove an account, and/or add an account with sysadmin rights,
etc?
Thanks in advance for any help -IF that person continues to have a valid login to SQL Server with
administrative priveleges, then he can do anything via OSQL he can do via
Query Analyzer or SQL Enterprise Manager..
So when someone leaves, we delete their login ( in SQL and/or Windows )
immediately and they can do us no harm..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"ScottT" <jbell@.vitria.com> wrote in message
news:10ddv86i6ng5e47@.news.supernews.com...
> As a Sys Admin, I was wondering - if I have admin rights to a Win2k
machine
> that is hosting SQL Server 2000, do I have the ability using any
> command-line tools such as OSQL or ISQL (that can be accessed remotely) to
> add, delete, or change accounts
> registered in SQL Server for the various databases if I don't have access
to
> a specific account within SQL Server?
> I ask, because the question that came up was - what if we have a DBA leave
> under less than amicable circumstances? Could I, someone who has admin
> rights on the machine, be able to log into that machine remotely and
somehow
> via command line (I don't maintain active SQL clients centrally), change
the
> SA password, remove an account, and/or add an account with sysadmin
rights,
> etc?
> Thanks in advance for any help -
>
that is hosting SQL Server 2000, do I have the ability using any
command-line tools such as OSQL or ISQL (that can be accessed remotely) to
add, delete, or change accounts
registered in SQL Server for the various databases if I don't have access to
a specific account within SQL Server?
I ask, because the question that came up was - what if we have a DBA leave
under less than amicable circumstances? Could I, someone who has admin
rights on the machine, be able to log into that machine remotely and somehow
via command line (I don't maintain active SQL clients centrally), change the
SA password, remove an account, and/or add an account with sysadmin rights,
etc?
Thanks in advance for any help -IF that person continues to have a valid login to SQL Server with
administrative priveleges, then he can do anything via OSQL he can do via
Query Analyzer or SQL Enterprise Manager..
So when someone leaves, we delete their login ( in SQL and/or Windows )
immediately and they can do us no harm..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"ScottT" <jbell@.vitria.com> wrote in message
news:10ddv86i6ng5e47@.news.supernews.com...
> As a Sys Admin, I was wondering - if I have admin rights to a Win2k
machine
> that is hosting SQL Server 2000, do I have the ability using any
> command-line tools such as OSQL or ISQL (that can be accessed remotely) to
> add, delete, or change accounts
> registered in SQL Server for the various databases if I don't have access
to
> a specific account within SQL Server?
> I ask, because the question that came up was - what if we have a DBA leave
> under less than amicable circumstances? Could I, someone who has admin
> rights on the machine, be able to log into that machine remotely and
somehow
> via command line (I don't maintain active SQL clients centrally), change
the
> SA password, remove an account, and/or add an account with sysadmin
rights,
> etc?
> Thanks in advance for any help -
>
Remote Server Login
As a Sys Admin, I was wondering - if I have admin rights to a Win2k machine
that is hosting SQL Server 2000, do I have the ability using any
command-line tools such as OSQL or ISQL (that can be accessed remotely) to
add, delete, or change accounts
registered in SQL Server for the various databases if I don't have access to
a specific account within SQL Server?
I ask, because the question that came up was - what if we have a DBA leave
under less than amicable circumstances? Could I, someone who has admin
rights on the machine, be able to log into that machine remotely and somehow
via command line (I don't maintain active SQL clients centrally), change the
SA password, remove an account, and/or add an account with sysadmin rights,
etc?
Thanks in advance for any help -
IF that person continues to have a valid login to SQL Server with
administrative priveleges, then he can do anything via OSQL he can do via
Query Analyzer or SQL Enterprise Manager..
So when someone leaves, we delete their login ( in SQL and/or Windows )
immediately and they can do us no harm..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"ScottT" <jbell@.vitria.com> wrote in message
news:10ddv86i6ng5e47@.news.supernews.com...
> As a Sys Admin, I was wondering - if I have admin rights to a Win2k
machine
> that is hosting SQL Server 2000, do I have the ability using any
> command-line tools such as OSQL or ISQL (that can be accessed remotely) to
> add, delete, or change accounts
> registered in SQL Server for the various databases if I don't have access
to
> a specific account within SQL Server?
> I ask, because the question that came up was - what if we have a DBA leave
> under less than amicable circumstances? Could I, someone who has admin
> rights on the machine, be able to log into that machine remotely and
somehow
> via command line (I don't maintain active SQL clients centrally), change
the
> SA password, remove an account, and/or add an account with sysadmin
rights,
> etc?
> Thanks in advance for any help -
>
that is hosting SQL Server 2000, do I have the ability using any
command-line tools such as OSQL or ISQL (that can be accessed remotely) to
add, delete, or change accounts
registered in SQL Server for the various databases if I don't have access to
a specific account within SQL Server?
I ask, because the question that came up was - what if we have a DBA leave
under less than amicable circumstances? Could I, someone who has admin
rights on the machine, be able to log into that machine remotely and somehow
via command line (I don't maintain active SQL clients centrally), change the
SA password, remove an account, and/or add an account with sysadmin rights,
etc?
Thanks in advance for any help -
IF that person continues to have a valid login to SQL Server with
administrative priveleges, then he can do anything via OSQL he can do via
Query Analyzer or SQL Enterprise Manager..
So when someone leaves, we delete their login ( in SQL and/or Windows )
immediately and they can do us no harm..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"ScottT" <jbell@.vitria.com> wrote in message
news:10ddv86i6ng5e47@.news.supernews.com...
> As a Sys Admin, I was wondering - if I have admin rights to a Win2k
machine
> that is hosting SQL Server 2000, do I have the ability using any
> command-line tools such as OSQL or ISQL (that can be accessed remotely) to
> add, delete, or change accounts
> registered in SQL Server for the various databases if I don't have access
to
> a specific account within SQL Server?
> I ask, because the question that came up was - what if we have a DBA leave
> under less than amicable circumstances? Could I, someone who has admin
> rights on the machine, be able to log into that machine remotely and
somehow
> via command line (I don't maintain active SQL clients centrally), change
the
> SA password, remove an account, and/or add an account with sysadmin
rights,
> etc?
> Thanks in advance for any help -
>
Subscribe to:
Posts (Atom)