opc.three (6/21/2011)

---

Which method performs better in the end will depend on the data volume, recovery model, data set shape, probably too many variables to definitively say one method will perform...

Try datatype DATE instead of DBTimestamp

opc.three (6/21/2011)

---

Whether supplying an explicit column list or a * SELECT...INTO generates a table with no clustered index, i.e. a HEAP. If you're managing large quantities of data in temp...

Jeff Moden (6/21/2011)

---

toddasd (6/21/2011)

---

What do yall think about giving the interviewee a "broken" database to analyze? Script out one of your databases except remove some indexes, rewrite a basic update...

Single Connection manager for ease of use, don't turn on the RetainSameConnection property (ie: Leave it False) and they'll each open an independent SPID.

This is your best method unless you...

opc.three (6/21/2011)

---

I won't let the cat out of the bag as to how I think you're planning to create the misdirection necessary to accomplish a secure xp_cmdshell environments without any...

Steve Jones - SSC Editor (6/21/2011)

---

Depending on how your storage works, anything could work. 30GB isn't a huge amount and SSIS has been shown to load 1TB in about 30...

I would target this normalization very differently. Instead of going all the way to having an ID for a length amount, I'd expect some standardization (cm for example) of...

00 and 09 are character entries to sql, not digits.

Easiest way to display it is along the lines of:

SELECT RIGHT( '00' + DATEPART( mi, @timevariable), 2)

Craig Farrell (6/20/2011)

---

I may need to, however, learn more about this before I go any further in this debate:

opc.three (6/20/2011)

---

xp_cmdshell can be used by everyone on the instance but that...

Above is now reported as a marketing post.

asm1212 (6/21/2011)

---

Solution:

What can I do? What is the best way to get those databases set up on the reporting server with that data synced up every 24 to 48 hours???...

I went jamming down the wrong road, sorry. Had another methodology in my head, but it's really overkill.

Here's the typical way to do it:

;WITH LeftMethod AS

(

SELECT

eid.EventID,

CASE WHEN eSt.EventID...

Annoying. 😉

Right Track: Kinda, use a single cte and join it twice. Also, EventType...

UPDATE tbl SET phoneNumber = '0'+phoneNumber WHERE LEFT( phoneNumber, 1) LIKE '[1-9]'

... should work.

EDIT: Dang Ninjas... sneaking in unexpectedly EVERYWHERE!