SQL Server 2008

********************************************************************************************

This is one very interesting issue which I have started to follow recently. Just like any other organization my company has many servers. Some are production and some are development. It is very much necessary that query which are written for developer environment does not run for production environment accidentally.
In SQL Server 2008 there is special feature which can change the color of the task bar. This will alert developer to run query on server.
Let us see quick tutorial with images which explains how the color of the status bar in SQL Server management studio can be changed.

The Business Intelligence Development Studio

The Business Intelligence Development Studio (BIDS) is the central environment that you ’ ll spend mostof your time in as an SSIS developer. BIDS is just a specialized use of the familiar Visual Studiodevelopment environment that can host many different project types from Console applications to ClassLibraries and Windows applications. Although you may see many project types, BIDS actually onlycontains project templates for Analysis Services, Integration Services, Report Server, and Report ModelProjects. SSIS in particular uses a business - intelligence project type called an Integration Services projectthat provides development design surfaces with a completely ETL - based set of tools in the Toolboxwindow. Get your first look at the development environment

............................................................................................................

SQL Server SSIS Historical OverviewIn

SQL Server 7.0, Microsoft had a small team of developers work on a much understated feature of SQLServer called Data Transformation Services (DTS). DTS was the backbone of the Import/Export Wizard,and the DTS ’ s primary purpose was to transform data from almost any OLE DB – compliant Data Sourceto another destination. It also had the ability to execute programs and run scripts, making workflow aminor feature.

By the time that SQL Server 2000 was released, DTS had a strong following of DBAs and maybe a fewdevelopers. Microsoft included in the release new features like the Dynamic Properties Task that enabledyou to alter the package dynamically at runtime. Even though DTS utilized extensive logging along withsimple and complex multiphase data pumps, usability studies still showed that developers had to createelaborate scripts to extend DTS to get what they wanted done. A typical use case was enabling DTS toload data conditionally based on the existence of a file. To accomplish this in DTS, you would have hadto use the ActiveX Script Task to code a solution using the file system object in VBScript. The problemhere was that DTS simply lacked some of the common components to support typical ETL processes.Although it was powerful if you knew how to write scripting code, most DBAs just didn ’ t have this typeof scripting experience (or time).

After five years, Microsoft released the much touted SQL Server 2005, and SSIS, which is no longer anunderstated feature like DTS. With the 2008 release, SSIS is now one of the main business intelligence(BI) platform foundations. SSIS has moved so far up in importance that it now has its own service alongwith the new name. This is entirely appropriate because so much has been added to SSIS. Microsoftmade a huge investment in usability, adding the first set of ETL tool - based components and upping theante again with this latest version. If what you need to do isn ’ t readily available, you now have the full.NET library with VB and C# programming languages to add your own custom coding to message dataor manage the ETL process. However, you ’ ll be surprised how rarely you ’ ll need to drop into a codingenvironment. In fact, as you dig into the toolset, you ’ ll find that things you may have needed to hand -code in a Script Task are simply part of the out - of - the - box components.