selecttop 1

A, B, ... other columns ...

fromMyTable

order byA, B desc

I think that depends on who is doing the outsourcing, and the particular activity they are outsourcing.

The thread on the link below is a good example of a way not to generate a Next ID. I had thought about this method myself, so this is...

Jeff Moden (3/21/2009)

---

Ummm.... just a couple of things to clear up here, folks. First, DBCC ShrinkFile does not now nor has it ever nor will it ever cause fragmentation....

J (3/21/2009)

---

Michael Valentine Jones (3/20/2009)[/b

Not that I would ever recommend using this to get the next ID for anything I was designing, but when someone has already put something like...

Jeff Moden (3/20/2009)

---

Michael Valentine Jones (3/20/2009)

---

Not that I would ever recommend using this to get the next ID for anything I was designing, but when someone has already put something...

Jeff Moden (3/20/2009)[/b UPDATE NextID

SET @NextID = NextID = NextID + @Increment

WHERE TableName = @TableName

SELECT @NextID = @NextID - @Increment

... that little bit...

Are you sure it's actually a full backup? Maybe it’s just a differential backup of a database that has had so many pages changed that it's the same...

You should set the batch size on the DTS datapumps to a reasonable size, like 100,000 rows. This will make smaller transactions and help prevent expanding your transaction logs....

We run transaction log backups every 15 minutes, 25x7, on all transactional databases. It lets us restore to as close in time as possible after a problem, and it...

It is often better to shrink database files in small increments so that it can make continuous, incremental progress, instead of trying to shrink by a large amount in one...

Headphones for my desk phone are a big help.

I put them on and people automatically assume I’m on a “really import conference call” and leave me alone or run away...

We have literally thousands of people working in remote offices as far away as it is possible to be on Earth, so being far away is not a problem by...

I could mention using two-way merge replication, but that is really something that is just going to cause problems, not solve them. I imagine that anything you would do...

select

[HH:MM:SS:mmm] = convert(varchar(12),ET-ST,114),

*

from

( -- Test Data

select ST = convert(datetime,'20080318 23:57:33.887') ,

ET= convert(datetime,'20090319 10:45:47.850')

) a

Results:

HH:MM:SS:mmm ST ...