March 29, 2002 at 9:35 am
Here is the situation. Our comapny has a test SQL Server 2000 and our ISP has SQL Server 7. We need to be able give out serial numbers to our customers for our software (they are required to register first). We currently do this locally over the phone and enter registrations on a database the runs on our LAN. We now want to set up a Web interface to allow users to register on our site. We could also just use the ISPs db server instead of the one on our LAN but this could raise performance issues and our DSL typically goes down a couple times a month for a few hours. This is why I am think of replication.
Our ISP is willing to let us use replication but I am not sure which way to go:
Transational, Snaphot or Merge. I also don't know if the ISP's server should be the publisher or our server should be a publisher. Your sugggestions are appreciated.
March 29, 2002 at 10:13 am
I'd recommend that your server be the publisher since you'll be doing the administration. Since there is a fair chance of down time you'll want to use either transactional with queued updates or merge. Of those which you pick probably depends on your comfort level with replication. Merge is the more advanced/complicated of two.
Andy
March 29, 2002 at 10:17 am
quote:
I'd recommend that your server be the publisher since you'll be doing the administration. Since there is a fair chance of down time you'll want to use either transactional with queued updates or merge. Of those which you pick probably depends on your comfort level with replication. Merge is the more advanced/complicated of two.Andy
Thanks ANdy I'll try transactional with queued updates since I am new to replication. (I've really just used SQL server as a web developer).
Will I need administrative access to my ISP's SQL server or will I need them to do something (I only have permissions for my database obviously)
March 29, 2002 at 10:55 am
I think db access is all you need. Use push rather than pull so most of the activity is on your side.
Andy
March 29, 2002 at 4:03 pm
I get the following error in the replication Monitor:
Could not find stored procedure 'sp_MSdel_MDClients'.
{CALL sp_MSdel_MDClients (10066, 123456, 'Fake CLient', '1234 5th st', NULL, 'St. Paul', 'MN', '55104', '651-642-1988', {2009FB14-A2BA-427C-88EE-FA0C28FB5D73}, {0A6C22B2-4513-4F1F-A5B7-115E26258DDB})}
Transaction sequence number and command ID of last execution batch are 0x0000005100000118000800000000 and 1.
The store procedure is not found on my ISP's server.
Any suggestions as to what to do on this one?
March 30, 2002 at 5:50 am
When you send over the initial snapshot a bunch of these type procs get created - they apply the changes shipped from the publisher. If you bypassed the snapshot process they will be missing. You can use sp_scriptpublicationcustomprocs to generate them.
Andy
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply