Three Vs: Best Practices for a Unified Business Intelligence Infrastru
This article presents a broad set of guidelines to define the value, voice and visibility for a unified BI project.
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.
TechEd is a great show and while the PASS summit is the best one for DBAs, this one is great for most of the other Microsoft technologies. Read about Day 3 from Steve Jones.
The SQL Server 2000 Query Optimizer is one of the more complicated things that a SQL Server DBA deals with. For most of us, we just let it work and do not give it a second thought. But when a crisis occurred, Andy and Steve had to dive in to learn a few more things about it.
Day 2 from TechEd, this time from Brian Knight's perspective as the SQLServerCentral.com crew enjoys a week of learning and sun at the 2005 conference.
By Steve Jones
AI is a big deal in 2026, and at Redgate, we’re experimenting with how...
By Steve Jones
Another of our values: The facing page has this quote: “We admire people who...
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
Comments posted to this topic are about the item No Defaults Passwords Ever
Hi, We have low latency high volume system. I have a table having 3...
Comments posted to this topic are about the item The Long Name
I run this code to create a table:
When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?