These are not the DMO bits you are thinking of from SQL Server 2000. SQL Server 2005 introduces a new way of digging into the inner workings of the server with both Dynamic Management Views and Dynamic Management Functions. Longtime SQL Server guru Christoffer Hedgate looks at these new ways of understanding your server.
Trying to find the proverbial needle in the haystack of your SQL Server transactions is no small task. SQL Server Profiler not only helps you find that needle, it gives you details on all the other needles in a single interface.
The aggregate functions in SQL Server (min, max, sum, count, average, etc.) are great tools for reporting and business analysis. But sometimes, you need to tweak them just a little bit to get exactly the results you need. For example, if your manager came to you and asked for a report on how many sales have been made to your clients and how large they were, would you know how to get the data you need efficiently? Mark ran into something like this recently and here's the approach he took to solve the problem.
Haindong Ji brings us part 3 of his series on Oracle and SQL Server interoperability, this time taking a look at the Oracle Instant Client.
Database Snapshot (DB Snapshot for short) is a new tool offered by SQL Server 2005. Database snapshots can be used to protect against user errors, by creating a "snapshot" of your data that you can refer to later if you need to recover data or database objects that were accidentally (or even intentionally) updated or dropped. While the feature is quite useful, it doesn’t provide a 100% guarantee against user errors.
The new central tool for SQL Server 2005 is the SQL Server Management Studio and you can do most anything with it. Learn about this new utility and get a head start on SQL Server 2005 with a new book from SQLServerCentral.com by Dale Elizabeth Corey.
This example shows you how to cleanse data to look more modern in SSIS using the Script Component in transform-mode. It shows you how to make the first letter of every word capitalized from data that's in an unknown state.
Do you have a Web site or other system that deals in secrets of any sort? It seems like every time I give a security talk, people ask how to deal with the sticky problem of storing secrets. Connection strings with passwords are an obvious problem. You're better off simply using integrated security to get rid of those secrets, at least with SQL Server™, or an Oracle database. But what about credit card numbers and other financial or personal information? Can encryption help?
When considering business intelligence (BI) software, it is essential to be aware of underlying issues that can seriously impact on your bottom line. In a country where most businesses have information stored in several different databases, it’s no secret that the BI strategy you choose will effect your profit and loss target. From data collection and integration to data analysis, the holy grail of Business Intelligence software combines your disparate databases to provide a decision support system that will enable you to make key conclusions using all of the available information.
The guys that build software rarely get exposure of credit. Maybe that's why so many of them turn to open source where they get more well known. After a meeting at TechEd 2005, Andy Warren had the chance to get some interesting interview questions answered by Brooke Philpott, one of the 2 core developers of sqlSentry. And not a marketing guy.
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
When mirroring was first released for Azure SQL Database, it used Change Data Capture...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
Comments posted to this topic are about the item Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers