The Derived Column Transform component will do this.  You put it between the data source and the destination, and use expressions to define new columns.  The destination will see both...

The given answer applies only to transactions in stored procedures, where the stored procedure execution has been replicated.  Nothing in the question says anything about a stored procedure, whether the transaction is in a...

From "Role Assignments for Report Builder Access" in BOL:

Creating a System Role Assignment for Report Builder Access

To use Report Builder to create, modify, and save ad hoc reports, users...

They're crying over $300 million?  Doesn't Congress waste more than that before lunch on a slow day?

If a DBA was involved, we need to organize having a statue erected in...

One side effect of log shipping is that the destination database is read-only.  You can't change roles or permissions, but they can't make any updates.  But if you need completely...

In SQL 2000 you can deny CREATE PROCEDURE permissions to users in the ddladmin role, but unfortunately that doesn't prevent ALTER PROCEDURE or DROP PROCEDURE.

You could script all your procedures and...

The backup/restore method works, but if it is a large database you will spend a lot of time copying data every day.  The reporting database will only be refreshed once a...

There are a lot of reasons not to let anything (not just MySQL) be installed on your SQL servers.  It will compete for memory, disk space, and processing power.  As...

Dates are stored in a numeric form that doesn't look anything like dd/mm/yyyy or mm/dd/yyyy or any variation thereof (if they are datetime or smalldatetime).  The numeric values in the database are the...

I'm a minimalist.  The CASE function (it's not a flow-of-control statement) can be used anywhere it is legal to use an expression, so just use it in RETURN and forget...

An alternative would be to UNION the publisher list queries, which also removes duplicates.  I often use IGNORE_DUP_KEY myself, but it is not standard SQL and you should at least be aware...

The sid (security ID) of OrdinaryUser as a user in your attached database must match the sid of the OrdinaryUser login you created on the server.  Simply creating a login...

Don't even think about GUID primary keys for this particular case, sequential or otherwise.  There are other designs that will perform much better.

It doesn't really waste space to have a lot...

With Enterprise Edition you can do online index rebuilds and other maintenance without locking up tables.  This relies on snapshot isolation, and will eat a lot of tempdb space.

It's a great...

One of the first things to do when you seem to be getting bad query plans is to force updates of statistics and rowcounts (sp_updatestats and DBCC...