New to replication please help

Hi

I am new to this topic.i am trying to create a publisher in sql server 2005

here is what i do..

sql server studio->replication->local publisher->New publication

I get this error mesage

"Microsoft sql server management studio is unable to access replication components because replication is not installed on this instance of sql server

Additional information:Execute permission denied on object sp_MS_replication_installed database:master,owner:dbo"

I have installed sql server again but it show me the same error.

please anyone let me know.

To install here are the steps which i followed.

To install replication components, including Replication Management Objects (RMO), select SQL Server Database Services on the Components to Install page of the Installation Wizard.
To install replication components:

On the Components to Install page of the SQL Server Installation Wizard, click Advanced.

On the Feature Selection page, expand Database Services.

Click Replication, and then click Entire feature will be installed on local hard drive.

After this a screen pops up saying Database Services on the Components installed.

there is a button at the bottom called details when clicked shows up with the message below.

Name: Microsoft SQL Server 2000
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

I have no idea what does this message means.

please let me know

|||It means you're trying to upgrade, but cannot due to requriements that you haven't met. Read the books online topics for more information.

New to replication please help

Hi

I am new to this topic.i am trying to create a publisher in sql server 2005

here is what i do..

sql server studio->replication->local publisher->New publication

I get this error mesage

"Microsoft sql server management studio is unable to access replication components because replication is not installed on this instance of sql server

Additional information:Execute permission denied on object sp_MS_replication_installed database:master,owner:dbo"

I have installed sql server again but it show me the same error.

please anyone let me know.

To install here are the steps which i followed.

To install replication components, including Replication Management Objects (RMO), select SQL Server Database Services on the Components to Install page of the Installation Wizard.
To install replication components:

On the Components to Install page of the SQL Server Installation Wizard, click Advanced.

On the Feature Selection page, expand Database Services.

Click Replication, and then click Entire feature will be installed on local hard drive.

After this a screen pops up saying Database Services on the Components installed.

there is a button at the bottom called details when clicked shows up with the message below.

Name: Microsoft SQL Server 2000
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

I have no idea what does this message means.

please let me know

|||It means you're trying to upgrade, but cannot due to requriements that you haven't met. Read the books online topics for more information.

New to Replication

I am new to replication. Please forgive me if this sounds silly.
I have one publisher and several subscriber, all in different locations. In
case of emergency and I have to shut down the publisher, I want to use the
one of the subscribers to process our business, and I want to turn this
subscriber to a new publisher. Is this possible? What kind of replication
should I use?
Its not really possible in SQL 2000, but it looks like the peer-to-peer
replication model in 2005.
You have to look at how the data flows. If it flows only from the publisher
to the subscribers it might be possible to convert a subscriber to a
publisher by applying the publication creation script on one of the
subscribers you wish to promote the new publisher. Then make all other
subscribers subscribers of this new publisher.
Hilary Cotter
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
"Wind" <Wind@.discussions.microsoft.com> wrote in message
news:4AF7A0BF-DB5F-43E8-BD2C-D7F1EE5E6098@.microsoft.com...
> I am new to replication. Please forgive me if this sounds silly.
> I have one publisher and several subscriber, all in different locations.
In
> case of emergency and I have to shut down the publisher, I want to use the
> one of the subscribers to process our business, and I want to turn this
> subscriber to a new publisher. Is this possible? What kind of replication
> should I use?
|||Thanks a lot for your reply.
Do you mean that if I am in SQL 2000, and the subscribers only read data,
not write, I should be able to turn one subscriber to a publisher? Actually,
what I want to do is, when the publisher has to be shut down (or damaged), I
will still have the full database for business continuity in another
location. This can be a kind of emergency backup system.
"Hilary Cotter" wrote:

