August 11, 2013 at 6:44 pm
john.jones (1/25/2011)
We are going to use this.
For all of the rreasons previously stated, I strongly recommend that you don't.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 11, 2013 at 6:46 pm
sorry folks, I think you're all trying too hard. Think about it. People make mistakes. If an unwanted all-row update happens in a production environment, ok, stupid, and obviously not properly tested.
But you can't prevent every possible error. Live with it.
August 12, 2013 at 2:06 am
Hi Rahul,
I have i doubt on this query, if all the rows have "CASH" then how to work this query
August 12, 2013 at 2:10 am
Hi Rahul,
Thanks for your article, but I have a doubt on this query, if all the rows have "CASH" columns only, then how this query works ?
August 15, 2013 at 1:00 pm
Why not just compare @@RowCount against (select count(*) from TABLE)?
When I query sys.dm_db_partition for some of my tables I have multiple rows returned whose row_count is either <= count(*).
If I SUM these as the example shows the result is multiples of count(*).
And Everytime @@RowCount = count(*).
Viewing 5 posts - 91 through 94 (of 94 total)
You must be logged in to reply to this topic. Login to reply