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
Chris Hedgate, one of our regular SQL Server columnists, recently became intrigued by the way that SQL Server implements the week number. His concern was why SQL Server treats week 53 as week 1, which is not that way that ISO6801 sees it. Read about his investigation into the methods of implementing an algorithm to solve this problem.
2005-01-20
11,761 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
Robert Pearl of Pearl Knowledge Solutions, Inc., recently attended a meeting of the NY Database Professionals Council where SQL Server Analysis Services 2005 was a large part of the topic of conversation. Read his report on the push to move business intelligence into the mainstream.
2005-01-18
15,634 reads
When it comes to auditing index use in SQL Server databases, I sometimes get overwhelmed. For example, how to do you go about auditing indexes in a database with over 1,500 tables? While auditing a single index is relatively straight-forward, auditing thousands of them in multiple databases is not an easy task. Whether the task is easy or not, it is an important task if you want to optimize the performance of your SQL Server databases.
2005-01-18
3,860 reads
Referential Ingegrity is a critical part of any well designed RDBMS application, not just a part of Oracle, DB2, or some other platform. SQL Server has tools to make it easy, but a developer has to take the time to ensure that it is setup correctly, and ignorance is no excuse. New author Nick Duckstein brings us a look at basic RI and how you can set this up in your database.
2005-01-17
14,287 reads
Have you ever had to access data from either a non-SQL Server source or from a separate SQL Server database (either residing on the same instance or on a separate instance)? Rahul Sharmas discusses how to bridge the gap between two different SQL Server instances or between heterogenous RDBMS such as SQL Server and Oracle: Use linked servers!
2005-01-17
3,331 reads
Andy Warren takes a look at SQLCompare, a tool that lets you compare two SQL databases and create a script to synchronize the differences.
2005-01-14 (first published: 2001-06-06)
16,278 reads
The next version of SQL Server named SQL Server 2005 is completely hyped with the integration of CLR into SQL Server. The introduction of CLR into SQL Server allows developers to write stored procedures, triggers, user defined functions, user defined aggregates and user defined types using .NET languages like VB.NET and C#. This introduction has opened up multiple avenues for developers and we need to be careful in maximizing the feature provided.
2005-01-14
3,007 reads
By Brian Kelley
The concern that a particular technology is going to destroy the world seems to...
The STIG is detailed, which is a good thing, but I found myself wanting...
By Steve Jones
After my session at VSLive last week, I had a few questions from the...
Comments posted to this topic are about the item RegEx Functions III
Comments posted to this topic are about the item Optimized Locking in SQL Server...
Comments posted to this topic are about the item Finely Tuned Models
If I run the REGEXP_LIKE() function, does it match values in a case-sensitive fashion, or a case-insensitive fashion by default.
See possible answers