Reputation
1,187
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
2 10 29
Impact
~84k people reached

  • 0 posts edited
  • 2 helpful flags
  • 81 votes cast
Jul
4
comment Is select * still a big no-no on SQL Server 2012?
At the end of the day pulling back data you don't need is wasteful. /EndOf really.
Jul
3
comment Is select * still a big no-no on SQL Server 2012?
@RobIII In essence it's a select *, i've updated to clarify, thank you. The less you ask SQL Server to do the better for everyone, yes you should consider lazy loading etc, but if you need 1/2 properties why pull back the whole table? Especially if that table contains a large entity such as an image. The correct 'solution' should be tested, measured and evaluated in a development environment.
Jul
2
comment Is select * still a big no-no on SQL Server 2012?
@rotard its not in the table itself, I meant the actual resolved entities. So if I dont need property x which is a 1024 length byte array, then I dont need to retrieve it from the database. Thus, saving memory from RAM. Hope that clears it up.
Jul
1
comment Is select * still a big no-no on SQL Server 2012?
@rotard I've added a sample for you :)
Dec
16
comment Difficulty in finding Candidate Keys
re-tagged as homework
Dec
13
comment DELETE vs TRUNCATE
Thanks for all the links to the other questions all :)
Dec
8
comment case versus isnull versus coalesce
Thanks for the complete answer so quickly. I had no idea that the order of precedence mattered for COALESCE. Thanks again
Dec
8
comment case versus isnull versus coalesce
related I agree. but not dup. Thanks for the comment :)
Nov
29
comment When should a primary key be declared non-clustered?
there are only two other answers to read... thanks for your time to answer mind.
Jul
15
comment Tempdb autogrowth settings
Got that down on my to-do list. Sys-admins are going to love me on Tuesday when im back in the office :D Thanks for the link.
Jul
15
comment Tempdb autogrowth settings
Yes it does, thanks for the insight. :)
Jul
15
comment Tempdb autogrowth settings
Typically in the environments I work in, SQL Server is generally placed on a multi-purpose server. So SBS might be on the box as well so I have to keep these things in mind. I am definitely an accidental dba (developer by trade) and your comments are much appreciated. I will have to come up with sensible defaults for each environment. Thanks
Jul
15
comment Tempdb autogrowth settings
Thanks for the links. It would be great if that trace flag could be configured for just one database
May
28
comment Does SQL Server evaluate functions once for every row?
Thanks for the link and explanations :)
May
23
comment Is it recommended to clear the query plan cache
Thanks for the discussion guys. It's been most helpful :)
May
22
comment Is it recommended to clear the query plan cache
Probably no more than 15% for this one query. Don't have access to the server at the moment to check
May
22
comment Is it recommended to clear the query plan cache
Not sure if you saw the edit I put on as you were writing but most of the top queries are like SELECT blah FROM t WHERE param = 1 then param = 2 and so on... Does that affect your answer? Sorry if it does, you were too quick :P
Feb
15
comment Output into temporary table
Thanks. Fancy putting that in an answer :)
Dec
28
comment Table value functions vs UDF SQL Server
Didn't see the duplicate :/ my bad
Nov
29
comment Over use/correct use of schemas?
I usually sort out permissions at the end of development as we have somewhat "fluid" specifications at times. Is this how you do it? Or do you assign permissions as you create the objects etc