Reputation
1,197
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
2 11 30
Impact
~88k people reached

  • 0 posts edited
  • 2 helpful flags
  • 81 votes cast
Jul
15
awarded  Popular Question
Jul
6
awarded  Yearling
Apr
2
awarded  Famous Question
Dec
18
awarded  Notable Question
Dec
17
awarded  Popular Question
Dec
9
awarded  Notable Question
Sep
22
awarded  Nice Question
Aug
18
awarded  Popular Question
Jul
25
accepted Implementing application locks within SQL Server (Distributed Locking Pattern)
Jul
25
awarded  Popular Question
Jul
24
awarded  Custodian
Jul
24
reviewed Approve Implementing application locks within SQL Server (Distributed Locking Pattern)
Jul
24
asked Implementing application locks within SQL Server (Distributed Locking Pattern)
Jul
6
awarded  Yearling
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
3
revised Is select * still a big no-no on SQL Server 2012?
added 12 characters in body
Jul
3
awarded  Nice Question
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
2
awarded  Curious