.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Server Migration with Replication

Posted By:      Posted Date: October 08, 2010    Points: 0   Category :Sql Server
Hi All,

I am in the process of moving our database server onto new hardware . Some of the databases on old server are involved in replication. So my question is:

(1) If I created the replication jobs same as existing old server and also script publiations from old server and run both the things ( replliation jobs and Publication ) at my new server...............Will this be enough (or) not............Will this work ....... Will database gets in synch.

Please let me know what is the best way that I should be doing this task efficiently.


View Complete Post

More Related Resource Links

SharePoint Enterprise Search Migration Tool for SharePoint Server 2010

Use this tool when you upgrade to SharePoint Enterprise Search to migrate search-related data, such as best bets, search scopes, and site collection search settings.

SQL Server 2005 Merge Replication

We did the following: We setup a database with all of standard tables, views, etc. We then put in place merge replication for a few of the tables within this database, including a tables called "Areas". We can execute SQL statements to insert rows into this table fine. We then applied an update script for this database to change a few tables by adding fields and changing indexes, etc.  We didn't change the "Areas" table though. After the update to the database structure, we get an error when trying to insert into this "Areas" table. The error message was the following: The insert failed. It conflicted with an identity range check constraint in database 'AETest', replicated table 'dbo.Areas', column 'AREPrimaryId'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.  The statement has been terminated.   What would cause such a problem and how do we resolve it?  The structure of the "Areas" table before and after the update is the following: USE   [AETest] GO /****** Object: Table [dbo].[Areas] Script Date: 08/24/2010 17:42:36 ******/ SET   ANSI_NULLS ON GO SET   QUOTED_IDENTIFIER ON GO SET   ANSI_PADDING ON

Sql Server 2008 R2 Replication

Dears, I am make a testing environment before implementing it into real world. I have 3 servers SQL 2008 R2, i configured 1 Publisher, 2 Subcribers with a merged replication. Everything is Ok. However, i have an ID field on Publisher which is autonumber(Start by 1, increment by 1). When I try to add new record on publisher, it takes it 1 by 1 i.e. 1-2-3.... But i try to add it on subscriber it starts with 20,000 i.e. 20001, 20002. I think this is logical for SQL, but can i define this number on the subscriber? So it will start on 200,000 for example? Another question, In LAN i can connect the subscriber to the publisher, it will connect to it directly, since it is broadcast. But in WAN environment how can the subscriber detects the publisher??? Your reply is highly appreciated, Thanks in advance,

Replication Wizard doesn't like SQL Server Alias

I tried creating a new replication but I get an error that says, "SQL Server replication requires the actual sever name to make the connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specifiy the actual server name, 'SomeMachineNumber'." I don't get this. Why can't I use an alias? I googled and found few articles but not sure if I understand what others are talking about. Here is how I have things set up and I'm hoping someone can explain to me what is happening. On my machine, I have the following alias set up. Alias Name: SQLDEV, Port No: 2433, Protocol: TCP/IP, Server: SomeMachineNumber In Mgmt Studio, I can connect to the server SomeMachineNumber by using the alias SQLDEV. However, if I try to create a new publication on SQLDEV, I get the above error. Now, just for the heck of it, I created another alias using the same properties as above except, I named the alias the same as the server, "SomeMachineNumber". I connect to the server in Mgmt Studio using the new alias, and now I am able to create the new publication. Does this make sense? Am I not still using an alias in the second example? Why does the replication seemingly like the alias "SomeMachineNumber", but not "SQLDEV"?

SQL Server Compact 4 replication library bug ?

