March 25, 2013 at 10:26 am
Really nice one to start my week. Thanks, Dwain!
March 25, 2013 at 10:32 am
Thanks for a great question!
Rob Schripsema
Propack, Inc.
March 25, 2013 at 4:08 pm
Nice question, thanks
Not all gray hairs are Dinosaurs!
March 25, 2013 at 6:23 pm
thanks for the question
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
March 26, 2013 at 1:21 am
mtassin (3/25/2013)
Good question, I lost count of GO statements... 🙁 knew where it would fail... but thought that was the 3rd batch, not the 4th.
🙂 I lost track of those go, myself.
--------------------------------------------------------------------------------------
Hai Ton
My Db4Breakfast blog.
March 26, 2013 at 8:12 pm
First I'd like to thank everybody that stopped by and left some kind feedback on the question.
Second, I'd like to apologize for not saying the above sooner but I've been kind of busy the last few days here preparing a customer demo.
Third, I've checked and found that Steve kindly fixed the issue with the last line of DROPs/GO, so hopefully that won't be confusing anybody else!
Thanks Steve!
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
March 28, 2013 at 7:53 am
dwain.c (3/24/2013)
kapil_kk (3/24/2013)
This wil also give error :DROP FUNCTION dbo.Test DROP TYPE dbo.MyTable GO
as GO is present at the same line where it should not be....
Alas I got wrong :w00t:
I'll refer you back to my answer to Tom's post just a little ways back.
Clearly that last line should appear as:
DROP FUNCTION dbo.Test
DROP TYPE dbo.MyTable
GO
I have requested Steve to fix it if he can. Hopefully it won't confuse too many others.
It appeared as three separate lines when I read it to-day (28th March) so it may have been fixed.
March 28, 2013 at 7:55 am
dwain.c (3/26/2013)
First I'd like to thank everybody that stopped by and left some kind feedback on the question.Second, I'd like to apologize for not saying the above sooner but I've been kind of busy the last few days here preparing a customer demo.
Third, I've checked and found that Steve kindly fixed the issue with the last line of DROPs/GO, so hopefully that won't be confusing anybody else!
Thanks Steve!
and then I saw this so I would say, yes, it has been fixed.
April 1, 2013 at 4:16 am
Nice question.
--
Dineshbabu
Desire to learn new things..
April 4, 2013 at 8:52 am
Dineshbabu (4/1/2013)
Nice question.
+1
Manik
Go Fast As Possible...
Manik
You cannot get to the top by sitting on your bottom.
April 18, 2013 at 1:34 am
Good question.
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply