You'd have to ask ArcServe. The SQL side should be fine. It doesn't matter where or how the backups are taken, as long as they are transactionally consistent with through...

Have you tried stopping and restarting the replication agent?

Can you connect from SSMS on one server to the other? Or with a Linked Server/OpenRowset just to verify there's no network...

You can use staging tables, or partitioning, if your edition supports it. Partitioning sounds like what you are thinking of.

When you looked through the data, do you mean in SSMS? Or did you query something like LEN()?

Never been to a GenCon or Comicon. Would like to give it a try if one comes close.

Yes, always looking for them.

Miles Neale (1/15/2013)

---

Steve, I have to admit that today's editorial is one of the most hard-nosed, direct, hard hearted, and excellent ones you put together and I could not...

aykut canturk (1/15/2013)

---

okay, not related with this topic but if I use ms azure for hosting instead of renting my own physical one, would I guarantee that my sql data...

majorbloodnock (1/15/2013)

---

GSquared (1/15/2013)

---

The problem with the part I added emphasis to, is that quite often a company needs to hire a DBA because they don't have anyone who knows anything...

you may need to qualify as I mentioned:

USE [TrackIT]

GO

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

CREATE TRIGGER [dbo].[trUpdateBulkPurchases]

ON [dbo].[tblTransactions]

AFTER UPDATE

AS

BEGIN

UPDATE tblBulkPurchases

SET

PO_Number = i.PO_Number,

Quantity = i.Quantity,

Unit_Price = i.Unit_Price,

Software_Description = i.Software_Description,

PO_Date = i.PO_Date,

PurchaseCostCenter = i.PurchaseCostCenter,

HeatTicketNumber...

Do you have an asterisk in your code? I thought you were using the to mark the place you were writing about.

No asterisks needed in your code.

What's the error? If it's an ambiguous column, you need to specify from which table (The base one or INSERTED) you are specifying in the WHERE clause.

Sorry, wasn't reading well. The problem is that you have a malformed UPDATE statement.

CREATE TRIGGER [dbo].[trUpdateBulkPurchases]

ON [dbo].[tblTransactions]

AFTER UPDATE

AS

BEGIN

UPDATE tblBulkPurchases

set PO_Number = i.PO_Number

, Quantity...

No effect. The extensions have no bearing on the files' purpose or use. They are set to mdf/ndf/ldf only for convention.

I had a line on a job in Kabul. 35% "danger" pay. Not sure it's worth it, though that car looks nice.