I get the subscriber connection string from a SqlCeReplication object like so: public string GetFullConnectionString(string connectionString) { using (SqlCeReplication repl = new SqlCeReplication()) { repl.SubscriberConnectionString = connectionString; return repl.SubscriberConnectionString; } } With a connection string of: "Data Source=C:\data\nw(40).sdf" I get this from 3.5.8081: ssce:default lock timeout="5000";data source="C:\Data\nw.sdf";ssce:max database size="256";ssce:max buffer size="4096";ssce:temp file max size="256";ssce:enlist="True";ssce:default lock escalation="100";ssce:autoshrink threshold="60";ssce:flush interval="10"; But I get this from 4.0 CTP 1: "Autoshrink Threshold=\"60\";Case Sensitive=\"False\";Data Source=\"C:\\data\\nw40.sdf\";Default Lock Escalation=\"100\";Default Lock Timeout=\"5000\";Encrypt Database=\"False\";Encryption Mode=\"\";Enlist=\"True\";Mode=\"Read Write\";Flush Interval=\"10\";Locale Identifier=\"-1\";Max Buffer Size=\"4096\";Max Database Size=\"256\";Password=\"\";Persist Security Info=\"False\";Temp File Max Size=\"256\";Temp File Directory=\"

Replication between SQL Server 2005 and SQL Server 2008

Hi,    We were using SQL Server Transactional Replication between two SQL Server 2005 servers. Now we are going to upgrade the Publisher server to SQL Server 2008, Distributor Server remains as SQL Server 2005.     Can anyone let me know what is the challenges we need to face when configuring Replication between SQL Server 2005 and SQL Server 2008. Replication Method - Transactional Replication Distributor/Subscriber - SQL Server 2005 Publisher     -  SQL Server 208 Regards, Fazlu.

Exchange Server 2007 SP1 mailbox migration into 2010

