277 reputation
210
bio website hoyt.us
location St Louis, MO
age
visits member for 2 years, 7 months
seen Mar 26 at 18:22

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.


Feb
9
comment SQL Server: Invalid Log Scan Number (…) passed to log scan in database (…) is not valid
Thanks Dan! I saw this when you posted it but forgot to say something. We are planning to do this over the weekend.
Feb
1
awarded  Teacher
Jan
31
answered SQL Server: Invalid Log Scan Number (…) passed to log scan in database (…) is not valid
Jan
31
awarded  Editor
Jan
31
revised SQL Server: Invalid Log Scan Number (…) passed to log scan in database (…) is not valid
deleted 8 characters in body and bulleted artical search
Jan
31
asked SQL Server: Invalid Log Scan Number (…) passed to log scan in database (…) is not valid
Dec
8
comment Don't rebuild indexes < 1000 pages - then why bother having them?
I would tend to believe the guy that wrote the DBCC commands that actually do the shrinking (e.g. Paul Randall) over anyone else.
Dec
8
awarded  Notable Question
Sep
28
awarded  Popular Question
Sep
24
awarded  Autobiographer
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