Viewing 9 posts - 1 through 9 (of 9 total)
I don't think:
does what you intended. The square brackets indicate a list of characters, so it would be 'B' 'o' or 'b', rather than '[Bob]'. I think you...
October 4, 2011 at 1:14 pm
I know people like lists of myths, but I remember reading that the way our memories work is often context-free, and sometimes these lists reinforce the myths in people's...
September 1, 2011 at 1:26 pm
Another vote against addressing this with more legislation and regulation.
Regulations are rarely flexible enough to allow for reasonable distinctions, and always have unintended consequences.
There are plenty of established best-practices out...
July 18, 2011 at 11:53 am
It seems that you had just tried to supply the wrong number of columns in the original insert, and has nothing to do with newsequentialid() (it could have been any...
June 15, 2011 at 12:10 pm
Even though it has "Sequential" in name, the values themselves are not really adjacent to each other. It's just that the next value will be greater than any previous...
October 26, 2010 at 10:44 am
Maybe I'm missing something, but, I don't think you need @NextSequentialID at all, or the XxX column, or some other complexity in the table.
This seems to work:
CREATE PROCEDURE dbo.sp_NewSequentialId
October 19, 2010 at 10:46 am
But, if it contains both strings, you'll get it in the output twice. You may need a DISTINCT.
Also, you're not really using the CROSS APPLY functionality. This could...
September 16, 2010 at 12:15 pm
Did you want this?:
Set @qry='select column1 + ''_'' + column2 from '+@var1
Where '' is two consecutive single quotes.
April 30, 2009 at 11:12 am
I think this is another of those things that has always been pretty much the same, but always seems to be getting worse as we get older. It's probably...
August 25, 2008 at 10:47 am