(Ron Talmage) SQL Server DBAs often find themselves importing and massaging data using T-SQL. Why? Because some transformations of the data simply require the power of full-fledged SQL. Having just recently survived yet another case of data importing, I was inspired to assemble a list of do’s and do

Using SQL Server 2000 and above versions you can retrieve data from SQL Server in XML format directly from the database. Many XML related features were incorporated in the SQL Server database. This enables the development of XML enabled applications very easy and it makes exchange of data over inter

When you run a query against a view in Microsoft SQL Server 2000, the results of the query may be returned much slower than you expect. You may experience this problem when the following conditions are true: • The query that you run includes a GROUP BY statement. • The database on which you run

(Krishna Prasad V.R.) In SQL Server reporting services you can use custom assemblies, which gives your report a feature to add more functionality using any language of your choice. This can be done by referring the custom assembly in the Report properties-> References window in the Report Designer.

Consider the following scenario: • You run Microsoft SQL Server 2000 together with the full-text search component. • You start the Microsoft PKM Search Filter Daemon (Mssdmn.exe) to parse Microsoft Office Word documents.

Nine new webcasts are scheduled for August, covering such topics as New Features in Indexing, SQL Server 2005 Express Edition, Implementing Application and Data Security and more.

(Jeremy Kadlec) When it comes to raw database performance, one of the biggest performance gains can be achieved through beneficial indexes. The indexes improve access to the data so you don’t have to scan an entire table, a costly endeavor in terms of CPU, IO and memory usage. Over time, indexes can

In Microsoft SQL Server 2000, some queries against indexed views may run slower when one of the following conditions is true: • You install a SQL Server 2000 post-Service Pack 3 hotfix or a SQL Server 2000 post-Service Pack 3a hotfix, and the hotfix is build 2000.80.811 or a later build. • You

Consider the following scenario. You install Microsoft SQL Server 2000 Service Pack 4 (SP4). Then, you run the Sqldiag.exe utility. In this scenario, a Buffer Overrun check dialog box appears, and you receive the following message: Getting registry information.

(Jayaram Krishnaswamy) As businesses may have more than one SQL Server holding their data, it is of interest to know the technique of connecting to mulitple servers through saving connection information in the configuration of the application. In fact, it is a recurring question in several forums. T