Hi All
I wasn't aware of the security feature of MSDE, whereby it doesn't allow the
TCP/IP(?) network protocol to work and allow a networked PC to connect to an
SQL DB running on a MSDE installation on another PC. It only allows the
'host' PC to connect to the SQL DB.
I've sussed this in my MSDE installer so that it enables the network feature
when it installs, but I have a user who already has MSDE installed and
running with the protocol disabled and now that they are in the process of
connecting and using a 2nd PC I don't want to ask them to detach their db,
re-install MSDE with the right flag and then re-attach their db, as our
relationship is strained as it is.
Is there anyway to re-set/patch this flag on an installed version?
Thanks
Robbie
hi Robbie,
Astra wrote:
>..
> I've sussed this in my MSDE installer so that it enables the network
> feature when it installs, but I have a user who already has MSDE
> installed and running with the protocol disabled and now that they
> are in the process of connecting and using a 2nd PC I don't want to
> ask them to detach their db, re-install MSDE with the right flag and
> then re-attach their db, as our relationship is strained as it is.
> Is there anyway to re-set/patch this flag on an installed version?
please have a look at
http://support.microsoft.com/default...b;en-us;285097 in the part
regarding the Windows registry modification..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Showing posts with label whereby. Show all posts
Showing posts with label whereby. Show all posts
Friday, March 23, 2012
Saturday, February 25, 2012
msdb recreate cause replication problems
We just went through a nasty experience whereby we had to recreate the
MSDB database.
System is now back, but replication is completely messed up. Is there a
way to get all the MS* tables back, in the MSDB? I tried to de-install
and install Replication, but that doesn't seem to generate all the
required tables and procs
SQL2005, SP1.
Any help much appreciated!
I take it you mean you want your jobs to pick up where they left off.
Dropping and recreating the publications and subscriptions should do that.
If you mean the replication table in msdb, they are created there when you
install sql server.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<renedevries@.gmail.com> wrote in message
news:1159994716.013545.158270@.i3g2000cwc.googlegro ups.com...
> We just went through a nasty experience whereby we had to recreate the
> MSDB database.
> System is now back, but replication is completely messed up. Is there a
> way to get all the MS* tables back, in the MSDB? I tried to de-install
> and install Replication, but that doesn't seem to generate all the
> required tables and procs
> SQL2005, SP1.
> Any help much appreciated!
>
|||Eventually called MS Tech Support. The goal was to het replication
working at all, never mind the jobs or the previous state. But since
all relevant tables in msdb where gone, the whole thing was in limbo
The only REAL option is indeed a fresh install of SQL. However, they
where able to help me out, though a number of steps which involved
removing repliation from the database, dropping the distribution db,
and some other assorted trickery. But eventually we got it to work.
Turns out that if you re-create the distribution database all the
associated msdb tables and jobs are also recreated. Fortunately ;)
Lesson: make sure you keep good, validated backups of msdb at all
times. Bitten once again
Rene
Hilary Cotter schreef:
> I take it you mean you want your jobs to pick up where they left off.
> Dropping and recreating the publications and subscriptions should do that.
> If you mean the replication table in msdb, they are created there when you
> install sql server.
> --
MSDB database.
System is now back, but replication is completely messed up. Is there a
way to get all the MS* tables back, in the MSDB? I tried to de-install
and install Replication, but that doesn't seem to generate all the
required tables and procs
SQL2005, SP1.
Any help much appreciated!
I take it you mean you want your jobs to pick up where they left off.
Dropping and recreating the publications and subscriptions should do that.
If you mean the replication table in msdb, they are created there when you
install sql server.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<renedevries@.gmail.com> wrote in message
news:1159994716.013545.158270@.i3g2000cwc.googlegro ups.com...
> We just went through a nasty experience whereby we had to recreate the
> MSDB database.
> System is now back, but replication is completely messed up. Is there a
> way to get all the MS* tables back, in the MSDB? I tried to de-install
> and install Replication, but that doesn't seem to generate all the
> required tables and procs
> SQL2005, SP1.
> Any help much appreciated!
>
|||Eventually called MS Tech Support. The goal was to het replication
working at all, never mind the jobs or the previous state. But since
all relevant tables in msdb where gone, the whole thing was in limbo
The only REAL option is indeed a fresh install of SQL. However, they
where able to help me out, though a number of steps which involved
removing repliation from the database, dropping the distribution db,
and some other assorted trickery. But eventually we got it to work.
Turns out that if you re-create the distribution database all the
associated msdb tables and jobs are also recreated. Fortunately ;)
Lesson: make sure you keep good, validated backups of msdb at all
times. Bitten once again
Rene
Hilary Cotter schreef:
> I take it you mean you want your jobs to pick up where they left off.
> Dropping and recreating the publications and subscriptions should do that.
> If you mean the replication table in msdb, they are created there when you
> install sql server.
> --
Subscribe to:
Posts (Atom)