SQLRNNR (10/26/2011)

---

Sean Lange (10/26/2011)

---

Chad Crawford (10/26/2011)

---

I was in a meeting today where we were talking about bug tracking, and I just have to share. Here is how it...

Chad Crawford (10/26/2011)

---

I was in a meeting today where we were talking about bug tracking, and I just have to share. Here is how it went:

Boss (to group):...

I second that. Nice work Wayne!!!

GSquared (10/26/2011)

---

Not too surprising, on the Denali deodorant.

"Denali" is the Athabaskan name for Mt McKinley in Alaska, and means "The High One". (Which could be taken all kinds of...

join school on school.SiteID = coalesce(tempsiteID, permsiteID)

Not sure what else can be said. If tempsiteID is not null then it will join on that, otherwise it will join on the...

just join on tablea = coalesce(tempsiteID, permSiteID)

You can't specify the same column more than once in a single update. Which one does it use as the new value???

To accomplish what you are trying you will have...

No problem. It is a great shortcut to figuring all that stuff out. 😉

Take a look at this. http://www.sqlservercentral.com/blogs/lynnpettis/archive/2009/3/25/some-common-date-routines.aspx

Floss

Easiest way to make sure your update is not doing something really bad is to put it in a transaction first.

begin transaction

update blah blah

rollback transaction

If you see a reasonable...

How do you know which one is first?

update table

set column = somevalue

where Some Condition

That help?

evaleah (10/21/2011)

---

Thank you! This is very slick!

I keep going back and forth on the one lookup table design. For UI purposes in this case it makes it easier...

That is a pretty slick way to deal with that Lowell. I will have to add to my bag of tricks when dealing with other people's data structures. :w00t: