There are a lot of situations....We had a ton of predeveloped...

Im with you there...nchar(1).

No character set was specified....so I have to choose unicode to handle all...

I know this is an older post but....in this case it does appear that the resolution was as simple as "you cant concatinate a null with a string without first...

I would have thought that too, except he proved the performance gain by the IO stats when doing the switch verses the typical way.

I find that even when using SET FMTONLY ON; (and NOCOUNT ON) I still have issues with using temp tables in general in SSIS..i can get around it by...

...but then again, assuming that there are no real concerns (small table, dev database, etc.) with using the "create destination, load destination, drop source, and rename destination" table approach, I'd...

I had a similar situation where i wanted a group to only run/stop jobs, but not modify, etc...i created the following role, which is essentially the SQLAgentOperatorRole minus certain permissions:

USE...

I too used your similar solution, but i do not want to allow my users to alter jobs, schedule them, delete them, etc. So i created the following...

Nice, that works. I forgot about SET ROWCOUNT, havent had to use in a while. Anyways, now there is a post from me with a cursor in it....crap!...

Sergiy (8/6/2008)

---

Well, I see you guys had a lot of fun here.

OK, I read this thread as well.

And I cannon figure out one thing.

Everyone agreed the puzzle was designed...

Im pretty OCD about the naming conventions that I use, but as long as you have something, it really doesnt matter what they are. Granted, some seem to work...

To further complicate things...can you actually SET ANSI_NULLS [highlight=#ffff11]= [/highlight]ON?

I got this correct, but only because i had to assume that the "correct" answer wouldnt be totally correct.

Select 1 as "Col1", Col2, Col3

From Table

Group By Col2, Col3

...will...

tymberwyld (2/29/2008)

---

Ok, I've looked through all the posts here, but I don't see anyone bringing up the SOUNDEX / DIFFERENCE functions. We're currently using this to help "enhance" fuzzy...

This is NOT what I would do, but depending on the size of your company table...its something different

Declare @SoundExName varchar(50)

Set @SoundExName = 'Smith, John'

Select a.EmpId, Difference(a.AssociateNm, @SoundExName) Diff

Into #Temp

From Associate...