Jobs are pretty basic aren't they? They are until you get a couple hundred, or a thousand. Andy continues talking about managing jobs by standardizing how you handle notifications and failures, and talks about an interesting idea to monitor jobs separately from SQL Agent. Worth reading!
This article by new contributing member Bob Musser shows you how to reduce the amount of scans that SQL Server Agent does against databases. Not for the faint of heart.
An interview where they discuss their data strategy and integration with Visual Studio .Net
Although there are legitimate reasons for using filegroups, Chad Miller recently encountered a situation where they were used too much. He shows you in this article why and how to remove excessive filegroups.
In SQL Server 2000, there is a database option to close the database when it is not in use. Every wonder what this is? Or when it should be used? Steve Jones takes a look at this seldom used option.
There are times that you may find yourself on a project where you have one data source and need to publish to many subscribing databases. Often times, Replication is not looked at as a viable solution to achieving this goal. For this project, Demico and Lynn will demonstrate the way we utilized the Horizontal and Vertical partitioning capabilities that Microsoft has added to the Replication utility.
I've had to call Microsoft quite a few times for support this year. Was it worth it? Read on to see when you should decide to call.
In the previous article, you saw how the BETWEEN operator could be used in joins to solve problems dealing with range-based data. In this article, Chris Cubley will show you how to take joins even further by using multiple criteria in joins as well as using the greater than, less than, and not equals operators in joins.
Your software has passed all testing phase(s) and it is time to install your database into production. Andy Jones will outline below how he accomplished this task. This article is concerned with an evolving system and how to migrate it to production.
Last week the SQL Sapphire (or SQL Slammer) virus hit corporate networks throughout the Internet. Although damage has not been estimated yet, it is sure to be in the tens of millions of dollars. So who is to blame when a virus like this manhandles a corporate environment?
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
A while back I wrote a quick post on setting up key mappings in...
By Steve Jones
In 100 years a lot of what we take to be true now will...
Comments posted to this topic are about the item Lots of FKs
Comments posted to this topic are about the item Real-time On-prem SQL Server Data...
Comments posted to this topic are about the item Can You Let Go of...
In SQL Server 2025, what are the most outgoing and incoming FK references a table can have?
See possible answers