January 30, 2007 at 6:39 am
My suggestion is wait SP2.
January 30, 2007 at 8:54 am
?? Not sure what you mean
January 30, 2007 at 1:13 pm
i think there is a memory leak in the client components, a bug in replication the put in on purpose, a few other bugs in replication that make it more maintenance intensive than sql 2000 and i don't know what else we haven't discovered yet
January 31, 2007 at 6:42 am
Check the bugs fixed in SP2, you will know what I mean.
http://support.microsoft.com/?kbid=921896
I can't put SQL server 2005 in production without those fixes.
January 31, 2007 at 7:15 am
my favorites are in replication when you have a varchar column with more than 4000 characters it changes it to ntext. if you have a sql2000 subscriber you are out of luck because it can't convert back to varchar(8000) so i'm doing nightly snapshots of one publication.
and i'm actually running alter index on the distribution db. the clean up ran for like 9 hours a few times and it turned out all the indexes were fragmented. so i'm running alter index every few hours
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply