Viewing 15 posts - 16 through 30 (of 100 total)
Hi,
This should work fine if subscribers are at least SQL 2000 SP3. Check http://msdn.microsoft.com/en-us/library/ms143241.aspx for more details. Of course you should test it first 🙂
January 2, 2010 at 3:45 pm
With all respect, I don't see why bulk insert would cause problem in TRANSACTIONAL REPLICATION. I read Hilary's answer, but still... Can you shed some light on this for me,...
July 14, 2009 at 1:34 pm
Hi,
Transactional replication works by reading the transaction log, not using triggers, so it shouldn't be a problem.
July 13, 2009 at 8:10 pm
Luke's suggestions are pretty straightforward 🙂 I handle this kind of issues in the following way: all login attempts are logged into the server errorlog and I get a filtered...
June 23, 2009 at 1:05 pm
Hi,
Apparently you set up an updatable transactional replication. You should rebuild the replication, stating that it cannot be updated. Until that, remove the write permission of the developers 🙂
May 22, 2009 at 1:21 pm
Hi,
If I got you correctly, you want to provide the right for role1 to grant some permission to role2. In this case you can use the grant command with the...
May 22, 2009 at 1:19 pm
Hi,
In SQL 2008, you can audit virtually anything (including reads) iirc. So a simple way is to upgrade - oops, it's an Enterprise feature of course, but you have...
May 21, 2009 at 11:46 pm
Not (only) to marketing myself, but if you have PowerShell at hand, check http://getmssqldump.codeplex.com in terms of data movement. With this, you can extract the records into insert...
May 21, 2009 at 11:36 pm
Hi Neil,
Your backup strategy seems straightforward to me, that is, keeping on disk only the last backup files. Only thing you have to consider if you take also differential backups,...
May 21, 2009 at 11:32 pm
SQL 2003 does run on Linux. I read it in the CV of one of our DBA candidates. And he was self-confident. So I didn't dare to question him... nor...
April 1, 2009 at 5:28 pm
Hi,
Just another idea: are the subscriptions logging properly? Couldn't that happen that for some reason the agent cleanup job removes the subscriptions?
April 1, 2009 at 4:22 am
Hi,
It can't be something with the OS/HW, otherwise your databases would be corrupt and you'd definitely noticed it. So something is on the SQL side. Question: only the jobs disappear...
March 31, 2009 at 2:20 pm
Hi,
If I were you, I'd consider removing the constraints and then checking if I can figure out what happened. If it turns out to be something "expected", you can instruct...
March 31, 2009 at 2:06 pm
If this is an already initialized subscription, I suggest you adding -CommitBatchsize and -CommitBatchThreshold with a low value (I had to set them to 1 in a similar situation), this...
March 30, 2009 at 10:28 am
If you raise a few of your questions I try to point you to some specific resources. I've been learning transactional replication for two years (and totally lame in merge...
March 30, 2009 at 10:23 am
Viewing 15 posts - 16 through 30 (of 100 total)