Viewing 15 posts - 46 through 60 (of 100 total)
Ok, so:
Truncate_only invalidates your transaction log backup sequence
says http://support.microsoft.com/kb/272318. Basically this command says the following: Although I set my database to keep the history of transactions, now please...
December 21, 2007 at 2:06 pm
The big question is the following: do you backup the transaction log regularly or not? This is a cornerstone at database implementation - if you may need to be able...
December 21, 2007 at 9:44 am
Hi,
No chance for it. DBCC operations are not really suitable in a transaction. So if there's an error then half of your databases will be shrunk.
BTW, why are you doing...
December 20, 2007 at 4:38 pm
Oh, sorry, I missed the fact that you'd like to run your db in full reco. In this case, your solution is a good solution if it's ok with the...
December 18, 2007 at 1:38 am
Hi,
The recovery model of the subscription database is absolutely irrelevant from replication perspective (of course you may have to set it to full from business reasons), because the subscription database...
December 17, 2007 at 9:00 am
Sorin Petcu (12/13/2007)
One of users have made a mistake and put some data in the wrong place: in subscription database. The correct way was to put data in the...
December 16, 2007 at 5:04 pm
Hi,
My suggestion:
1. use push replication to make your life easier if you can.
2. build an ssh tunnel from the distributor to the subscriber through which the distributor can reach...
December 16, 2007 at 5:50 am
Is that a transactional replication with updatable subscriptions or a merge replication?
December 16, 2007 at 5:37 am
Before all: I really recommend you to put a CLUSTERED index onto all of your tables.
In this particular case, if the heavily queried column is the member of the composite...
December 16, 2007 at 5:03 am
As I experienced, you can telnet to a SQL server via its TCP port. In case there's a server waiting for connections, you'll get a blinking cursor so the server...
December 16, 2007 at 4:50 am
Hi,
The recovery model of the subscriber is irrelevant. I use transactional replication with subscribers with simple recovery model and works fine, so don't worry about it.
December 15, 2007 at 4:42 am
One short note:
If you need to setup transactional replication through firewall, push is a bit easier than pull, because push is happy with a TCP 1433 from distributor to subscriber,...
December 15, 2007 at 4:37 am
Hi,
2 questions:
1. The snapshot of the new articles were prepared? (you can check it in the snapshot agent log or in the snapshot directory if the snapshot is not compressed)
2....
December 15, 2007 at 4:23 am
Hi,
AFAIK error 1418 usually caused by two things:
1. Inapporpiate credentials - make sure both server have access to each other.
2. (more likely) You made your initial restore without the NORECOVERY...
December 15, 2007 at 3:10 am
Hi,
You can use the STANDBY clause for the recovery. This way you can restore the differential backups from day to day. However, when you take a full backup from the...
December 14, 2007 at 7:03 am
Viewing 15 posts - 46 through 60 (of 100 total)