A Fine Slice Of SQL Server
Rob Sewell does a bit of testing:
A contained user can create a Windows login as its own account, although as it cannot grant connect permissions it is then is unable to connect at all.
So if your vendor application is running as a contained user and during an upgrade it tries to create a login for itself, it will succeed in the creation but then be unable to connect to the SQL Server instance and the upgrade will fail.
Click through for the context and the proof.
Leave a CommentStephen Planck turns the page:
Most of the time, corruption in SQL Server is either nonexistent or so widespread that you have no choice but to perform a file or full‑database restore. Yet an awkward middle ground exists: a handful of pages—perhaps only one—become unreadable while the rest of the database remains perfectly healthy. A full restore would repair the damage, but at the cost of rolling back hours of work and locking users out of an otherwise functional system.
That is precisely why Microsoft built RESTORE … PAGE. When you meet a short list of prerequisites (FULL or BULK_LOGGED recovery model, an unbroken backup chain, and a page that is not allocation metadata), you can surgically overwrite just the bad 8‑KB chunks, roll them forward with transaction‑log backups, and return the database to service in minutes rather than hours.
Read on to see how it all works, as well as situations in which this isn’t the right answer.
Leave a CommentReitse Eskens shows off Microsoft Fabric’s Monitor hub:
When we create a data solution for our company or clients, we create the best, right? Sure, we do. But still, monitoring the solution is something you should never forget. Your solution can be stable, but the data usually isn’t. And it just feels good to know all the data has been processed correctly.
So, let’s dig into monitoring Microsoft Fabric.
Read on to see how it works, as well as plenty of thoughts, advice, and critique from Reitse.
Leave a CommentWhen describing Oracle features to folks that are new to the platform or coming from other database platforms, I found it’s best to keep it simple, but take on the important aspects of the technology. I’m going to take on a few more posts on Oracle internals from the perspective of the individual new to Oracle.
To start, I’ve been having some long discussions, as well as documenting how Oracle memory works and how we monitor it when you don’t have the diagnostic and tuning pack at your disposal. With the exclusion of these management packs, you have to be intentional in your queries to provide the data, without violating the licensing by using the %_HIST_% views.
Click through for an overview of how Oracle makes use of memory and how you can monitor this usage.
Comments closedRyan Booz continues a series on pgNow:
In that first article, I shared how pgNow can be a lifesaver when you need immediate performance insights, highlighting features like query tuning and current activity monitoring. The tool’s ability to take periodic snapshots of query activity and spotlight active sessions has already been a significant help for early users.
Today, I wanted to look at another area of information that pgNow can help you explore during times of performance degradation or even as part of a regular database maintenance and hygiene: the Indexing tab.
Click through to see what’s in the feature and to get a free copy of the preview for pgNow.
Comments closedAndrea Gnemmi looks at a pair of extensions:
We all know the importance of monitoring our RDBMS to ensure the performance and availability. Are there any tools that provide functionality to better to monitor PostgreSQL databases? In this article we will explore pg_stat_activity and pg_locks.
Click through for an overview of these two extensions and some of the functionality available in them.
Comments closedJess Pomfret looks for old tables:
There are many reasons why you might end up with tables named
something_oldin your database. Perhaps this is part of your decommission strategy, to rename them to make sure they really aren’t in use. Or, it could be because you need to make schema changes, you can rename the current table and create a new table with the desired schema. But, the key to this blog post is when you then forget to come back and clean these tables up. We can easily find them with a dbatools command.
Read on to see how you can use dbatools cmdlets to find and remove these deprecated tables.
Comments closedFederico Campoli deals with a lot of RAM:
Nowadays it’s not uncommon to deal with machines with hundreds of GB of RAM.
Abundant memory can give PostgreSQL a massive performance boost. However things work slightly different than you may expect.
Let’s find out!
Click through for a dive into how PostgreSQL handles memory management.
Comments closedI have noticed new SQL Server database objects have been created and want to know how we can track down who created these objects. What options are available in SQL Server? In this article, learn how in SQL Server to check who created a table or other objects.
Burt shows a couple of techniques for this, though I’d lean heavily on using Extended Events over a server-side trace or Profiler for the task.
Comments closedKevin Hill explains those hidden costs:
Common Excuses That Lead to Expensive Problems:
- “Our system runs fine,”
- “The cloud takes care of it”
- “Our sysadmin is really smart”
- “DBAs are expensive”
Read on for thoughts around why it’s important to have a DBA, and why just having a junior DBA may not be sufficient.
Comments closed