This paper explains how batches are cached and reused in SQL Server 2005, and suggests best practices on maximizing reuse of cached plans. It also explains scenarios in which batches are recompiled, and gives best practices for reducing or eliminating unnecessary recompilations.
2005-01-31
1,234 reads
Many Enterprises create and maintain applications that reside on "IBM Lotus Domino Server." Since the Lotus Domino server has the capability of handling applications and messaging, it has become a prime requirement for a SQL Server DBA to cross- reference data or import and export data to and from the Domino database and SQL Server databases. In this article, I am going to discuss how to use SQL Server Linked server to connect to databases that reside on the Lotus Domino server. The steps involved in connecting to the Lotus notes mail server database can be used for connecting to other databases that reside in "Lotus Notes Domino" server.
2005-01-31
2,430 reads
When a DBA is managing many different SQL Server boxes, it can be a tedious job to find the port numbers used by all of the SQL Servers. In this article, I would like to discuss several methods for finding the Port numbers used by SQL Server.
2005-01-28
1,942 reads
Microsoft SQL Server Reporting Services is a powerful new tool allowing developers to move reporting solutions online for truly global access. This paper explains the key advantages, similarities, and differences between Microsoft Access reports and Reporting Services reports for organizations considering migrating to Reporting Services. (22 printed pages)
2005-01-28
1,323 reads
I recently ran into a need to run a report in SQL reporting services from the command line. The Report took four (4) input parameters and I had to export it to Microsoft® Excel and save it to disk. I had to rummage through the product documentation and the Microsoft® SQL Reporting newsgroup to get this right. For running reports from the command line, SQL Reporting services provide a utility called “rs utility”.
2005-01-26
2,602 reads
Detailed error reporting from stored procedures can be extremely valuable when debugging problems in your application. I will share different levels of detail that you can build into your stored procedures. You can choose the level of detail appropriate for your situation.
2005-01-25
2,903 reads
Table partitioning is a powerful new feature in SQL Server 2005. It is primarily a manageability feature, but my interest here is in the performance and scalability of table and index partitioning for use with very large tables.
2005-01-24
1,462 reads
Databases are being stolen. Customer data, credit card data, taxpayer data - they're all vulnerable. Scary? Yes - but wait, there's more. It's not just "their" data that's vulnerable - it's ours too!
2005-01-21
2,107 reads
Fabian Pascal, famed database author and writer takes his shots at a recent thread on another SQL site. He makes some good points about normalization.
2005-01-20
3,074 reads
SQL Server 2005 has added a new format for queries called a Common Table Expression or CTE. CTE’s are part of the SQL:1999 Specification and represent further compliance with this specification by SQL Server. This article will cover using one of the many capabilities of CTE’s, implementing recursive functions. A recursive function is a one that iteratively executes itself. Understanding how CTE’s implement recursive functions is the first step to understanding the full capabilities of CTE’s.
2005-01-19
1,858 reads
By HeyMo0sh
As someone who’s worked with data for over 20 years and with many cloud...
By HeyMo0sh
2025 belongs to the AI startups. If you peek into the tech headlines, you’ll...
By Vinay Thakur
it has been a year since i have not written much on the blog...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers