Office Hours: Open Q&A on Microsoft Databases

[@TheRealSmendle]

@8:50 Visual Studio is actually great for this. 1. Create a blank SQL Server Database Project/Solution 2. Select TOOLS from the upper left menu options (from the file edit menu options) 3. Select SQL Server 4. Select New Schema Comparison 5. In the SELECT SOURCE dropdown....Connect to your Primary Instance 6. In the SELECT TARGET dropdown....Connect to your Secondary Instance 7. Select the OPTIONS gear button just above the SELECT SOURCE dropdown 8. DE-SELECT the Applciation-Scoped Checkbox 9. Drill open the Non-Application-scoped checkbox 9a. Choose your Instance level objects(Logins, Master Keys, Server Roles, triggers etc...) you want to move. 9b. Select OK 10. Select the COMPARE button just above the SELECT SOURCE dropdown. 10a. wait 10b. wait some more 10c. keep waiting until it is done! Once the waiting is over with you can choose which objects you want to move (they will be underneath the ADD folder) All objects found will be checked so if you want to be selected you will need to manipulate each line items checkbox in the MIDDLE of the row. Thank me later!

[@Variant55]

11:59 Could you add solar capacity? I mean this opens up a rabbit hole haha

[@jwfcp]

Solar might help, but it also has the problem of backwashing onto the grid in ways that are inconvenient for the power company, they want a new transformer for that anyway.

[@BrentOzarUnlimited]

No, we went down that road, but NV Energy makes it painful for scenarios like this.

I really like the business advice you slip into all the answers about making double sure who is responsible for what and keeping proof that you gave the person making money decisions all the information you could. But I also find many people don't communicate because they are afraid the receiver won't understand what they are saying. It is really not a good excuse not to communicate, at least they might understand they need a specialist if they don't understand anything you are saying. Try to make it understandable sure, but obfuscating what was difficult and why to make it simple doesn't seem to work great.

[@kebekoi11]

Weird that for example a 40amp level 2 charger on a 50amp circuit would kill the network. You don't need a level 3 50-150k$ supercharger at home. :)

[@BrentOzarUnlimited]

I know, right? The breakers are all maxed out though, and that's common with 20-25 year old Vegas homes. Pool pumps, hot tub, multiple air conditioners, home office, etc all added over the years.

[@3lp33l]

Why all this that AGs are so complex as it is something that is hard to get work perfectly? The MS documentation tells everything, there is of course quite a work to know and perform the work related to AD, but once done it just works. The environment I sat up (bascically 4 nodes used as 2 + 2 dedicated to db engine, SSIS/SSRS/MDS is hosted on it's own FCI cluster) just works and have been several incidents outside the SQL environment causing failover - it just works without further notice. The services are running with gMSA:s, and restricted Kerberos delegation is in place towards where it is needed. I don't think "complex" is the same thing as "a lot of work", it is quite a lot to keep in mind, but complex, no.

[@BrentOzarUnlimited]

Try troubleshooting AG latency. Go ahead, I'll wait. ;-)