Viewing 15 posts - 91 through 105 (of 109 total)
Just curious - what was the outcome of this issue?
ChrisB
November 16, 2005 at 7:09 pm
You can setup a manual version of SQL Server log shipping, even with Standard Edition. Perform tran log backup at production server, ftp or copy backup device to standby server,...
November 16, 2005 at 6:59 pm
Yes - you will have no problems adding or deleting indexes to replicated tables.
ChrisB MCDBA OCP MyDatabaseAdmin.com
November 16, 2005 at 6:54 pm
Execute a CREATE TABLE script at the subscriber to create tables exactly how they exist in production.
On the Snapshot tab for each article, select 'Delete all data in the existing...
November 10, 2005 at 5:28 pm
I am assuming you are doing this at the publisher.
You need to drop subscriptions, make change, add subscriptions. If you ddl script is changing the structure of the table, changing...
November 10, 2005 at 5:24 pm
You can setup your sproc to execute at shorter intervals, or have your SQL Server subscribe to a replicated copy of your Oracle table(s) - this is less resource intensive...
November 9, 2005 at 9:59 am
"Invalid" doesn't necessarily mean "does not exist". Take a look at your stored procedures that the distr agent calls:
sp_MSins_TableName / sp_MSupd_TableName / sp_MSdel_TableName
Try to execute yourself in Query Analyzer at...
November 9, 2005 at 9:53 am
In order to run ALTER TABLE script, you must drop your subscriptions. The script below also drops the article to allow for column adds/deletes/mods then re-creates pub article. This is...
November 7, 2005 at 11:14 am
Very good. There is a caveat with IDENTITY columns. You must comment out the update of the identity field in your sp_MS_upd_xxx stored procedures.
Make sure NOT FOR REPLICATION set for...
November 3, 2005 at 1:09 pm
One set of cost savings for your ROI calcs, are going from licensing for 6 instances of SQL to 2.
Beyond that I can't provide much insight other than -...
November 1, 2005 at 3:19 pm
Execute sp_scriptpublicationcustomprocs on the publisher, take the results and execute on the subscriber... I think that is the step you are missing.
Regards,
ChrisB MCDBA OCP MyDatabaseAdmin.com
October 31, 2005 at 3:16 pm
Can you ping the pub server from the distributor by servername?
Since you haven't even successfully ran the snapshot, try to rebuild the publication - then run snapshot again.
Regards,
ChrisB...
October 31, 2005 at 11:53 am
Never update system tables. Drop article from pub, then re-add specifying columns...
exec sp_dropsubscription @publication = 'MyPubName'
, @article = 'MyTable'
, @subscriber = 'SERVERNAME'
GO
exec...
October 31, 2005 at 11:46 am
Well that explains the snapshot performance. Many tables / not much data.
I would put all 500 tables in 1 publication to eliminate administrative overhead.
You will find all publications will...
October 28, 2005 at 4:11 pm
By the way - how big is your database (Mb or Gb) ? How long does it take to deliver snapshot?
Chris
October 28, 2005 at 2:36 pm
Viewing 15 posts - 91 through 105 (of 109 total)