Comments
-
This is very quickly becoming a must have.
-
How about taking your query and putting it in a materialized view instead? Would be expensive to set up the first time, but one time run for existing data. (Do understand the drawbacks of this before doing it though!)
-
We played with Co Pilot a bit. It is frightening what it can do with just a basic schema of some tables loaded. Without a foreign key, primary keys or anything, it correctly wrote an ON statement like this: on tblA.ID = tblB.SomethingLongWithoutAnID. The good thing, maybe it will eliminate ORM.....
-
And dang sometimes it is hard to get those RTO/RPO numbers out of management. Also number of databases on a server factors into how often we do backups. 15 minute intervals when you have 500+ databases on a server (total size a bit shy of 20TB) gets taxing on the system. It Depends indeed.
-
This DB was upgraded from 2014 to 2022. Ran it in 2014 compatibility level for 2 weeks, with Query Store on Changed it to 2022 compatibility level, manually forced a few query plans. Ran it this way for a week Unforced all plans and turned this on. We have not had it make a bad decision yet.
-
I'm a huge fan of native backups, just makes things easier all around. But.... we use Managed Backups on our Azure IaaS servers, which does use BACKUP DATABASE, but automagic scheduling. Besides it making SQL Agent crash after 10 days if you have too many databases, and lack of a Differential Backup option, it works pretty…
-
Strangely enough.... how to become a better cook, i.e. eat healthier. Database wise, more tuning to be able to save some money in Azure.
-
Class mate from 1st to 9th retired at 48 with her husband, bought a sailboat, and been sailing around the world for the last 5 years. Just the two of them. Picked it up in Turkey, over to the Canary Islands, then to Bahamas. Taking their time enjoying life.
-
Low year for me due to prioritizing pure vacations. Did Summit, and spoke in person at the Raleigh user group.
