Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Help with replication scenario Expand / Collapse
Author
Message
Posted Tuesday, April 2, 2013 2:45 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, February 27, 2014 12:33 PM
Points: 13, Visits: 28
I have a scenario at work where I need to replicate (in the general sense, not necessarily in the "sql server replication" sense) a database in approximate realtime between two instances on separate servers.

The source server is running sqlserver 2000 standard and is a 24x7 database running a vendor-supplied dispatch program. Altering the structure of this DB is a non-starter.

The destination server runs sqlserver 2008r2 and does web services.

I tried setting up a transactional replication publication on the source, but it failed because several of the tables have > 255 columns. I got errors saying the articles couldn't have this many columns, and the snapshot couldn't be created.

So I looked at doing mirroring, but I don't think I can do database mirroring with server 2000, correct?

I also looked into log shipping, but apparently you need sqlserver 2000 enterprise to do log shipping (later releases do it with any version of the db).

Does anyone have advice or corrections for me? Can I do mirroring? Can I make log shipping happen with 2000 standard edition? Is there an easy fix for replication of big tables?

Also, is the 255 columns limitation specific to sqlserver 2000, or do all releases have that limit?
Post #1438087
Posted Tuesday, April 2, 2013 10:26 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 24, 2014 1:14 AM
Points: 60, Visits: 401
Hi

Can you try creating a DTS/SSIS package to transfer the data from your source server to destination? And schedule the package in an agent job to run every hour or so depending upon the amount of data that gets updated every hour ?

I have a scenario where we use a Package to refresh data from source just twice a day..

You might also have to consider a few points before you go ahead 1. No schedule conflicts affecting other jobs running on the server 2. Network bandwidth/resource utilization etc.. All these will depend upon the amount of data that is being transferred..
Post #1438160
Posted Wednesday, April 3, 2013 7:50 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, February 27, 2014 12:33 PM
Points: 13, Visits: 28
I think they wanted the data to be fresher than that; Is there a way to do a "differential transfer", so to speak, with SSIS?

Well, I spoke with the server admin yesterday afternoon and he says they are going to upgrade the database to 2012 at some point in the relatively near future, so maybe I will revisit this when they do.
Post #1438344
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse