While many things in technology decline in price over time, there are few things that do not, space being one of them. In response to other recent writings on the life work balance and other career articles for SQL Server DBAs, new author Sushila Iyer brings us a look at how telecommuting can be of benefit to both the DBA and the employer.
Shredding a recordset in this instance means that we are going to show you how to take a recordset produced in your SSIS package, loop over the rows in that recordset, break apart the columns and do something with them. This is really useful when you want to preform an action on a row of data for every row of data just like we are going to do here. Sure we could use an ExecuteSQL task to get the recordset as well but that does limit our choices of source data whereas doing it in the pipeline does not. Something useful we hope.
One of the most useful tasks in SQL Server 2000's DTS environment is the Dynamic Properties task. Author Kathi Kellenberger brings us a look at how this task can help you accomplish an unusal import task.
InfoPath forms can be saved to XML, these XML Files can later be used in SSIS XMLSource adapter to pull out the data in tables and columns. However, there are some common problems you may meet in these scenarios. This article describes how to work around these potential problems. The issues mentioned in this article is not only specific to InfoPath files, it can also be referenced in other similar situations as well.
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.
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
By John
Today is Christmas and while I do not expect anybody to actual be reading...
By Bert Wagner
Until recently, my family's 90,000+ photos have been hidden away in the depths of...
I have a SQL Agent job for backing up a set of Analysis Services...
Comments posted to this topic are about the item SQL Server 2025 Backup Compression...
Comments posted to this topic are about the item The Large Encoded Value
I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?
See possible answers