Ivanna Noh (12/16/2009)

---

great to see this thread come back to life!:w00t:

for all frustrated 120W amp owners out there that can't crank up the volume at home - try a Mesa...

Schadenfreude-Mei (12/16/2009)

---

happycat59 (12/16/2009)

---

Mmm, 120W. Can't even begin to image why she won't let you bring them home.

My sob story is that I have just been told that 7 guitars...

Mmm, 120W. Can't even begin to image why she won't let you bring them home.

My sob story is that I have just been told that 7 guitars is enough...

Transactional replication doesn't change the publisher's schema.

Merge replication will add the row guid column if it does exist.

For Enterprise and Developer Editions, the answer is 50 instances. For all others, the max is 16.

I think the problem exists because...

SQL Server may ask Windows to tell it when an I/O operation is complete. This is mostly required to ensure that things like the...

Your application may need to be changed for it to work in a mirrored environment. The connection string needs to include "Failover Partner=ServerName". This was introduced with SQL...

You cannot do what you are suggesting. With database mirroring, only one database can accessed at a time. When you failover, the database that was the primary will...

Your query could be something like ...

SELECT 'Opened' AS OpenClosed,

DATENAME(year, sys_requestdate) AS Year,

DATEPART(mm, sys_requestdate) AS Month_No,

DATENAME(month, sys_requestdate) AS Month_Name,

COUNT(sys_request_id) AS OpenClosedCount

FROM request

GROUP BY DATENAME(month, sys_requestdate), DATENAME(year, sys_requestdate),...

Replication includes a few agent collectively called Miscellaneous Agents (real imaginative, huh). One of these is responsible for deleting snapshots that are no longer needed.

As for estimating the size...

Replication does not restrict you from publishing from many servers to a single destination table. All you need to worry about is being able to make sure that the...

Any decision to use a separate server for the distribution database you be taken based on the expected load on each of the servers (publisher, distributor, subscriber). If you...

cjeremy74's solution sounds more like Log Shipping, not replication.

When creating a subscription in Transaction Replication when you wish to initialise using a backup, you specify the name of the database...

delete them - they have no value any more.

Have a read of articles "How to: Initialize a Transactional Subscriber from a Backup" and "Initializing a Transactional Subscription Without a Snapshot " in Books Online. I think everything...