Viewing 15 posts - 76 through 90 (of 100 total)
Hi,
What's your goal with the Disaster Recovery Plan? Do you want to have a general one or a specific one for your environment?
There's no point to create a general one...
September 10, 2007 at 9:58 am
Hi,
Just a quick question to avoid a pitfall: Do you use uncommitted read in your query? I yes, this error message can be quite normal (if not pointing to the...
September 7, 2007 at 2:47 am
Jeremy,
The size of the transaction log (of the app db) won't grow faster because of replication.
One question: how are you going to implement the pull replication on SQL 2005...
September 6, 2007 at 5:01 am
John,
Aren't you going to upgrade to SQL 2005? There you can use peer-to-peer (bidirectional multimaster) replication which can give you the required result.
September 6, 2007 at 2:04 am
Agree with Paul. You can use also log shipping for business continuity, with which you can quite easily bring your lost database up-to-date. Read this series: http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlhalp.mspx
September 3, 2007 at 11:06 am
Hi Mike,
Microsoft is your friend, they've almost done it Check http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx and download the word document. As you'll see, you can...
September 1, 2007 at 2:54 pm
Hi,
It looks like a disk bottleneck. Check it, and if it is, then try to lower the number of virtual devices in LiteSpeed (I don't know how they call it...
September 1, 2007 at 2:33 pm
Hi Pavan,
Next time if it happens, find what causes the blocking, this way you may modify your script to avoid this situation. Here's a quite simple script for this task,...
August 31, 2007 at 1:16 pm
Hi,
Check this:
http://technet.microsoft.com/en-us/library/ms152572.aspx
This is for SQL 2005, but may help you.
August 31, 2007 at 12:23 pm
SQL ORACLE,
You should be nicer to a new guy
Hank,
You can do this with transactional replication and with some trick
August 31, 2007 at 11:34 am
Hi Simon,
There's no difference until you add more articles to your publications. So you can decide which one is the better for you. I would choose the 'all' instead of...
August 31, 2007 at 11:15 am
Hi Mike,
1-Firewalls are a very good arguments for push replication. This case you need to open only one port: your SQL server for your customers. First, this way you risk...
August 31, 2007 at 5:17 am
Sure, you can do it, but it won't take into effect until you restart your job if it's set to run continuously. In this case, you can easily stop and...
August 29, 2007 at 7:18 am
Hi Mike,
If I were you, I'd set up continuous push replication. My reasons:
Continuous: If you set up a scheduled replication, then from time to time it starts up, hitting your...
August 29, 2007 at 7:15 am
JP,
Here's the URL, it was posted to another forum (hopefully I won't be banned for this ).
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=69430
If you can migrate to 2005,...
August 17, 2007 at 1:44 am
Viewing 15 posts - 76 through 90 (of 100 total)