(Arthur Fuller) Sometimes your application needs to know the specific directory where your database resides. It’s typically a front-end application that needs this information, but, occasionally, you may need it within a stored procedure. There are two ways to obtain this information: You can inspec
Tag: sql server
SQL Server 2005 Secures Your Data Like Never Before
(Don Kiely) If you care about your data, you must upgrade to SQL Server 2005 the day it is released. There simply is no other option.
Automatically Running a Process When SQL Server or SQL Agent Starts
(Gregory A. Larsen) Have you ever had a need to run a query or a process as soon as SQL Server starts? Or run some set of tasks when SQL Server Agent Starts? Possibly you want to run a cleanup routine, a copy process or have some task started each time SQL server or SQL Agent is started. Well, i
Query Analyzer: 10 tricks for simple querying
(Jeremy Kadlec) Back in the heyday of SQL Server 6.5, I remember writing many T-SQL statements in Enterprise Manager. Such was the case until Enterprise Manager locked up for the first time and I became a firm advocate for isqlw.exe. Also known as Query Analyzer, this tool has been my development an
FIX: The Mssdmn.exe process may use lots of CPU capacity when you perform a SQL Server 2000 full text search of Office Word documents
Consider the following scenario: • You run Microsoft SQL Server 2000 together with the Full Text Search component. • You start the filtering daemon (Mssdmn.exe) to parse Microsoft Office Word documents.
Undocumented stored procedures: Work directly with directories, files and drives
(Serdar Yegulalp) A T-SQL script will rarely need to access the file system directly. The vast majority of programming recommendations encourage you to manipulate files or folders through business logic (i.e., using a C#/VB.NET application) rather than a T-SQL script. However, in the few instanc
FIX: The error message that the SELECT statement returns may contain user data in SQL Server 2000
When you use a SELECT statement to fetch information from a view, and the SELECT statement returns an error message in Microsoft SQL Server 2000, the error message may contain user data. The user data is not returned in the final result if the SELECT statement successfully fetches data from a view.
Programming SQL Server 2005 with the .Net CLR
(Andrew Novick) One of the most anticipated features of soon to be released SQL Server 2005 is the integration of the .Net CLR into the SQL Server engine. This article is going to discuss just what that means and give you a first peak into how write .Net code and use it in SQL Server 2005. If you
Using DDL Triggers to Manage SQL Server 2005
(Jeffrey Juday) SQL Server 2005 has extended the trigger functionality you normally use with Data Manipulation Language (DML) commands such as INSERT, UPDATE, and DELETE to incorporate Data Definition Language (DDL) commands like CREATE DATABASE, DROP TABLE, and ALTER TABLE. The new technology, call
FIX: You receive an ‘Error: 8526, Severity: 16, State: 2’ error message in SQL Profiler when you use SQL Query Analyzer to start a distributed transaction after you have installed SQL Server 2000 SP4
When you use a client application such as SQL Query Analyzer to start or to enlist into a distributed transaction after you have installed Microsoft SQL Server 2000 Service Pack 4 (SP4), you receive an error message that is similar to the following: [Microsoft][ODBC SQL Server Driver][Shared Memo