> Its not really possible in SQL 2000, but it looks like the peer-to-peer
> replication model in 2005.
> You have to look at how the data flows. If it flows only from the publisher
> to the subscribers it might be possible to convert a subscriber to a
> publisher by applying the publication creation script on one of the
> subscribers you wish to promote the new publisher. Then make all other
> subscribers subscribers of this new publisher.
> --
> Hilary Cotter
> 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
> "Wind" <Wind@.discussions.microsoft.com> wrote in message
> news:4AF7A0BF-DB5F-43E8-BD2C-D7F1EE5E6098@.microsoft.com...
> In
>
>
|||Yes you can do this, but its difficult. Basically you have to prep your
database on the subscriber.
IIRC you have to do the following
1) backup the publisher
2) restore it on the subscriber
3) change all identity columns to NFR
4) change all triggers to NFR
5) change all constraints to NFR
You may need to run DBCC checkident ('tableName', reseed,X) on some of the
subscriber tables to fix the identity property on the restored databases,
don't use the set identity_insert 'tableName', off in the insert procs
Hilary Cotter
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
"Wind" <Wind@.discussions.microsoft.com> wrote in message
news:346FA462-5CD1-4156-BC06-E6B0662E4BFF@.microsoft.com...[vbcol=seagreen]
> Thanks a lot for your reply.
> Do you mean that if I am in SQL 2000, and the subscribers only read data,
> not write, I should be able to turn one subscriber to a publisher?
> Actually,
> what I want to do is, when the publisher has to be shut down (or damaged),
> I
> will still have the full database for business continuity in another
> location. This can be a kind of emergency backup system.
> "Hilary Cotter" wrote:
|||What about the alternate synchronization partner?
Jos.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23zmkjND0FHA.2960@.tk2msftngp13.phx.gbl...
> Its not really possible in SQL 2000, but it looks like the peer-to-peer
> replication model in 2005.
> You have to look at how the data flows. If it flows only from the
publisher[vbcol=seagreen]
> to the subscribers it might be possible to convert a subscriber to a
> publisher by applying the publication creation script on one of the
> subscribers you wish to promote the new publisher. Then make all other
> subscribers subscribers of this new publisher.
> --
> Hilary Cotter
> 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
> "Wind" <Wind@.discussions.microsoft.com> wrote in message
> news:4AF7A0BF-DB5F-43E8-BD2C-D7F1EE5E6098@.microsoft.com...
> In
the[vbcol=seagreen]
replication
>
|||Plain merge and queued updating subscribers would also come into this
section, although none of these techniques would really allow the subscriber
to easily become the publisher.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

New records were not replicated on publisher and subscriber

I have seen this happen in 2 circumstances:
(1) Firstly when the filter was set to 1=2 and inserts
were made while the merge agent was running
(2) If you bulk insert the rows and choose the defaults,
then FIRE_TRIGGERS is false and consequently the rows are
not added to MSmerge_contents.
In either case, you need to run sp_addtabletocontents to
include the rows then resynchronise. Alternatively you
can use sp_mergedummyupdate for a single row.
rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul,
Thanks for the answer, I would give it a try.
Hope it will solve my problem.
Thanks again, and more power.
Roland
"Paul Ibison" wrote:

> I have seen this happen in 2 circumstances:
> (1) Firstly when the filter was set to 1=2 and inserts
> were made while the merge agent was running
> (2) If you bulk insert the rows and choose the defaults,
> then FIRE_TRIGGERS is false and consequently the rows are
> not added to MSmerge_contents.
> In either case, you need to run sp_addtabletocontents to
> include the rows then resynchronise. Alternatively you
> can use sp_mergedummyupdate for a single row.
> rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

New Publication Error

Hi All,
A couple of months ago, I setup a transactional replication between 2
servers. In the last week, the publisher stopped replicating to the
subscriber for some unknown reason. When I was troubleshooting the problem,
I tried to add a new publication and I received the error attached in the
screenshot.
I ran the DBCC CHECKDB on that DB and the results were ok.
Any help would be greatly appreciated.
Regards,
JN
Can't see the screenshot using the web interface to the newsgroup. Can you
post up the error message for us...
Cheers,
Paul Ibison
|||Sure thing...Error as follows:
"New Publication Wizard encountered one or more errors while retrieving the
list of databases on the 'servername'. The list of databases may not be
complete.
Additional Information:
An exception occured while executing a T-SQL statement or batch
(Microsoft.SqlServer.ConnectionInfo)
The operating system returned error 21 (The device is not ready) to SQL
server during a read at offset 0x000000614d2000 in
file F:\TST\TSTDAT.mdf (not sure what this DB is?). Addtional messages
in the SQL Server error log and system event log my provide more detail.
This is a severe system level error condition that threatens database
integrity and must be corrected
immediatly. Complete a full database consistency check (DBCC CHECKDB).
This error can be caused by many factors; for
more information, SQL Server Books Online (MS SQL Error: 823)"
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:D538F184-0AC3-4CD2-AC4D-0029B4E0ED7E@.microsoft.com...
> Can't see the screenshot using the web interface to the newsgroup. Can you
> post up the error message for us...
> Cheers,
> Paul Ibison
>
|||I'd look to see what database the file F:\TST\TSTDAT.mdf corresponds to, then
run DBCC CHECKDB on this database. The info should be in sysaltfiles.
HTH,
Paul Ibison