Version control of stored procedures is not exactly a SQL Server 2000 strong point. In fact, it is downright abysmal and there have been lots of ideas and solutions put forth to solve the problem. Andy Warren brings us a new one that's small and lightweight and may help you after getting inspired at TechEd 2005.
Even a cursory inspection of data management practice reveals that the majority of practitioners-–be they novices, or experienced, users or vendors--operate in a “cookbook”, product-specific mode, without really knowing and understanding the fundamental concepts and principles underlying their field, e.g. what data means, what data model, database, DBMS, data independence really are, and so on.
Ever do something to your SQL Server 2000 server and then realize you've just broken something major? Ever have a moment when you want to go "whoops", but really feel like crying ot running away? Steve Jones just had one of those and gives you a few things to think about when you deal with a situation like that.
This article presents a broad set of guidelines to define the value, voice and visibility for a unified BI project.
This is one of the very useful features in SQL Server 2000 and if you ever have the need to perform this actiom, you will appreciate the knowledge in this article.
This is the third article of our series discussing SQL Server 2005 Integration Services (SSIS), which provides Extraction, Transformation, and Loading features, replacing Data Transformation Services (DTS) available in SQL Server 2000 and 7.0. We have already presented an overview of the basic concepts necessary to design and implement SSIS-based projects. We have also stepped through the creation of one such project using Business Intelligence Development Studio. Our sample SSIS package, described in our previous article, delivered the basic functionality we needed (running an external process and loading the outcome of its execution stored temporarily in a text file into a database), however, it had one major shortcoming - a lack of support for reusability.
One of the lesser used features of SQL Server 2000, but the capability to restore your databases to a particular point in time can be a valuable skill. Kathi Kellenberger takes a moment to explain how this feature works and how you can use it in your environment.
In the first article of this series, we presented the basic concepts relevant to understanding SQL Server 2005 Integration Services, which is the primary mechanism for Extraction, Transformation, and Loading (ETL) functionality available in SQL Server 2005. We also provided a quick overview of tools that allow you to manage such activities as DTS package design, development, and storage, as well as interactive and scheduled execution. In order to gain better familiarity with each of these activities, we will look at them from a more practical perspective, using a number of fairly straightforward examples.
One of the SQL Server 2005 Beta 2 features that has undergone considerable architectural, functional, and interface changes, compared with its earlier versions, deals with extraction, transformation, and loading (also known as simply ETL) of data. (In other words, allowing you to move data between a variety of stores and to modify it in the process, according to your arbitrary requirements). While in SQL Server 7.0 and 2000, such capabilities have been provided by Data Transformation Services (DTS in short), Microsoft decided that the degree of modifications introduced in the new version justified re-branding it, hence its rearchitectured and significantly improved implementation has been introduced under the new name of SQL Server Integration Services (SSIS).
This is the first article in a series on writing stored procedures using the Common Language Runtime (CLR). This article focuses on basic C# syntax and using Visual Studio to build a stored procedure. It's targeted at DBA's and anyone else who primarily writes in Transact-SQL and hasn't had much exposure to .NET yet.
By Steve Jones
I haven’t done one of these in awhile, but I saw an article recently...
In last months one of the scenarios where you can use AI has been...
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
Comments posted to this topic are about the item 25 Years Later: What SQLServerCentral...
Comments posted to this topic are about the item Doing Good at SQL Server...
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers