What's the use of these strage statements in a reload.sql script for a SQL Remote database:

CREATE PUBLICATION dummy_pub_1( TABLE dbo.RowGenerator )
go
DROP PUBLICATION dummy_pub_1
go

CREATE PUBLICATION dummy_pub_2( TABLE dbo.RowGenerator )
go
DROP PUBLICATION dummy_pub_2
go

CREATE PUBLICATION "dbo"."PUB_ArtTabellen" 
(

Are these dummy publications just created to assure that the real publications have the same publication_ids as in the original database?

asked 21 Sep '10, 16:35

Volker%20Barth's gravatar image

Volker Barth
40.1k361549819
accept rate: 34%


Yes, that is exactly the reason. Publication id's can be recorded in the transaction log. Preserving the id's allows logs created prior to the database rebuild to be accessed by SQL Remote without compatibility issues. Otherwise all remote databases would need to be sync'ed before the rebuild (unlikely), or those not synced would need to be re-extracted after the rebuild.

permanent link

answered 22 Sep '10, 13:10

Bruce%20Hay's gravatar image

Bruce Hay
2.6k1510
accept rate: 48%

Well, that's reason enough...thanks for the clarification. I guess the same background applies to the "GRANT CONNECT ... AT n" statements to assure remote users have the same user IDs as before?

(22 Sep '10, 13:27) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×103
×52
×19
×17

question asked: 21 Sep '10, 16:35

question was seen: 2,380 times

last updated: 22 Sep '10, 13:10