[2003-12-15] Manage Multiple SQL Server Installations and Databases with OSQL
At one point in time I was tasked with running over 70 databases on more than a dozen servers without any of the costly third-party tools that exist to accomplish such tasks, and I often get asked how can you handle such large numbers of databases. This is a short article that will show you how to use the handy OSQL command line utility, provided with SQL Server, to execute repetitive tasks against large numbers of databases or to manage large numbers of servers.
[2003-12-15] How to Interact with SQL Server's Data and Procedure Cache
As you have worked with SQL Server, you probably have run across the terms data cache and procedure cache, and may have wondered what exactly a cache was. SQL Server is configured to use a physical pool of memory on the server, and it will allocate the majority of this memory pool to hold data pages that have been read, along with the compiled execution plans for all previously-run Transact-SQL statements. It is this dynamic pool of memory that is being referred to by the data cache and procedure cache. Before SQL Server 7.0, the data cache and procedure cache were two separate pools of memory and could be controlled separately. In SQL Server 7.0 and SQL Server 2000, one pool of memory is used both for data and execution plans.