Hi Everyone, I’ve got all in one Exchange Server 2007 SP1 RU3 that got all in one role installed (HT-CAS-MBx) in Windows Server 2003 Standard R2 SP which is also running as domain controller with all FSMO role. I’m planning to migrate the Exchange Server 2007 server role into the Exchange Server 2010 Standard that I have prepared in my Virtual Machine of Windows Server 2008 R2, what is the safest migration path to make the email flow working end to end parallel (staging migration process). [B](please also not that this Exchange Server 2007 SP1 got so many problem like – OOF email error in Outlook 2007, meeting scheduler stopped working, etc… therefore updating it into SP3 is not the way here and I've backed up the mailbox using Backup Exec 2010 in case i can just restore the backed up mailbox into the new server 2010 if possible)[/B] My this is what I’m about to do: 1. Transfer all FSMO role into another domain controllers 2. Install and configure similar role in the new VM (Exchange Server 2010 Std.) 3. Confused… Things to do after all mailbox migration: 1. Cutover the MX record into the new server name 2. Install updated UCC- SSL certificate into the exchange server 2007 Any kind of help and suggestion would be greatly appreciated. Thanks, AWT /* Infrastructure Support Engineer */

Membership migration from MS Access to MS SQL Server

Dear all,I want to migrate membership data table from Access to SQL Server but I got a problem about Data type.Do you know some topic what is related with it or somebody can did it?Thank you,

Migration of DSN use for SQL Server access from Windows SP-3 clients to Windows 7 64 bit client

We have numerous apps which use a named DSN using SQLSRV32.dll for an ODBC connection from our Windows XP-Pro SP3 32 bit machines client access to remote windows 2003 based SQL servers (mix of 2005 and 2008).  On migrating to Windows 7, this dll will not allow the apps to use the newly constructed DSN (using SQLSRV32.dll with ODBC), even though a test connection is sucessful (abbeit much slower than seen on the XP-Pro machines).  What must I use on the Windows 7 64 bit machine to allow a DSN to be used by the migrated apps?  - I have descerned through Google that WDAC is now the tool to use, but I am cluless how to use it. - The expectations from the app on the Windows XP-Pro and on the Windows 7 64 bit machines is to use a DSN to connect to SQL servers on Windows 2003. I would appreciate any advice, and thanks!

Using SQL Server Replication for SQL Server 2005 and 2008

I have an ASP.NET application that uses replication, and uses the RMO DLLs to do this. I initially built the application against the 2005 version of the DLLs and have it running successfully against SQL Server 2005. However, when I try running it against SQL Server 2008 it doesn't work. Initially I didn't deploy the Microsoft.SqlServer.* DLLs with my app - instead relying on them being in place on the server on which it was installed. However, when trying to make it work against SQL Server 2008 it was looking for the 2005 version DLLs which it wasn't able to locate. Following some other advice I read online I have now swapped out the 2005 DLLs and referenced the 2008 assemblies in my .NET project. In my MSI I now also deploy (i.e. redistribute) the SQL Server 2008 DLLs to the bin folder of my ASP.NET project. Now, when I try to run the application against SQL Server 2005 it fails to load the Microsoft.SqlServer.Replication assembly. I run depends.exe against this and find that it's dependent on SQLNCLI10.DLL which is missing on my machine with only SQL Server 2005 on it. So, what am I to do? Is this possible? How do I get around this?

SQL server 2008 to oracle replication

Hi, I am trying to replicate data from a sqlserver to an oracle 11 subscriber(push subscription). I recently moved to SQL server 2008 from 2005. The replication in 2005 worked ok, and now in 2008 - it does not. The problem: It tries to make some fields as an interval data type in Oracle. For example, nvarchar(3) are turned into interval and numeric(38,8) fields are turned into nvarchar2(40). Anyone has any idea why is this happening and how can I change it?

Replication: How could we use SQL Server to perform this replication model ?

Hi everybody, I'm trying to build up a database system using both peer-to-peer and normal transactional replication. However, it seems to be not able to combine both types of replications on one database. This is the replication model which I'm trying to build. http://a.imageshack.us/img28/4095/8copym.jpg I have already had two DB servers and one common database which could be synchronized between these two DB servers using peer-to-peer replication (2-way synchronizing). And then I attempt to use normal transactional to perform 1-way synchronizing but not successful. Always get this error: Invalid column name '$sys_p2p_cd_id'. Anyone has ideas to resolve the problem or suggestions to build this replication model. Please help.   Thank you.  


Hi All, Yesterday we installed SQLSERVER 2008 R2 in our development mechine , and already it have Microsoft TFS 2008. When i open my report project it came up with the upgrade messagebox i clicked on Yes.And i try to run the reports locally its giving me exception like "An attempt has been made to  use the data extention 'custom datasource extention 1.2' that is eaither not registered for this report server or is not supported in this edition of reporting services'.So i did the changes like adding the dlls into the reportserver bin and added the data block which i have configured for SSRS 2008 i have applied the same setting for the SSRS 2008 R2 but still i am gettign the same exception do we need to do any changes in SSRS 2008 R2. because i am able to run the reports sucessuflly in SSRS 2008 but not SSRS 2008 R2? Any body have ideas on this. Thanks, Veeren.

Error message in opening a view after Replication server restored

Hi, Yesterday Replication was broken as Publisher was down. After it was restored, I tried to open a view in Subscriber and I get the following error message [Microsoft] [ODBC SQL Server Driver] [SQL Server] Login failed for user 'Repl admin'   Any suggestions to get around this problem.   Thanks in advance -Jaya

Error in SQL server 2000 after the migration (internal query processor error)

I just moved a couple of databases from one instance of SQL 2000 from different hardware to SQL 2000 instance of other hardware and after the move from the application side the app team gets an error -2147217900 - Internal Query Processor Error: The query processor could not produce a query plan.  Contact your primary support provider for more information.', 'E', '2UA929041X. Does any one have any idea about this. I took a trace while they were testing and I found out this in the trace. exec usp_DlyPrc_LogProcessEvent '-2147217900 - Internal Query Processor Error: The query processor could not produce a query plan.  Contact your primary support provider for more information.', 'E', '2UA929041X An idea or direction on this will be greatly appreciated. Thanks hash

SQL Server 2008 Standard replication

Dear All, Im new in SQL, would like to what will be the consideration and effort from [WIndows Server 2008 STd with SQL Server 2008 STd] and replicate over to another location with same setup? Is there any guide which could describe the steps for this?  
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend