Just use a separate DB on the publisher to collect the merged data.

Cheers,

Large updates *do* have impact on replication. The reason is that whatever goes into your transaction log gets stored in the distribution database (for the retention period). 10 000 rows...

Totally agree with my friend Ed. An in-place upgrade is a risky business. I have been through this "upgrades" many times my advice is that you should do it as...

To take advantage of partitioning there are several requisites. Look at partitioned Views in BOL. In particular the primary key must define a check constraint so that the engine can...

First When you use INSERT/SELECT you should especify the colum list on the insert table and on the select too.

That way you know exactly what goes where.

Secondly your source procedure...

I guess its better late than never!!!

Congratulations and Thank you very much for your support.

This sort of application as well as the encryption one do make a lot of sense in mobile devices. In there you need to minimize space and maximize security.

That...

I have to agree with colin here. This is one of those "dangerous" articles that could mislead people. You need to think really twice before using (NOLOCK) I would add...

sure just replace the comma "," for " + CHAR(13) " and you will be fine.

Mind you there is a limit of 8000 characters for the operation.

good luck.

This is a "WORKING" example... do your thing and Enjoy!

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[proc1]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)

drop procedure [dbo].[proc1]

GO

if exists (select * from...

dbachmann,

When replication is installed *many* of the database security roles that used to work are effectively broken. The reason is that M$ is hardcoding those permissions on the replication stored...

Allow me to differ:

This is a sample from BOL:

USE pubs

SELECT royalty, SUM(advance) 'total advance',

GROUPING(royalty) 'grp'

FROM titles

GROUP BY royalty WITH ROLLUP

Cheers,

You can't truncate the Log of a database in simple recovery mode

You can run CHECKPOINT though to get the expected effect immediately

Database Partitioning is *not* a primary performance feature. It is mostly a maintainablility one.

I have "several" instances in which that was the case. On SP2, M$ is saying that...

Hehe ... I was biten by that too