That was quite the saga alright. It isn't quite right though - they were supposed to dig a sunken area and put the hot tub in it, but when they were "all done", they brought the hot tub in and... the sunken area wasn't dug large enough. (sigh)
@9:48 ApplicationIntent=ReadOnly as a client connection property is the closest you will get to "forwarding" reads to the secondary replica. Caution tho that will require Enterprise SQL and configuring read only routing on a AG listener.
Regarding question about Index and "why was it created?". I'm not sure if it's applicable to dbs, but in app development all the code is tracked in VCS. For instance, with EF Code First, you would not have a Jira ticket in the index name, you would have your db versioned in VCS as well. Then, if you have a question "why was IX_Name_Name_Name created", you search for IX_Name_Name_Name in your VCS and it brings up the commit which introduced it in the first place. Each commit should have a reference to a Jira ticket in its message and/or come from a branch named after the corresponding Jira ticket. Apart from that, wonderful QA, thanks Brent for those.
Depends on what kind of reality you’re living. If you’re in a situation where all index tuning is done by developers, that’s a great solution. If your index tuning is at least sometimes done by DBAs that aren’t on board with your DCM (database change management) solution, then it’s unreliable at best. However, if your index tuning is done by DBAs who ARE on board with your DCM solution, then you’re back to happyville.
