Hey Noeld, glad you kept this one short .

Sorry Sergiy but this can't work >>

CREATE PROCEDURE dbo.TestDefaults @Input as int = 0

AS

SET NOCOUNT ON

Select @Input * 2 as Demo

SET NOCOUNT OFF

GO

Select O.Name, S.Name, S.cdefault from dbo.SysObjects O inner...

Oh that, apparently it's too hard to understand for newbies. Looks like I'll have to comment everything in details before reusing that again .

Well when I ask some questions about the execution plan, it's often faster to just ask for the plan than to educate the guy on how to read it... and...

I guess it's time to ask for the execution plan :

SET SHOWPLAN_TEXT ON

GO

Select 'query here'

GO

SET SHOWPLAN_TEXT OFF

For the ones wondering how we found out about that (no Phil is not the first one to notice it... the original informant desires to stay anonymous), check out their...

Remember that it's a smalldatetime datatype. Maybe it was just by a second but it got rounded up... those damn memory exceptions .

HTH, sorry to hear about your mother. I hope she'll be doing better soon.

Good point, it's their fault .

I'll try to finish my thaughts on this one tomorrow. Drop me a line if I forget to.

No. The only case where I'd find that "acceptable" is when the data is the other databases is unsafe and that it could cause errors in the transfer. ...

What's the question??

Sure, if calling a split function twice is too hard to understand, I certainly see your point. Sorry if I rubbed you the wrong way, wasn't my intention.

IIRC, I...

I don't think he meant cross-tab, but nice exemple .

Oh we are enjoying .