SQL server 2008

Posted Date: 30 Nov 2008 Posted By: sreenivasarao Member Level: Gold Points: 1 Responses: 6

Hi,
I am new to Sqlserver 2008.

I would like to know what are the new features in SQL Server 2008?

And Please let me know diferences between Sqlsever 2005 and 2008?

What is SSIS?
What is SSRS?
What is Analyis Services?

Thanks in Advance.

Responses

Author: Deepika Haridas 30 Nov 2008

Member Level: Diamond

Rating:

Points: 6

4 features :

Table variable parameters

With the advent of SQL Server 2005, XML variables can be passed into procedures and parsed out with XQUERY inside the procedure to form a table. However, with the ability to pass a table variable in SQL Server 2008, developers will not have to be fully XQuery literate to pass a table of data into or out from a stored procedure. In my opinion, this will be one of the more integral tools for the developer in SQL Server 2008.

MERGE statement

The idea behind the MERGE statement is that the developer can construct TSQL data-manipulation language (DML) statements in which INSERT, UPDATE, or DELETE can occur in the same statement, based on different search conditions. I think this idea is very cool. The ability to complete multiple statements within one statement could potentially lead to less coding and increased performance.

In addition to this statement, another great feature has been added to the INSERT statement. In SQL Server 2008, the developer can issue multiple rows to be inserted without using a SELECT statement as the INSERT statement source. Instead, the VALUE clause of the INSERT statement can be used to specify sets of values separated by parentheses and commas.

Declarative Management Framework

The Declarative Management Framework gives DBAs a central location to manage database server policies for server management, object management, and security. I presume that some type application will be deployed with client tools that use this framework to manage your database server policies. Because it is a framework, you should be able to develop your own database policies through custom .NET code.

The potential for this type of tool is huge. It could possibly save DBAs a huge amount of time administering enterprise databases.

Change Data Capture

Change Data Capture makes database auditing easier to create and maintain. While DML auditing has been available via triggers in SQL Server for a few versions, and DDL auditing has been available since SQL Server 2005, the solutions had to be custom written by a developer with reasonably intimate details of the database's underpinnings. With Change Data Capture, system stored procedures are used to mark which types of objects you want to audit, and the stored procedures take care of how the auditing occurs.

While setting up these auditing procedures is typically a one-time deal, business requirements change over time; it is usually easier to use system stored procedures to handle changes, plus it's less error prone than changing your custom auditing code. Unfortunately, when you use Change Data Capture, you will lose the auditing flexibility that you currently have with your own auditing solution.