November 14, 2011 at 6:33 am
Gianluca Sartori (11/14/2011)
With my powers of divination I foresee just a few more threads like this one and Gail taking a break from the forums again.:hehe:
I'm already taking a break. Notifications are auto-delete, visits trending down.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 14, 2011 at 6:39 am
Ninja's_RGR'us (11/14/2011)
Gianluca Sartori (11/14/2011)
With my powers of divination I foresee just a few more threads like this one and Gail taking a break from the forums again.:hehe:
I can handle him if that's really a problem :-D.
He's improving, but still doesn't test what he posts and doesn't research terms which he's unfamiliar with.
The one post that bugged me was when he posted saying "This code doesn't do what you think. Many get caught by this. This creates a procedure that alters another procedure when run because there's no GO or ;"
CREATE PROCEDURE p1 AS
SELECT 1
ALTER PROCEDURE p2 AS
SELECT 2
Actually that just throws a syntax error because ALTER PROCEDURE is not allowed within a procedure. 2 seconds taken to test would have shown that.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 14, 2011 at 6:42 am
p.s. A binding error (it can have other names) is thrown by the algebriser as it binds the query to the objects that it refers to. That's the phase after syntax check and parse and before optimisation. It's not a run-time error, it's not thrown by the query processor. It's not a syntax error because the parser (which does the syntax checks) doesn't care if objects exist or not, it just checks for valid SQL syntax.
That thread was, however, a bad place to mention that, because the OP's code there does actually throw a syntax error.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 14, 2011 at 7:02 am
Gianluca Sartori (11/14/2011)
Congrats Jason for winning T-SQL challenge 63!
Thanks - you were quick on that. I just got the email this morning.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 14, 2011 at 7:17 am
SQLRNNR (11/14/2011)
Gianluca Sartori (11/14/2011)
Congrats Jason for winning T-SQL challenge 63!Thanks - you were quick on that. I just got the email this morning.
Me too. Morning means night for you. 🙂
-- Gianluca Sartori
November 14, 2011 at 7:23 am
GilaMonster (11/14/2011)
Gianluca Sartori (11/14/2011)
With my powers of divination I foresee just a few more threads like this one and Gail taking a break from the forums again.:hehe:
I'm already taking a break. Notifications are auto-delete, visits trending down.
Does this mean you're not catching Steve anytime soon?
Don't be worried about hurting his feelings, as he can set up a trigger to be always 500 points ahead of you. 😀
-- Gianluca Sartori
November 14, 2011 at 7:32 am
GilaMonster (11/14/2011)
Gianluca Sartori (11/14/2011)
With my powers of divination I foresee just a few more threads like this one and Gail taking a break from the forums again.:hehe:
I'm already taking a break. Notifications are auto-delete, visits trending down.
... and the sun is cooling down, Earth stopped turning and rain is dry!
...but posts are going way up (might be because you were "off" at pass this time last month).
So I guess you're more effective this way. :w00t:
November 14, 2011 at 8:48 am
After looking at the link Remi posted, and noticing the MERGE answer there, I have to wonder. For a simple one or two table update like that, is MERGE really more effective then writing an UPDATE with a WHERE clause?
I'm just now starting to look up all the nifty new T-SQL features of 2008 (been putting out fires since the upgrade). Anything else I should put at the top of my "check this out" list with MERGE?
November 14, 2011 at 9:43 am
Brandie Tarvin (11/14/2011)
After looking at the link Remi posted, and noticing the MERGE answer there, I have to wonder. For a simple one or two table update like that, is MERGE really more effective then writing an UPDATE with a WHERE clause?I'm just now starting to look up all the nifty new T-SQL features of 2008 (been putting out fires since the upgrade). Anything else I should put at the top of my "check this out" list with MERGE?
I'd still use UPDATE in that case, but I have gotten away from using the FROM the clause with JOIN in most cases.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 14, 2011 at 9:43 am
Gianluca Sartori (11/14/2011)
Congrats Jason for winning T-SQL challenge 63!
+1, congrats
November 14, 2011 at 9:54 am
SQLRNNR (11/13/2011)
I find the practice of prefixing with tbl_ just a waste of 4 chars in a table name. It would be funny if a proc were prefixed with tbl_ though.:hehe:
I've ended up with too many tables prefixed with vw and views prefixed with t or tbl to consider it amusing any more. Just annoying.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 14, 2011 at 9:55 am
Brandie Tarvin (11/14/2011)
GilaMonster (11/14/2011)
SQLRNNR (11/13/2011)
I find the practice of prefixing with tbl_ just a waste of 4 chars in a table name.Likewise and a waste of time when typing in object explorer to find an object.
Waste of time or not, when you work in an environment that demands certain standards, you can either adhere to those standards or get traded in for a DBA that will do as (s)he's told. In an environment where there are multiple battles to be fought every day, using object prefixes is the least of my concerns.
Except in the case of "sp_" because of the side effects.
Yep.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 14, 2011 at 10:00 am
GSquared (11/14/2011)
SQLRNNR (11/13/2011)
I find the practice of prefixing with tbl_ just a waste of 4 chars in a table name. It would be funny if a proc were prefixed with tbl_ though.:hehe:I've ended up with too many tables prefixed with vw and views prefixed with t or tbl to consider it amusing any more. Just annoying.
Ok then let me throw something at you (never having had the partitioning issue).
How do you dev directly in a ERP that continuously updates itself and can destroy your objects? I have been told that they don't use prefix on views so that if I do, I won't have any issues.
Viewing 15 posts - 31,681 through 31,695 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply