Key Performance Indicators are typically displayed in a scorecard with stop light indicators, which are either red, amber or green light icons. The limitation for these kind of indicators is that you can see the actual and target values in two different fields as well as see the status of the KPI in red, amber or green color. If the user wants to figure out the thresholds associated with the KPI, these values are generally not visible. Further, representing the threshold values in the scorecard itself defeats the purpose of the scorecard. The scorecard should display the KPI's status in the most summarized form and use a minimal amount of space on the dashboard. In this tip we would look at how to address this issue.
Today Steve Jones talks about a new use for cloud computing with Excel to analyze large sets of data.
Unstructured and XML semi-structured data is now used more than structured data. But fixed structured data still keeps businesses running day in and day out, which requires consistent predictable highly principled processing for correct results. For this reason, it would be very useful to have a general purpose SQL peer-to-peer collaboration capability that can utilize highly principled hierarchical data processing and its flexible and advanced structured processing to support dynamically structured data and its dynamic structured processing. This flexible dynamic structured processing can change the structure of the data as necessary for the required processing while preserving the relational and hierarchical data principles. This processing will perform freely across remote unrelated peer locations anytime and transparently process unpredictable and unknown structured data and data type changes automatically for immediate processing using automatic metadata maintenance.
It seems that archival isn't on the mind of most designers when they first build a database, which is OK, but DBAs ought to be building skills to implement this if the data size grows large.
This week Steve Jones notes there were quite a few patches from Microsoft for a variety of products. No SQL Server specific security patches, but that doesn't mean that DBAs shouldn't be patching systems.
Of all the technical solutions to the problem of slowly changing dimensions, the T-SQL MERGE statement is one of the most elegant.
Identifiers aren't locators, and they aren't pointers or links either. They are a logical concept in a relational database, and, unlike the more traditional methods of accessing data, don't derive from the way that data gets stored. Identifiers uniquely identify members of the set, and it should be possible to validate and verify them. Celko somehow involves watches and taxi cabs to illustrate the point.
Come to Indianapolis on June 25, 2011 for a free one day training event on SQL Server.
By Steve Jones
I wrote about learning today for the editorial: I Can’t Make You Learn. I...
By ReviewMyDB
Fabric has CI/CD built in, but if you've tried to use it for database...
By Steve Jones
attriage – n. the state of having lost all control over how you feel...
WA:0821-4447-7715 Jl. Veteran No.18-24, Krembangan Sel., Kec. Krembangan, Surabaya, Jawa Timur 60175
WA:08218154393 Jl. Jend. Sudirman No.49-51, Terban, Kec. Gondokusuman, Kota Yogyakarta, Daerah Istimewa Yogyakarta 55223
WA:08218154393 Jl. Kisamaun No.57, RT.001/RW.006, Sukasari, Kec. Tangerang, Kota Tangerang, Banten 15118
I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?
See possible answers