Viewing 15 posts - 1 through 15 (of 77 total)
I worried about using these undocumented procs as well and thought the biggest fear was the global cursor it employed. I modified it to use a dynamic local cursor...
April 15, 2016 at 8:48 am
Not to pick on the article too much further since it appears much has been said already but to me it seems the first sentence is off and that always...
February 9, 2011 at 12:27 pm
For fun 2 slight variations based on Kingston's.
DECLARE @strVariable VARCHAR(100)
SELECT @strVariable = '| hello | world | I love sql server'
SELECT CASE SUBSTRING(@strVariable, 1, 1)
November 18, 2010 at 3:58 pm
September 3, 2010 at 11:47 am
This is often overlooked but for all your variables that are nvarchar it is a good practice for you to be adding the pre-pended 'N' to the hardcoded string parts...
August 31, 2010 at 10:23 am
Sean Elliott (UK) (8/21/2010)
August 22, 2010 at 2:27 pm
Cool stuff, this type of auditing can really come in handy.
However, I am surprised to see @@ERROR\GOTO used as the error handling mechanism in these scripts instead of...
August 19, 2010 at 7:59 am
Jeff Moden (8/12/2010)Someone already said it... I'd love to read that article. Would you post the URL on this thread so we can take a peek? Thanks, Joe.
Jeff Moden (8/12/2010)
Someone already said it... I'd love to read that article. Would you post the URL on this thread so we can take a peek? Thanks, Joe.
August 13, 2010 at 12:22 pm
Lynn Pettis (6/25/2010)The way you are using ROWCOUNT has been depreciated and may not be supported in future versions of SQL Server.
Lynn Pettis (6/25/2010)
Did you mean to say depreciated? Or did...
June 30, 2010 at 11:39 am
ken.trock (6/18/2010)I prefer Hungarian notation with only the 1st letter capitalized but I see that SSMS intellisense is promoting all caps for keywords. Didn't know about Ctrl+Shift+u, nice little trick.
June 18, 2010 at 12:14 pm
'M' is a name already taken for a language. M is the name for the language once called MUMPS.
June 14, 2010 at 3:24 pm
Some other things to improve on the code might be:
Get rid of the return statement after the raiserror since it can never be hit when raising severity level 16
June 11, 2010 at 12:42 pm
Software Engineer, currently working with .NET and SQL Server. I have had to do a lot of database work in the past and now. Never been a DBA....
June 8, 2010 at 2:17 pm
Atif Sheikh (5/27/2010)For checking the flow of T-SQL code in SSMS, PRINT statement is fine. For debugging, another option is RAISERROR. You can check the details @ http://www.sqlservercentral.com/articles/SQL+Puzzles/quickhintsforusingtheraiserrorcommand/2114/
Atif Sheikh (5/27/2010)
That is a...
May 28, 2010 at 10:51 am
Another way to calculate the age is:
SELECT (ABS(CAST(CONVERT(char(8),GETDATE(),112) AS int)
- CAST(CONVERT(char(8),@DOB,112) AS int)) / 10000) [AGE];
Here is a link to where I originally saw...
May 28, 2010 at 9:00 am