242 reputation
16
bio website hoyt.us
location St Louis, MO
age
visits member for 1 year, 11 months
seen 5 hours ago

I've been an generic Microsoft applications developer for 17 years. I started out doing simple Access 1.x programs (many years ago). For the last 10 years, I've primarily worked with various versions of .NET and SQL Server.


Jul
2
awarded  Curious
Jun
13
comment How do I find out *why* a user has certain effective permissions?
Awesome question. I've been trying to figure this out for a very very long time. fn_my_permissions kinda works but often shows permissions that I cannot track down to an origin.
May
1
comment SHRINKFILE best practices and experience
To thrown in my 2 cents, I do occasionally shrink a data file but only when a large amount of one off data has been dumped into it then subsequently deleted resulting in a huge amount of free space. I'll agree that leaving the free space there won't cause any direct issues (except for drive space); however, if you need to backup/restore this same database to a smaller test/dev environment you may well be in a position where this is simply not possible. If you are never going to use the space again and are willing to pay the penalty of rebuilding your indexes, I do not see any problem.
Mar
6
accepted Initializing Transactional Replication From Backup
Feb
6
comment SQL Server Linked Servers and Remote Statistics
Excellent idea. Thanks John!
Feb
6
accepted SQL Server Linked Servers and Remote Statistics
Feb
3
asked SQL Server Linked Servers and Remote Statistics
Nov
12
awarded  Popular Question
Oct
8
comment Dropping Hypothetical Indexes
Hi Sam. Unfortunately this brings me back to the start. The script shows me the hypothetical indexes and give me the correct drop statement which I've been using all along. The problem is that the drop statement simply doesn't work. I am of the belief that this is a bug in the engine and have pretty much given up on it. At some point, I'll take the tables out of production then drop/recreate everything from scratch. I know that will fix it!
Aug
7
awarded  Yearling
Jun
21
comment Dropping Hypothetical Indexes
Full checker is clean
Jun
21
comment Dropping Hypothetical Indexes
With hypothetical nonclustered indexes you use a drop stat for some weird reason. blogs.technet.com/b/anurag_sharma/archive/2008/04/15/…
Jun
21
comment Dropping Hypothetical Indexes
Yea... Im in SSMS and I've tried all the above multiple times. CheckDB is clean. I even tried doing it through o-SQL and SQLCMD hoping that using a different connection stack would break it free. I am throwing in the towel and living with it. At some point I'll drop and recreate the tables. That will definitely fix it!
May
22
comment Dropping Hypothetical Indexes
Thanks Mike. All of these are hypothetical so are not going to fall into any of these categories. Aside from this these are all non-clustered hypothetical indexes which are treated as a statistics for dropping. Ultimately they are not "real indexes".
May
22
awarded  Commentator
May
22
comment Dropping Hypothetical Indexes
Hi Jason. Run SELECT * FROM sys.indexes WHERE is_hypothetical = 1
May
20
asked Dropping Hypothetical Indexes
Jan
25
comment Last Known Successful DBCC CHECKDB
Martin, nobody else has chimed in and I'm satisfied with your answer. Can you post this as an answer so I can give you credit?
Jan
18
comment Last Known Successful DBCC CHECKDB
Martin, please put your response as an answer so I can give you credit.
Jan
18
comment Last Known Successful DBCC CHECKDB
Thanks Martin. You are right. It must depend on the level of corruption. I needed to run UPDATEUSAGE on the database. Once I did that it was all good.