I have a magic phrase I've memorized and you can have it too.

"I don't know, but here's how I'd find the answer..."

Now, you have to have a plan for finding...

Just guessing here, but if the data was ordered first, so that you're doing your batches in the same order that the data is already stored in, you'll likely see...

Piling on a little. It's truly dependent on the load of the system, data size, number of transactions, transaction size, database design, statistics, indexes, code, code, code, system settings, version,...

They will tell you right up front if you have to pay for anything, and what that cost is. Just go straight to the source.

In addition to @Ant-Green's excellent answer, after you get the backups working, practice doing restores. Do a full restore, then do point in time restores with the logs. Make sure...

Again, we're talking theoretical. I don't have a specific answer I can give you on this question. Either could work. Either could work well. Testing is your best friend. This...

I very much agree with the answers you've already received. SQL isn't meant to be a "looping" language. It's designed to work on the concepts of sets. Yes, there are...

Really sounds like you may have the database in FULL recovery, but you're not running log backups. Just guessing, but from what you've posted, seems likely. However, if you answer...

One thing, toss, the action for SQL text. You'll get the statement values anyway in the event.

However, right there with Jeff, the nature of the session you have here is...

ADS has an explorer window. You can see the objects and their properties there.

Jeff has laid out most of the interesting bits of storage of nonclustered indexes. Here's a...

I suspect Eirikur is looking at recovery as the culprit. Sounds right too. How big is the log?

It's a soup to nuts, everything is on the table, proposition to really get proper protection  from SQL Injection.

First, and most important, use the least-priviledge principal when setting up your...

Whoops! Weird.

For Redgate Compare, you don't have to have a primary key. You do have to have a column, or set of...

I'm not sure I understand the example that's giving you problems. Yeah, if the column names are different, you have to explicitly state them on an INSERT ... SELECT. That's...