790 reputation
413
bio website
location Finland
age
visits member for 2 years, 1 month
seen 2 days ago

Former ASP.NET Web Forms developer of 2 years, I'm currently working as one of the DBA's in a large project. TSQL scripting has become an increasingly interesting subject to me on a personal level, as I thoroughly enjoy doing it.


Nov
19
revised Procedure permission issues with a SQL state query
added 173 characters in body
Nov
19
comment Procedure permission issues with a SQL state query
Thanks for the suggestion. This was actually among the first alternatives I was thinking, and what I'm still considering if there's no cleaner alternative. But in this case, I'd rather avoid granting the SQLAgentOperatorRole and instead just create a scheduled job which would pass the information to a few tables every 1-5 minutes or so, allowing the DBO user to read the data from there. But it just seems unnecessarily complex just to get the results off of a few simple queries. :/
Nov
19
asked Procedure permission issues with a SQL state query
Nov
7
awarded  Popular Question
Nov
7
awarded  Yearling
Oct
12
comment SQL Server stuck in single_user with auto_update_statistics_async on
Finally got this resolved and opened the DB for MULTI_USER. A colleague disabled all external connections to the DB from software, which were trying to get in as well. Apparently it was just a question of odds. When enough contenders were took out, my loop for trying to set the DB back to MULTI_USER finally got through. I guess this is one of those lessons one will never forget. Thanks a lot for the help Martin!
Oct
12
comment SQL Server stuck in single_user with auto_update_statistics_async on
Thanks for the migration and edits. So far I've been unable to find anything to offer any alternatives, other than taking the instance down entirely, removing the DB files, bringing it up, deleting the DB, and creating it again from backup. The problem is, that server hosts other important DB's too so this is rather a way too drastic measure for a single DB.
Oct
12
asked SQL Server stuck in single_user with auto_update_statistics_async on
Sep
24
awarded  Autobiographer
Sep
19
comment SQL Server 2008 - How did I solve the need to check the column definitions quickly?
Ah nice to know! This is the trouble with creating general scripts from the perspective of a single - albeit large - database. :)
Aug
27
comment Outer Apply vs Left Join Performance
Logically, APPLY is called for every row in the left hand side of the query. In reality though, the execution planner will decide how to handle it in the context of the entire query, so it can sometimes be very hard to know beforehand whether a join or an apply will prove the better option. Best to just try both, compare their execution plans, see if you can make any adjustments, and go with that.
Aug
19
answered Simple SQL Query
Aug
7
comment AlwaysOn Secondary Replica DB-size
Thanks for the quick answer! Apparently sp_spaceused / sp_helpdb showed the space usage correctly after all. What got me confused was comparing them to a slightly older copy of the DB, which contained more unused space amounting to the same total space used. That combined with my not understanding the filesystem .mdf timestamps got me properly confused. Thank you for your time!
Aug
7
accepted AlwaysOn Secondary Replica DB-size
Aug
7
asked AlwaysOn Secondary Replica DB-size
Jul
29
awarded  Notable Question
Jul
28
comment INSERT/SELECT slow after TRUNCATE TABLE on table with 6 over mllion rows
As others pointed out, truncating basically leaves all statistics and indexes all outdated and fragmented. Also, if your table is basically a dump table for data, you might want to alter it as a heap instead of clustered (which I assume it is). Heaps are ideal for pretty much nothing, except for huge bulk inserts. Either way, to read data from there you'll need to update the statistics for the query planner to have any clue what the data looks like and how it's ordered.
Jul
25
revised Estimate projected database growth
deleted 146 characters in body
Jul
25
answered Estimate projected database growth
Jul
24
comment SQL Server NULL values UNDO
He's new, and inexperienced, and the question is valid for someone like that. So instead of this liberal "let's give attitude and vote down everyone new and vote up everyone with gold on their stats" how about we give the guy a break and do what this site was meant for: offer help? Namely, if you have access to another DB, excel, file etc with the same data with the WL:5 values (which is often the situation in test), you can use that to update everything WL:5 except those rows. Or as mehdi said below, just restore your last backup. And in the future, use rollback blocks to check first.