Quantcast
Channel: SQLServerCentral » SQL Server 2005 » SS2K5 Replication » Latest topics
Viewing all 302 articles
Browse latest View live

sql server replicatoin requires actual server name to make a connection to the server

0
0
I have two servers at different locationIn both servers sql2005 is installed and have the same database instancesI wanted to create a replication between these two servers, one location has static ipiam able to connect to the remote server using the static ip, while in the replication, it is not accepting the ip, it is asking for the server name,how do i handle this situation.???sql server replicatoin requires actual server name to make a connection to the server, it is not accepting the alias name or ip address.help me out

Filter article for Snapshot and then remove

0
0
Hello all,I am setting up a transactional replication job between two servers and I am trying to find out if it is possible to filter my publication when I create the snapshot and then remove the filters without needing to re-initialize the subscription.My publisher has about 7 years worth of data in 6 large tables and I would like to filter these tables to 1 year of data for my initial snapshot so that it initializes quickly but then have subsequent transactions ignore the filter to optimize performance of the log reader agent. According to the documentation, if I remove the filter on the publication, the subscription must be re-initialized which defeats the purpose of what I am trying to do. Is there any way around this?

Setting up replication and dealing with a time lag

0
0
We have a replicated database (transactional replication) that is primarily used for reporting, although this also could be a secondary or tertiary (3rd option) disaster recovery solution if the other DR options fail. I inherited this situation, and it is not in ideal shape. A fair amount of the metadata has not been replicated from the production database, and it has proven to be more of a task than I thought to try to get this corrected. So, it would seem a good idea to just restore the replicated database from backup and then re-initiate replication. However, I am unsure of some things which will play into how I need to implement this.We are using SQL Server 2005. The size of the database is over 8GB.The full backup of the production database occurs shortly after midnight. The replicated database is at another site. It takes a couple of hours to get the backup compressed and moved across the wire to the server where the target instance resides. So, I'm unsure of how to deal with what happens during time it takes to get the backup file to the replicated server. We do take transaction log backups, so I assume I'll also need to get these transaction logs across the wire and restored as well while replication is down. I guess my question is at some point, a "last" transaction log needs to be taken, moved across the wire, restored and replication needs to be re-initiated before another database transaction occurs after this "last" transaction log was taken. I assume I'll need to take the production database offline briefly or perform the snapshot immediately upon completion of the transaction log in question.From all I've read, I know this is not an uncommon scenario, so is there an article or something I have missed that deals with the particular issues that I have concerns about? Perhaps this is not as complicated as I'm thinking it is. It really should be no different than initially setting up replication (there will always be at least a little time lag, right?), actually, but I just don't recall any articles addressing dealing with the time lag in setting up the replicated database (subscriber).Give me your thoughts and maybe you can fill in the gaps I have with my understanding.

Merge replication - some deletes not replicated

0
0
I'm currently testing a merge replication setup and I've discovered a problem with it. I ran a delete statement on two tables on my publisher and after running SQL Data Compare I found that some rows on both tables did not delete. There are no errors reported in the replication monitor. My question is, how can I troubleshoot further what went wrong here?

Merge Replication - How to start between Live databases without Drop object for FK

0
0
Hi,Just learned that SQL2012 do not support "transaction replication with update-able subscriber", But i believe the issue with merge replication will be the same in SQL2005 and above. So:Trying to setup merge replication between two live databases and both have same structure and same data for replication related objects but They do have different data in there related Foreign key tablesReason is because i am try to solve/avoide following error:[code="sql"]Error messages:The schema script 'DbTable1_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)Get help: http://help/MSSQL_REPL-2147201001[b]Could not drop object 'dbo.DbTable1' because it is referenced by a FOREIGN KEY constraint[/b]. (Source: MSSQLServer, Error number: 3726)Get help: http://help/3726[/code]So question is:How to start merge replication between two live database without a need to Drop and Re-create objects on subscriber? Is this really necessary OR can be avoided with any option?Note: I am trying to implement merge-replication as an alternative to "Transactional replication with update-able subscriber"Many Thanks.

Merge publication keeps bulk copying

