|
|
-
|
|
Extending the Windows user experience of file searches to SQL server is a bit of a challenge because the asterisk [*] is a wild-card character in Windows whereas SQL Server uses percentage [%]. The percentage [%] is valid in a file name which adds to the complications. Today's post presents an approach to realize such a requirement using the ESCAPE keyword....
|
|
-
|
|
In this post, I present an alternate to Table Valued Parameters for SQL Server 2000. Support for Microsoft SQL Server 2000 ends this year and yet, one can find systems (production or otherwise) that continue to run on and support SQL Server 2000. The solution presented in this post might be useful to such products....
|
|
-
|
|
Although one of the most robust change and tamper detection mechanisms available in Microsoft SQL Server, HASHBYTES suffers from a limitation that it cannot handle more than 8000 bytes of input, which translates to 4000 NVARCHAR characters....
|
|
-
|
|
Having the same non-qualified column name/alias in the ORDER BY clause results in an error. But what would happen if we define duplicate column aliases in the SELECT clause? Will SQL Server consider this to be an ambiguous column name? This post presents the answer to this interview question....
|
|
-
|
|
In this post, we look at the SQL Server installation related DMVs introduced in SQL Server 2008 R2/2012...
|
|
-
|
|
Every SQL developer/DBA I know has spent a considerable time customizing their SSMS setup. When moving from workstation to another, all the efforts need to be spent again. But not anymore - the Import and Export wizard, a part of the SSMS for SQL Server 2012 makes moving settings from one computer to another an easy task....
|
|
-
|
|
The FMTONLY option can be SET to ON if applications need to know the format of the response and test it without actually running the query. The query is parsed, compiled, executed and only the meta-data is returned to the client application. ADO makes use of such a mechanism as a "dry-run" before actually executing a query. The FMTONLY is recommended only for SQL 2008 R2 and below....
|
|
-
|
|
What would you do if you wanted to check whether a particular query/batch you wrote is free from any errors without using Intelli-sense and without executing or compiling the statement? A T-SQL solution within Microsoft SQL Server to this challenge is to use the SET option PARSEONLY to ON....
|
|
-
|
|
It is a myth that the ROWVERSION column holds a unique value across a database. In this post, I demonstrate that a possibility exists for having duplicate values in a ROWVERSION column when using Bulk-Insert operations (SELECT…INTO)...
|
|
-
|
|
How do you know when your index was last rebuilt or reogranized? How many records changed during this rebuild/reorganization operation? Read this post for answers to all these questions....
|
|