Viewing 15 posts - 44,926 through 44,940 (of 59,095 total)
I'd still like to know why we're spelling out dates. What are the business rules that would require such a thing?
Also, just a friendly tip... you don't need a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 5:50 pm
Can you post the actual code you tried? The code you posted has no percentage calculations in it.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 5:47 pm
GilaMonster (2/27/2009)
Jeff Moden (2/26/2009)
[Great minds think alike... 😛 modeled very close to what the query designers in 2k and 2k5 spit out... makes it easier for "coders" to comply.
Not...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 5:34 pm
Max (2/27/2009)
GilaMonster (2/27/2009)
Max (2/27/2009)
Always wondered of there was an overhead with using equal aliases though.No, but it is deprecated syntax
Pity, it's grown on me and quite like it, somehow...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 5:31 pm
Cool... thanks for the feedback, Roy.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 5:16 pm
Mark (2/27/2009)
Pretty much exactly what we do, I really don't like underscores...Seems to be a common convention, don't know where it originates.
Oracle... when code is autogenned, it comes out in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:28 am
Adiga (2/26/2009)
Jeff Moden (2/26/2009)
Can't use -E from a command prompt... only from SQL Server.
I disagree with this. I have tried using -E (Trusted connection) and it works well...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:22 am
Can't use -E from a command prompt... only from SQL Server. Where are you trying to run the OSQL command from?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:28 pm
If the nested proc only works on one row at a time... "Death by SQL". 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:23 pm
Just curious... why do you need to do this?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:14 pm
Heh... must be a one way street... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:13 pm
Use this as a source of rowcounts, instead of all that RBAR and counting...
/**********************************************************************************************************************
Purpose:
Returns a single result set similar to sp_Space used for all user tables at once.
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:07 pm
If column one contains, say, whole numbers greater than zero and you want the index seek without contraining column 1 to a single value, the following will usually all it...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:01 pm
Keeping in mind that a "Page" is 8KB, you could try this and get some pretty good information about the table and all of it's indexes... all at once...
DBCC SHOWCONTIG...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:49 pm
Lookup "deadlocks [SQL Server], avoiding" in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:32 pm
Viewing 15 posts - 44,926 through 44,940 (of 59,095 total)