0
0
The merge publication keeps bulk copying tables into the subscriber database. It will copy the data over to the subscriber from the snapshot. Once that's done, it begins copying data from the snapshot again, over and over which means the program that uses the subscriber database can't be launched. No data since the snapshot was created is being transferred.Does anyone know why this is happening? :crazy:It also shows this error:Error messages:The merge process was unable to access row metadata at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to write to, or use SQL Profiler to determine the source of the failure. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200996)Get help: http://help/MSSQL_REPL-2147200996Could not find stored procedure ''. (Source: MSSQLServer, Error number: 2812)Get help: http://help/2812Failed to get metadata for a batch of rows. (Source: MSSQLServer, Error number: 20680)Get help: http://help/20680The process was successfully stopped. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199481)

oracle golden gate slow reponse / lag observed during index rebuild job in sql 2008 r2

0
0
HiI want help if any one having oracle golden replication exeprience in SQL 2008 R2 edition. I have a source database Sql2008 R2 and targate database Oracle 11g using Oracle golde gate version 11.2.1.0.1 for data replication.It has been observed while index rebuild activity on source database oracle golden gate read the transaction log very slow. Observation is 1 record replicate in targate database with 3 minutes time.If any one having any experience for aboe slow replication please help

Getting error when setting up subscription

0
0

I get the following error when setting up subscription:

Creating Subscription(s)...

- Creating subscription for 'CISSW-YUKON04' (Warning)

Messages

Unable to set the Publisher login for the updatable subscription. You may have to set this up directly on the Subscriber machine using sp_link_publication. (New Subscription Wizard)------------------------------ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)------------------------------The security mode specified requires the server 'CISSW-YUKON03' in sysservers. Use sp_addlinkedserver to add the server.Changed database context to 'ReportServer'. (Microsoft SQL Server, Error: 20620)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=20620&LinkId=20476

any ideas?

thanks


view snapshot agent status

0
0
Hi, my problem is that when i m create new publication of database on ms sql server 2005, it is create success then i m "view snapshot agent status"after view minutes a message disaply," The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job step history message or Replication Monitor for more information. NOTE: The step was retried the requested number of times (10) with " .Please reply me urgently

Tran Repl - Placeholder implementation

0
0
Morning everyone,Running into an odd issue with a net setup of transactional replication. As part of setup, we are replicating (schema only) stored procedures and functions. In one of the stored procedures, I see the following message:[code="sql"]BEGIN-- This is a placeholder implementation of the schema object to facilitate deferred creation of the actual implementation.raiserror(N'This is a placeholder implementation of the schema object to facilitate deferred creation of the actual implementation.',16,-1)END[/code]This is not in the original stored procedure. More to the point, the above statement replaced the code in the stored procedure after replication. Going to the publisher, the proc certainly doesn't look like this.Does anyone have any idea what this is trying to tell me?Thanks,Fraggle

Merge Replication - Agent jobs maintaining data

0
0
I am just learning about replication, as I have been asked to set up a merge replication for one of our databases. Besides being completely overwhelmed by the whole thing :unsure: I do have a question that I cannot seem to find an answer for. The database I plan to set up replication for has several SQL Agent jobs that add/update/maintain the data within the tables. How are Agent jobs handled with merge replication? Are jobs on both the publisher and the subscriber, or do they run only on the publisher and then the data is updated when synchronization occurs? As a side note - I have learned lots from the Stairway to Replication by Sebastian Meine. Excellent reading – and for a newbie like me, written in language I can understand. Kudos to Sebastian!

Using oracle subscriber ---Questions

0
0
[b] Oracle treats both empty strings and NULL values as NULL. This is important if you define a SQL Server column as NOT NULL, and are replicating the column to an Oracle Subscriber. To avoid failures when applying changes to the Oracle Subscriber, you must do one of the following:[/b] o Ensure that empty strings are not inserted into the published table as column values. o Modify the generated create table script, removing the NOT NULL attribute from any character columns that may have associated empty strings, and supply the modified script as a custom create script for the article using the @creation_script parameter of sp_addarticle. [b]Which option is better from above two? I liked second option but want to know how ot run it or use it and when during replication process?[i][/i][/b][b]ALso Oracle Subscribers support a schema option of 0x4071. For more information about schema options, see sp_addarticle (Transact-SQL).[/b]What does this mean? does this mean that Oracle subscriber will not understand the create table scripts generated by SSMS when creating subscription.Ifi have to modify it to be able to run on oracle how do i do that?

Reinitialize subscription remove index from subscriber?

0
0
We reinitialized the subscription for a replication and noticed afterwards that an index the was created on the subscriber database was missing. This index isn't replicated from the publisher. Is this correct that an index created on a subscriber database will be removed when reinitialized? Thanks.

Trouble with log shipping. Reporting Server.

0
0
Hi,This is a new setup I'm trying to accomodate load.I have server A that is production server. I have server B which is the exact same DB on server A that will be used only for reporting. I have log shipping setup between server A and server B. Log shipping works ( I have DB B setup as standby/read only) - it works but if I run a query, then check my log shipping job I get the log shipping job error:"Exclusive access could not be obtained because database is in use"I need server B to be my report server, so I can't have it not complete the log shipping.What can I do? I need server A and server B to be in sync and be 'reportable'..

Subscription expire duration

0
0
Hi, I would like to know if I change the no of days in publication properties in General tab "Subscription expire and may be dropped if not synchronized in the following number of days. Replication meta data is kept for this amount of time". Will the subscription be reinitialised? If so how can I avoid reinitialising the subscriber when I change the number of days?Thanks in advanceAradhya

SQL 2005 Merge Replication and Sync Framework Toolkit operating parallel on SQL 2005 Server Database

0
0
Good Day,We have recently completed development of an iOS app that allows us to sync with a SQL 2005 Server which is currently running SQL Merge Replication. We successfully created the required tables to sync via the SQL Framework Toolkit however we are now experiencing issues syncing the data to the SQL Server due to Identity Range constraint violations. We created a column with type Unique Identifier for SQL Merge Replication years ago to prevent the creation of the rowguid column however the tables also contain Primary Key columns which are type Int.I have increased the Publisher's Identity range to allow for iOS uploads to consume the Identity Range however it does not resolve the issue. I have also executed the sp_adjustpublisheridentityrange command which has not yielded a solution.I would like to find out if anyone else has experienced this issue before and if they have been able to find a solution to this issue.

Advice about how to refresh a test database that is acting as a publisher, distributor, and subscriber (not replicating to other servers though)

0
0
I am hoping to get some guidance about setting up a weekly refresh of data from production to test. I want to use SSIS but I am open to whatever method makes sense with the following scenario: prod server one (database named A) is the publisher and distributor to a database on prod server 2 (A_REPL). prod server 2 (database B) is the publisher and distributor to another database on prod 1 (B_REPL) (so 4 databases so far on two servers).the test server has two databases that replicate to two other databases all on this test server (4 databases and 1 server) (named A and A_REPL and B and B_REPL)Now I want to refresh the data from prod 1 one of the databases (database A)) to the test server (one of the publisher databases (database named A on this test server)). How can I refresh the data without messing up replication? Is SSIS the way to go? I would do this after hours.Thanks in anticipation of any advice anyone may have. General suggestions or specific details appreciated. Whatever you have time for :-)

Editing replication stored procedures

0
0
Just wanted a high level answer really on whether or not it is a good idea to alter the sql replication stored procedures. Reason I ask is that we have a need for replication but the destination table has many additional columns to the source and a proposed solution is to set up transactional replication but customise the sprocs to retrieve additional information.I have to admit I dont particulalry like the idea but I might be being a little too cautious, is it a reasonable solution to consider?

Indexed view to table replication. No errors but also no replication.

0
0
Hi,Yesterday I altered our Products table. Just added a nullable column.This morning I was informed that products were not being replicated.Turns out the replication was an Indexed View to Table. (Transactional).To add the column to the view, it had to be removed from replication.The publication only has this one indexed view as an article.I dropped the publication, altered the view to included the new column then recreated the publication.Replication monitor shows all is fine and log reader agent is showing new transactions with commands, yet the products table on the subscriber still shows old data.The replication has been recreated many times with different options. In the article property the "Destination object name" is set to the table name on the subscriber.The table only has 85,000 records. Snapshots are created in 14 seconds.I have followed up these links, but couldn't resolve my problem.[url]http://www.sqlservercentral.com/Forums/Topic447542-291-1.aspx#bm448403[/url][url]http://www.sqlservercentral.com/forums/Topic348632-291-1.aspx#bm599356[/url]Any idea's?

replication undistributed commands

0
0
Hi Gurus,I am having weird situation in replication monitor. I see latency time 00:00:01 in replication monitor but when I check "undistributed commands" tab I see the transactions to apply are 69000 and estimated time is over 1 hour but latecny tab shows zero.and also When I click "undistributed commands" it took a while to get the above results. There should be something wrong. Please let me know what would be the possible reason for this.
Viewing all 302 articles
Browse latest View live




Latest Images