Ravi S.Maniam's Blog

Did you Experience the NEW SQL Server 2008 R2 [Kilimanjaro]

Ravi S.Maniam — Sun, 04 Oct 2009 10:37:01 GMT

Kilimanjaro is now SQL Server 2008 R2. This is the next version of SQL Server 2008 that will give your organization a power steering to drive the Business Intelligence efforts much faster & focused in your organization. Why I say that it is the next version of SQL Server 2008 instead of “SQL Server” is because Kilimanjaro has extended the existing capabilities of SQL Server 2008.

Thank you very much for visiting this article. In case if you are not on the MSDN blogs then I would request you to please visit my blog at http://blogs.msdn.com/manisblog because at times I improve the existing articles after reading emails from people who enthusiastically provide their feedback. These improvements might not be reflected on the other blog sites who have indexed this blog post.

The Kilimanjaro comes with some of the most powerful features and most desired features for Business Intelligence that will allow the organizations to broaden the reach of BI to every section of the business helping business to take faster, better and more relevant decisions. SQL Server 2008 R2 will help you to unlock your data & produce meaningful information in no time which in turn will empower the end users to take reliable & relevant decisions.

SQL Server 2008 R2 is presently in the CTP (Community Technology Preview) stage it can be downloaded from the Microsoft Website : http://technet.microsoft.com/en-us/evalcenter/ee315247.aspx . I started using the SQL Server 2008 R2 since last a few days and among the features I used, I find them all very compelling and convincing.

Some of the features / project that SQL Server 2008 R2 comes with are worth mentioning like the “Project Madison” which is a highly scalable and high performance data warehouse appliance that will deliver amazing performance at low cost through a massively parallel processing (MPP). Moreover it allows you to scale your data warehouse from Terabyte to Petabyte range on an Industry Standard Hardware. The best part is that “Project Madison” will complement your existing SQL BI solution & ongoing BI efforts because the appliance model of “Project Madison” simplifies deployment and maintenance, it integrates with existing SQL Server 2008 data warehouses via hub-and-spoke architecture and the fruits are greater ROI from BI investments through integration with SQL Server 2008.

A sample of scale out data warehouse with “Madison”.

Picture Source : Click Here

Do you love MS-Excel for analyzing your business results ? The project “Gemini” in an innovative solution that allows you to analyze your data on your most loved tool MS-Excel. This Excel add-in enables the Excel power users to easily create powerful BI solutions by streamlining the integration of data from multiple sources enabling interactive modeling and analysis of massive amount of data. “Gemini” also supports the effortless sharing of data models and reports through Microsoft Office SharePoint 2010.

A quick look at the “Gemini” dashboard

Picture Source: Click Here

People are using SQL Server Reporting Services for sometime now, they have developed their critical and important reporting solutions with SQL Server Reporting Services. So now the SQL Server 2008 R2 comes with an enhanced SQL Server Reporting Services which also has a new and enhanced Report Builder component the “Report Builder 3.0”. The Report Builder 3.0 accelerates report creation, collaboration and consistency. The Reporting Services now allows rich visualization of geospatial data which includes mapping, routing, and custom shapes that can help the end users to create customized reports that leverage existing content objects, such as queries, data regions, and charts and graphs. The users can also enhance location-based data reports with Bing Maps in Report Builder 3.0.

There are many more exiting features that I am exploring now like, the UCP (Utility Control Point) that will help the DBAs with the manageability or the MDS (Master Data Services) that helps to improve the quality of the data and many more….. If you have not explored the features of SQL Server 2008 R2 then you may do it now… Download the latest SQL Server 2008 R2 August CTP from : http://technet.microsoft.com/en-us/evalcenter/ee315247.aspx

I will get back to you soon with my articles on the SQL Server 2008 R2 features till then keep visiting my blogs and keep writing to me !

Performance Boost for SQL Queries – Filtered Index in SQL Server 2008

Ravi S.Maniam — Sat, 04 Jul 2009 06:09:59 GMT

SQL Server 2008 introduces an enhancement to the way the indexes are created which helps to get better performance from the same queries. This new little guy is known as ‘Filtered Index’. This is actually an Optimized Non-Clustered index which is well suited to cover the subset of data with in a table.

Every organization has a specific data usage pattern and if we have an idea of the data usage pattern then we can create the filtered indexes to cover the subsets of data that can actually yield faster results from our same query / stored proc.

Let’s say the sample database “AdventureWorks” is used by a company that sells spare parts and they have different departments that sell specific products and lets say the racing bikes being the hottest in the market, it drives more sales for the racing bike spare parts. This means that more transactions are being done related to a specific product(s) so most of the times the data is filtered, is based on a specific Product Id. Moreover if there are millions of Rows in the table, it becomes really necessary to choose the indexes correctly and carefully because of the storage space involved to store them.

For example the queries (like the following one) are executed based on a selection criteria very frequently then the filtered indexes will help you a lot.

SELECT * FROM [AdventureWorks].[Purchasing].[PurchaseOrderDetail]

Where ProductID =709 OR ProductID = 879 OR ProductID = 877

Let see generally how indexes speed up the queries. During the SELECT, UPDATE, DELETE operations the SQL optimizer will look for indexes and determine the most efficient method to complete an operation. In this process SQL Optimizer determines to use an index or to go for a table scan. The SQL Optimizer does this operation to reduce the query execution time and improve the performance.

Index seeks are preferred for the selective queries like the one above and the index seeks happen only when the optimizer finds the index on the table useful, otherwise it will scan all the records. Generally, searching an index to spot a matching record is faster than a table scan because it is ordered and less number of columns means small set of data which in turn means less hops to find the match. Unique indexes are faster and table partitions speeds it up more. Well ….discussing the anatomy of indexes and strategy for indexing the tables is a huge subject and there are books available for that so …let me get back to the topic where I left it.

So why a filtered index ? A filtered index can be used as an index for a subset of data rather than the entire set of data. The filtered index takes less space to store the index because it stores only index information related to a subset of data unlike an usual non-clustered index. In no way this is a substitute for a regular Clustered and Non-Clustered indexes. This is an additional enhancement that can help you in tuning specific highly selective queries.

What are the advantages of Filtered Indexes :

Improved query performance and plan quality

A well-designed filtered index improves query performance and execution plan quality because it is smaller than a full-table non-clustered index and has filtered statistics. The filtered statistics are more accurate than full-table statistics because they cover only the rows in the filtered index.

Reduced index maintenance costs

An index is maintained only when data manipulation language (DML) statements affect the data in the index. A filtered index reduces index maintenance costs compared with a full-table non-clustered index because it is smaller and is only maintained when the data in the index is affected. It is possible to have a large number of filtered indexes, especially when they contain data that is affected infrequently. Similarly, if a filtered index contains only the frequently affected data, the smaller size of the index reduces the cost of updating the statistics.

Reduced index storage costs

Creating a filtered index can reduce disk storage for non-clustered indexes when a full-table index is not necessary. You can replace a full-table non-clustered index with multiple filtered indexes without significantly increasing the storage requirements.

You can also determine the space required for an index. Please visit : http://msdn.microsoft.com/en-us/library/ms191163.aspx

How to create a Filtered Index ?

Let’s see an example :

USE AdventureWorks

--Drop if the index already exists

IF EXISTS (SELECT name FROM sys.indexes

WHERE name = N'FNC_PurchaseOrderDetail_Bikes'

AND object_id = OBJECT_ID ('Purchasing.PurchaseOrderDetail'))

DROP INDEX FNC_PurchaseOrderDetail_Bikes

ON Purchasing.PurchaseOrderDetail;

--Create a new index

CREATE NONCLUSTERED INDEX FNC_PurchaseOrderDetail_Bikes

ON Purchasing.PurchaseOrderDetail(ProductID)

WHERE ProductID IN(709, 879, 877)

So simple .. just add a WHERE clause to the index. You need to choose the WHERE clause carefully.

When to Use Filtered Indexes

Filtered indexes are useful when columns contain well-defined subsets of data that queries reference in SELECT statements. Examples are:

Sparse columns that contain only a few non-NULL values.
Heterogeneous columns that contain categories of data.
Columns that contain ranges of values such as dollar amounts, time, and dates.
Table partitions that are defined by simple comparison logic for column values.

Reduced maintenance costs for filtered indexes are most noticeable when the number of rows in the index is small compared with a full-table index. If the filtered index includes most of the rows in the table, it could cost more to maintain than a full-table index. In this case, you should use a full-table index instead of a filtered index.

Filtered indexes are defined on one table and only support simple comparison operators. If you need a filter expression that references multiple tables or has complex logic, you should create a view.

Please visit books online to know more about filtered indexes and keep reading my blogs.

Bye Now !! :-)

How to get the current time of any TimeZone in SQL Server 2008

Ravi S.Maniam — Tue, 16 Jun 2009 19:56:00 GMT

We create ASP.Net applications which is hosted at a Central Location say Seattle (USA) but the customers using the application are located all around the world and when they enter the transaction they want their local time to be considered but when we call the function GetDate() the SQL Server will take the server time into consideration. This is a classic problem & people have come up with various ways to tackle this problem but with SQL Server 2008 and DateTimeOffset feature it has become a bit easier.

So how to do it…. When the user registers herself to the ASP.NET application for the first time you can ask the Country and State of residence of this user which is stored in the database. Now, when the transaction is posted you can do the following to get the user’s local time of the transaction.

Step 1:

I created a table called TimeOffsets with two Columns, Location and TimeOffset with a Primary Key on ‘Location’.

CREATE TABLE [dbo].[TimeOffsets](

[Location] [varchar](100) NOT NULL,

[TimeOffset] [varchar](10) NOT NULL,

CONSTRAINT [PK_TimeOffsets] PRIMARY KEY CLUSTERED

(

[Location] ASC

)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

) ON [PRIMARY]

Step 2:

I entered some values into this table. It is a little time consuming but it is a one time job. For your help I have attached an Excel Document along with this blog post so you can import the values into the SQL Server Table.

NOTE: The Time Zone Offset that I am providing below is not a complete list and it is not daylight saving aware. You have to make the changes accordingly. This is just a sample.

Location

TimeOffset

Addis Ababa

+03:00

Adelaide

+09:30

Algiers

+01:00

Almaty

+06:00

Amsterdam

+01:00

Anchorage

-09:00

Apia

-11:00

Asunción

-04:00

Athens

+02:00

Auckland

+12:00

Azores

-01:00

Baghdad

+03:00

Baku

+04:00

Bangkok

+07:00

Beijing

+08:00

Berlin

+01:00

Bogotá

-05:00

Buenos Aires

-03:00

Cairo

+02:00

Calgary

-07:00

Cape Town

+02:00

Cape Verde

-01:00

Casablanca

+00:00

Chicago

-06:00

Cocos Islands

+06:30

Colombo

+05:30

Dakar

+00:00

Dallas

-06:00

Darwin

+09:30

Delhi

+05:30

Denver

-07:00

Dhaka

+06:00

Dubai

+04:00

Fernando de Noronha

-02:00

Halifax

-04:00

Hanoi

+07:00

Havana

-05:00

Helsinki

+02:00

Hong Kong

+08:00

Honolulu

-10:00

Irkutsk

+08:00

Jakarta

+07:00

Jerusalem

+02:00

Juneau

-09:00

Karachi

+05:00

Kathmandu

+05:45

Kinshasa

+01:00

Krasnoyarsk

+07:00

Kuala Lumpur

+08:00

Lagos

+01:00

Las Vegas

-08:00

Lima

-05:00

Lisbon

+00:00

London

+00:00

Los Angeles

-08:00

Magadan

+11:00

Maldives

+05:00

Manila

+08:00

Mauritius

+04:00

Melbourne

+10:00

Mexico City

-06:00

Montevideo

-03:00

Montreal

-05:00

Moscow

+03:00

Mumbai

+05:30

Nairobi

+03:00

New York City

-05:00

Nouméa

+11:00

Omsk

+06:00

Pago Pago

-11:00

Papeete

-10:00

Paris

+01:00

Perth

+08:00

Petropavlovsk-Kamchatsky

+12:00

Phoenix

-07:00

Pyongyang

+09:00

Reykjavík

+00:00

Rio de Janeiro

-03:00

Rome

+01:00

Saint Petersburg

+03:00

Samara

+04:00

San Francisco

-08:00

Santiago

-04:00

São Paulo

-03:00

Seoul

+09:00

South Georgia and the South Sandwich Islands

-02:00

Suva

+12:00

Sydney

+10:00

Tashkent

+05:00

Tbilisi

+04:00

Tehran

+03:30

Tenerife

+00:00

Tokyo

+09:00

Toronto

-05:00

Tunis

+01:00

Vancouver

-08:00

Vladivostok

+10:00

Yakutsk

+09:00

Yangon

+06:30

Yekaterinburg

+05:00

Step 3:

Create a SQL Function that will return the value of type DateTimeOffset.

CREATE FUNCTION GetGeographicalTime

(

@MyPlace AS VARCHAR(100),

@TargetPlace AS VARCHAR(100)

)

RETURNS DATETIMEOFFSET

BEGIN

DECLARE @TargetPlaceOffset VARCHAR(100)

DECLARE @MyPlaceOffset VARCHAR(100)

DECLARE @todaysDateTime Datetime2

DECLARE @todaysDateTimeOffset DateTimeOffset

DECLARE @returnDateTimeOffset DateTimeOffset

SELECT @todaysDateTime = GetDate()

SELECT @MyPlaceOffset =[TIMEOFFSET] from TIMEOFFSETS WHERE [LOCATION] = @MyPlace

SELECT @TargetPlaceOffset = [TIMEOFFSET] from TIMEOFFSETS WHERE [LOCATION] = @TargetPlace

SELECT @todaysDateTimeOffset = TODATETIMEOFFSET (@todaysDateTime, @MyPlaceOffset)

SELECT @returnDateTimeOffset = SWITCHOFFSET(@todaysDateTimeOffset,@TargetPlaceOffset)

RETURN @returnDateTimeOffset

END

Step 4:

Now say suppose your Local TimeZone is “Delhi” (India) i.e. your server is located in Delhi and the local time zone is set for the server and you want to find out what is the current time in Los Angeles (USA) then you will call this function as follows:

Select dbo.GetGeographicalTime('Delhi','Los Angeles')

This will yield the current time at Los Angeles.

NOTE: I am attaching the SQL Script to create the Table and the Function as well as the Excel file containing the Time Zone Offsets along with this post. You can download it from here.

Thank you for reading this post … and keep a watch on my blog for newer posts.

Love @ First sight, The Visual Studio Team Test 2010

Ravi S.Maniam — Mon, 18 May 2009 14:04:16 GMT

Recently, I attended the Tech-Ed 2009 at Hyderabad (India). In the Application Lifecycle Management track the Visual Studio Team Test team showcased the new features of Visual Studio 2010 Team Test features. Usually, I write my blogs with screenshots and samples but this time I could not resist myself from telling my first hand experience with the cool features of VSTS 2010.

Mr. Amit Chatterjee delivered the first session on the VSTT 2010 features in the Tech-Ed on 13-May-2009. The theme was ‘Visual Studio 2010 has a new BUG’. Yes, the Visual Studio Team test has a new “BUG” i.e. the BUG Workitem. You will say ‘what is so new in that ?’ it is already there in the Visual Studio 2008 but this is really new & exciting …

… now in the Bug WorkItem you can automatically record the test and attach the screenshots & the video to the Bug workitem and it happens automatically once you turn on a couple of switches. Now Visual Studio will have the Lab management capabilities so if you want to test your application on a given platform you can do that. Rather than giving each tester additional set of PCs to test the application, you can put all these PCs in a Pool. These PCs will host the Hyper-V VMs specific to your test environment. The tester can test your applications thoroughly in this environment, preserve the environment, if something goes wrong - they can always step back to the previous setting and finally when everything done – they can tear down this VM to make additional room for other VMs. The coolness in this feature is … the Developers & Testers need not to be an IT-Pro or an Administrator to stage all this environment, the VSTS provides the connectivity to System Center Virtual Machine Manager and from within the VSTS you can initiate this environment and manage it. This will help the customers spend less from their IT budget and enhance the productivity of the testers. If you remember, I said “ENVIRONMENT” i.e. you can even test your distributed applications. These features were demonstrated by Shay Mandel.

One of the other cool feature that I loved the most is the Coded UI test. I work with a lot of ISVs and it has been a constant demand that they need to have some tools to test the UI. Now the VSTS 2010 comes with an ‘INTELLIGENT’ test recorder. ‘I want to emphasize the word INTELLIGENT’ because unlike the usual test tool that records the (X,Y) coordinates and breaks when the screen resolution changes, the VSTS 2010 records the details of the controls used on the web pages and creates the C# or VB.Net code in the background so now you can either play it back and write a few lines of code to test this application’s UI against the million possible values. You can even fetch the data from your database and play it on the UI to check if any of these values break the UI, just by writing simple code.

Check out for more in the near future…

Microsoft Tech-Ed @ Hyderabad [INDIA] - May 2009

Ravi S.Maniam — Mon, 18 May 2009 11:55:56 GMT

I attended the Microsoft Tech-Ed event @ Hyderabad (India) on 13,14,15th of May 2009 i.e. the last week. There were a lot of exiting sessions for Developers, Architects and IT Pros. The podium was setup in a large hall with all vibrant colors.

The Rock Band – Agnee http://www.agneelive.com started the session with Rock Music – Jee Le Baby !! This song was specially composed for Microsoft Tech-Ed. It is a very cool song. Everyone in the audience was very restless to see Steve Ballmer with a lot of expectations and questions, glittering their eyes.

It started with a Key Note by our CEO - Steve Ballmer. Everyone cheered loud when Steve entered the hall. Steve started with the economic slow down and he shared his vision of optimism towards the future. People had a lot of questions for him starting with Windows 7 to economic slow down. Steve said that very soon Windows 7 will be released and there is a lot of buzz in the industry. People who are using the pre-release version of Windows 7 are already liking it very much. Some SQL Server MVPs had the question on SQL Server’s future release and Steve said “Keep a watch !!”. Steve is very optimistic about the release of the latest Microsoft software in the near future like Windows 7, VSTS 2010 etc. There was a question around the Microsoft’s future plans in India. Steve said that, he sees a great talent pool in India. Steve sees the current “Economic Reset” as a half glass full, he energized everyone with positive energy. The key note ended with loud cheers from the audience.

Overall the arrangements were done very well. From the registration desk, upkeep of the hotel, certification kiosks to the food, everything was well managed. The event organizers wearing the green T-shirts were always ready to help and guide. There were some certification kiosks setup where people played games and won the vouchers. The XBox counter was the one I liked the most. There were many more counters from Microsoft learning, Citrix, Intel, Kingfisher Airlines etc. Overall it was very informative. The security arrangements, quality of food and beverages are worth mentioning.

This event was co-sponsored by many other partners including the news paper, Economic Times http://economictimes.indiatimes.com/.

There were many tracks in the Tech-Ed like the Developer Track, IT-Pro track, Business Intelligence Track, Architecture Track, Application Lifecycle Management Track. I attended the Business Intelligence Track and the Application Lifecycle Management Track.

The session by Amit Chatterjee on Visual Studio Team Test is the one I liked the most. He talked about the new capabilities in Visual Studio 2010. I attended the detailed session on VSTS 2010 Lab Management and Visual Studio Team Test 2010 called as “Tech Tent” delivered by Shay Mandel, I was simply spell bound. The new VSTS 2010 carries so many cool features. The entire Visual Studio Team Test team, including Eyal Melamed, Neelesh Kamkolkar, Vishal Mehrotra, Vinod Malhotra and others were very helpful, addressed every question that came up during the session and took a note of every feedback.

I will write about the new features of VSTS 2010 and other sessions I attended very soon … so keep a watch on this blog. Cheers !!

The official Tech-Ed site is : http://www.microsoft.com/india/teched2009/

Easy Table Partitions with SQL Server 2008

Ravi S.Maniam — Sun, 18 Jan 2009 03:13:00 GMT

I am glad to see people realizing the value of SQL Server 2008 platform and they are happily migrating to the SQL Server 2008 platform.

Hmm.. what am I going to cover today.... it is something that we all expect from a SQL Server database i.e. performance and I am going to write it in the same fashion that you like most i.e. simplify the contents, make it easy to understand and provide the steps with pictures.

Introduction

We all know we have to work with loads of data every day and over the time with the growth of the organization the data bank also grows tremendously. We see there is a performance degradation after few years or months. Is it the same SQL Server that was working efficiently in past is now getting slower, it is not the SQL Server binaries that have changed, it is still the same efficient SQL Server but the growth of data and the way it is structured plays a big role in the performance.

In my experience I have seen that an inefficient query, badly built index, poorly structured database can eat up the entire resources on the server. If the best practices are followed then you will get good performance from the SQL Server. For the best practices on Physical Design of SQL Server Database visit: http://www.microsoft.com/technet/prodtechnol/sql/2005/physdbstor.mspx

Today I am going to discuss how easy it is for us to partition our tables for better performance with SQL Server 2008 (Katmai). I am not going to cover what is the criteria for partitioning your data because it is a long conversation topic. I am just going to highlight the SQL Server 2008 Management Studio's feature for table partitioning.

Partitioning Steps

You should partition your tables that has accumulated a lot of data over the time and you find that the performance is slowing down. It would not be a very good idea to partition a table it has just a couple of hundred rows for example : Product Category table. You could partition your tables that contains a lot of transactions like Purchase Order tables, Sales Order tables, General Ledger Tables etc.

Step 1:

Open the SQL Server 2008 management studio and select the appropriate table that needs to be partitioned. Right click on the table and in the context menu select Storage >> Create Partition.

Step 2:

I am using the [Purchasing.WorkOrder] table in the 'AdventureWorks' sample database. When you select the above option a wizard dialog box appears, press the next button once.

You will see a dialog box with the columns available for partition with data type, length etc. Select the column on which you would like to create a partition and press next.

Step 3:

Provide the name of the partition function and press Next.

Step 4:

Provide the name of the partition scheme and press next.

Step 5:

You have to select the option Left Boundary or Right Boundary and then click the button that says Set Boundaries.

Left boundary
The Boundary column label in the grid will dynamically display <= Boundary when you select Left boundary.

Right boundary
Select to include range values up to the specified value in the Boundary column for each filegroup selected. The specified value will be the starting value for the range values of the filegroup on the next row. The Boundary column label in the grid will dynamically display < Boundary when you select Right boundary.

A small dialog box appears with the caption "Set Boundary Values". Select the starting and ending date and select the Date Range from Monthly, Yearly, Quarterly, Half-Yearly , Daily and press OK. I am using End Date field for the partition in this demo.

The above option will create the partition ranges for you. Select the appropriate File Group for each partition in the grid and then click on the 'Estimated Storage' button which will give you the details of the required space. Once you are happy with the results, please press 'Next'.

Step 6:

After pressing the 'Next' button you will get the option to create a script or to run it immediately or to schedule it for a later time. Depending on your requirements you can select the option and press the finish button.

See it's so easy to partition your tables and achieve better performance. Please keep a track of my blogs because I will soon come up with more blog posts, if you have any feedbacks or if you liked this article then please drop me an email. Thank you.

How to deploy SQL Server 2008 Express as a prerequisite with ClickOnce

Ravi S.Maniam — Mon, 22 Dec 2008 21:33:00 GMT

People often ask me how to deploy SQL Server 2008 Express with applications as a prerequisite with Visual Studio 2008. Most often this situation is encountered when people want to deploy applications using the ClickOnce or they want to build a MSI package with SQL Server 2008 using Visual Studio 2008 and include the SQL Server packages with the setup.

Now I am providing you with a set of steps to demonstrate deployment of SQL Server 2008 with your application as a prerequisite. You can try these steps on your test environment first. SQL Server 2008 Express needs Windows Installer 4.5 and .Net 3.5 SP1 Framework.

In case if you are not on the MSDN blogs then I would request you to please visit my blog at http://blogs.msdn.com/manisblog because at times I improve the existing articles after reading emails from people who enthusiastically provide their feedback. These improvements might not be reflected on the other blog sites who have indexed this article.

Download and install Visual Studio 2008 Express edition because the SQL Server 2008 bootstrapper will be found with the VS2008 Express. Now the steps that I am suggesting would be done using your usual VS 2008 SP 1 development environment like VS 2008 Professional, Team Suite etc.

NOTE: If you are using any other language version other than English like German etc. then please download the appropriate language version of Visual Studio 2008 Express and SQL Server 2008 express.

Visual Studio 2008 Express and SQL Server 2008 Express could be downloaded from : http://www.microsoft.com/express/download/
Using VS 2008 Development Environment, create a small .Net 3.5 Windows application that connects to SQL Server 2008 Express Edition.
Add a Setup Project to this Visual Studio 2008 Solution.
Add the project output of the Windows Application to the setup project.
In the setup project you would not be able to locate Windows Installer 4.5, .Net 3.5 SP1 and SQL Server 2008.
Now download all the files from http://www.microsoft.com/downloads/details.aspx?FamilyId=5A58B56F-60B6-4412-95B9-54D056D6F9F4&displaylang=en to the Bootstrapper/packages folder which looks like C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages. This will provide you with the Windows Installer 4.5 Bootstrapper.
Download SQLEXPR_x64_ENU.exe , SQLEXPR_x86_ENU.exe, SQLEXPR32_x86_ENU.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=58ce885d-508b-45c8-9fd3-118edd8e6fff&DisplayLang=en and place them in the SQLExpress2008/en folder within the Bootstrapper/packages folder. This makes sure that the SQL Server 2008 Express is present.
Now to download the .Net 3.5 SP1 framework please navigate to http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe and download the 231 MB file.
At the command prompt navigate to the folder that contains the dotnetfx35.exe file and type : dotNetFx35.exe /x:. This will extract the Framework files to a folder named "WCU" in the current directory.
Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:
Now for the successful installation of the .Net 3.5 SP1 Framework on the client computer you need to take further following actions so that the framework installs successfully. After these steps you would be able to add .Net 3.5 SP1 Framework, Windows Installer 4.5 and SQL Server 2008 Express with your application setup.

Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems

Edit the Product.xml file in Notepad.

Paste the following into the <PackageFiles> element:
<PackageFile Name="TOOLS\clwireg.exe" />
<PackageFile Name="TOOLS\clwireg_x64.exe" />
<PackageFile Name="TOOLS\clwireg_ia64.exe" />

Find the element for <PackageFile Name="dotNetFX30\XPSEPSC-x86-en-US.exe" and change the PublicKey value to: 3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6
CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE
8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D057447
65CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5
E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625D
ED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13
DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE
805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8
A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707
CEE554D77D2085576810203010001

Find the element for <PackageFile Name="dotNetFX30\XPSEPSC-amd64-en-US.exe" and change the PublicKey value to the same as in step 4 above

Save the product.xml file

NOTE : If the table above is not properly displayed then you can refer Section 2.3.1.1 in readme file. In the section 2.3.1.1 you would get the options to install additional language packs as well. You should copy the PUBLICKEY from the URL below. Please navigate to the following URL:

http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm.

I referred the following documents / blogs to put these steps together :

Thank you very much for visiting my blog and this article. Please keep a watch on this blog for new posts.

SQL Server 2008 - Resource Governor - Part II

Ravi S.Maniam — Sun, 16 Nov 2008 12:01:00 GMT

Hi Friends, I was a bit caught up during these days so I could not update my blogs since a long time. Today again it is a weekend and I have some time so I am writing the article on Resource Governor Part II which is overdue since a long time.

In my first post you would have seen what is the advantage of using Resource Governor and how it works. In this post I will provide you with some sample code. The scenario is that you have one SQL Server 2008 installation and it is used by all the people in the organization. Sales people use it for querying historical sales data, senior executives use it for taking out reports and other useful data and at the same time other people use it for data entry, ad-hoc queries etc. Eventually the DBA finds that the server gets into run-away situation during peek hours. So now the DBA decides to allocate bandwidth each of these user groups.

Let's see a demo script how a DBA will do that.

NOTE : This script was written to execute well on my Laptop so please avoid copy + paste and execute on your production server. This script is provided just to help users understand the concept.

Sample Code

We will do some settings that needs to be done only once per installation. It is not same for all types of server so please refer to the Books Online before performing these settings.

--ONE-TIME SETTINGS

sp_configure 'show advanced', 1

RECONFIGURE

-- Use only 1 CPU (Laptop)

sp_configure 'affinity mask', 1

RECONFIGURE

-- NOTE : It is a best practice to set min & max when using Resource Governor

-- 512 MB is suitable for a Laptop Demo

sp_configure 'min server', 512

sp_configure 'max server', 512

RECONFIGURE

-- END of ONE-TIME settings

We can find out the information on the Resource Governor by querying the DMVs (Dynamic Management View). These DMVs provide us with the information on the resource pools, workload groups and the classifier function.

There will be 2 resource pools and 2 workload groups

already existing in the SQL Server when you will run this

query. Please don't change any of these.

--Get the information on existing Workload Groups

SELECT * FROM sys.dm_resource_governor_workload_groups

--Get the informayion on exissting Resource Pools

SELECT * FROM sys.dm_resource_governor_resource_pools

--Get the information on existing classifier function (if any)

SELECT * FROM sys.dm_resource_governor_configuration

Now we will create two Resource Pools first.

We will create 2 Resource Pools for the Users

1) PoolAdhoc for Generic Users

2) PoolExec for Company Executives

-- Create User pools

CREATE RESOURCE POOL PoolAdhoc

CREATE RESOURCE POOL PoolExec

After creating the Resource Pools we will create the Workload Groups and these Workload Groups will be assigned to respective Resource Pools.

We will create 3 Workload Groups

1) GrpMarketing for Marketing Department Users

2) GrpGeneric for Generic Ad-Hoc query users

3) GrpExec for the Top Level Executives

..and assign them to respective resource pools

1) GrpMarketing to PoolAdhoc

2) GrpGeneric to PoolAdhoc

3) GrpExec to PoolExec

CREATE WORKLOAD GROUP GrpMarketing

USING PoolAdhoc

CREATE WORKLOAD GROUP GrpGeneric

USING PoolAdhoc

CREATE WORKLOAD GROUP GrpExec

USING PoolExec

In the next step we will create SQL User Logins.

Now we will create 3 user logins for 3 different class

of users.

1) UserMarketing for Marketing Department

2) UserGeneric for Generic Users

3) UserExec for Senior Executives

-- create logins to separate users into different groups

CREATE LOGIN UserMarketing WITH PASSWORD = 'UserMarketing1', CHECK_POLICY = OFF

CREATE LOGIN UserGeneric WITH PASSWORD = 'UserGeneric1', CHECK_POLICY = OFF

CREATE LOGIN UserExec WITH PASSWORD = 'UserExec1', CHECK_POLICY = OFF

Now when the user logins are created our next task is to create a Classifier Function. Classifier function tells the Resource Governor on how to handle the incoming request. The classifier function has to be created in the Master database. After the creation of the classifier function we have to make the Resource Governor aware of this function.

We would create classifier function now.

This classifier function has to be created in the

MASTER Database. Please make sure to select the

Master Database

USE master

CREATE FUNCTION RGClassifier()

RETURNS SYSNAME WITH SCHEMABINDING

BEGIN

DECLARE @val varchar(32)

if 'UserExec' = SUSER_SNAME()

SET @val = 'GrpExec';

else if 'UserGeneric' = SUSER_SNAME()

SET @val = 'GrpGeneric';

else if 'UserMarketing' = SUSER_SNAME()

SET @val = 'GrpGeneric';

return @val;

END

-- Make this function

-- known to the Resource Governor

ALTER RESOURCE GOVERNOR

WITH (CLASSIFIER_FUNCTION = dbo.RGClassifier)

Now we can set the priority of the Workload Group or the CPU usage by any Resource Pools etc. as demonstrated in the query below.

-- Adjust PoolAdhoc to not consume more than 50% of CPU

ALTER RESOURCE POOL PoolAdhoc

WITH (MAX_CPU_PERCENT = 50)

-- Make the changes effective

ALTER RESOURCE GOVERNOR RECONFIGURE

-- Adjust PoolExec to not consume more than 30% of CPU

ALTER RESOURCE POOL PoolExec

WITH (MAX_CPU_PERCENT = 30)

-- Make the changes effective

ALTER RESOURCE GOVERNOR RECONFIGURE

-- Alter importance of GrpGeneric

ALTER WORKLOAD GROUP GrpGeneric

WITH (IMPORTANCE = Low)

-- make the changes effective

ALTER RESOURCE GOVERNOR RECONFIGURE

-- Alter importance of GrpMarketing

ALTER WORKLOAD GROUP GrpMarketing

WITH (IMPORTANCE = High)

-- Make the changes effective

ALTER RESOURCE GOVERNOR RECONFIGURE

That is all in this post from my side. If you have any feedbacks then please feel free to share it with me over email.

SQL Server 2008 - Resource Governor - Part I

Ravi S.Maniam — Tue, 22 Jul 2008 23:50:42 GMT

Hi Friends, I am back with one more blog post on an interesting feature in SQL Server 2008. Today I was discussing about run away situations with my colleagues and I found that only few people read about this excellent feature available in SQL Server 2008 so just thought why not to blog about it.

If you are using SQL Server everyday then you would be aware of the situations when you get into run-away situation during the peak load on the server. For example: there is a heavy transaction volume on the server and someone from the remote end fired an ad-hoc query to churn several tables, running to a few million rows and everything comes to a screeching halt. You would have always wondered if there was a way to manage this to avoid run-away situation. Even if there was any solution that sort you would have wondered can it be done on the fly with a minimal impact.

What is run-away ?

To explain it in a very simplified manner, every server hardware has a finite number of CPUs and amount of RAM installed on it. When you try to fire a query that is resource intensive and the hardware resources are not available to serve the request ..you get into a run-away situation due to which the service requested is delayed and other requests being handled by the server in parallel are also delayed.

So what is the solution ?

In an environment where multiple distinct workloads are present on the same server, Resource Governor enables you to differentiate these workloads and allocate shared resources as they are requested, based on the limits that you specify. These resources are CPU and memory.

Resource Governor

Resource Governor is a new technology in SQL Server 2008 that enables you to manage SQL Server workload and resources by specifying limits on resource consumption by incoming requests. In the Resource Governor context, workload is a set of similarly sized queries or requests that can, and should be, treated as a single entity. This is not a requirement, but the more uniform the resource usage pattern of a workload is, the more benefit you are likely to derive from Resource Governor.

It is feature that is designed to manage the resource limits in real time with minimal impact on workloads that are executing.

Issues addressed by Resource Governor

Resource Governor addresses 3 primary issues that are prevalent in the database environments.

Run-Away : A situation where one process eats up all the resources and another process starves.
Workload Priority : A situation where we need to prioritise one workload type over another viz. a current payment transaction over another query that is crunching millions of rows to take out some summarized information which is expected to run for a few minutes.
Unpredictable workload execution : A situation similar to this one where two data warehouse applications are a mix of OLTP and data warehouse applications. These applications are not isolated from each other and the resulting resource contention causes unpredictable workload execution.

All of the above scenarios require the ability to differentiate workloads in some way. Resource Governor provides:

The ability to classify incoming connections and route their workloads to a specific group (Identifying a workload group based on an incoming connection).
The ability to monitor resource usage for each workload in a group.
The ability to pool resources and set pool-specific limits on CPU usage and memory allocation. This prevents or minimizes the probability of run-away queries.
The ability to associate grouped workloads with a specific pool of resources.
The ability to identify and set priorities for workloads. (Setting the priority or Low, Medium, High)

Scope of Resource Governor

There is a clear scope in which Resource Governor works and it is important to understand the scope of it.

It is only manages the CPU Bandwidth and the RAM managed by the SQL Server 2008.
Resource Governor itself will not optimise any slow running queries.
No load balancing will be done between multiple SQL Server instances.
It does not divide the server into isolated pieces.
OLTP workloads. Resource Governor can manage OLTP workloads but these types of queries, which are typically very short in duration, are not always on the CPU long enough to apply bandwidth controls. This may skew in the statistics returned for CPU usage %.

How Resource Governor Works

The following three concepts are fundamental to understanding and using Resource Governor:

Resource pools. Two resource pools (internal and default) are created when SQL Server 2008 is installed. Resource Governor also supports user-defined resource pools.
Workload groups. Two workload groups (internal and default) are created and mapped to their corresponding resource pools when SQL Server 2008 is installed. Resource Governor also supports user-defined workload groups.
Classification. There are internal rules that classify incoming requests and route them to a workload group. Resource Governor also supports a classifier user-defined function for implementing classification rules.

Explanation (Step by Step):

There is an incoming connection for a session (Session 1 of n).
The session is classified (Classification).
The session workload is routed to a workload group.(Workload Group 1)
The workload group uses the resource pool it is associated with, for example, Pool 1.
The resource pool provides and limits the resources required by the application, for example, Application 1

For more information on Resource Governor you may visit SQL Server 2008 Books Online.

I will write more about the Resource Governor very soon so keep a watch.

SQL Server 2008 - Auditing

Ravi S.Maniam — Mon, 21 Jul 2008 04:08:23 GMT

Hi Friends, I am back again with one more blog post on SQL Server 2008 Auditing.

As we all know that SQL Server 2008 is coming up with *Cool* enhancements that will help the End Users, DBAs, Developers in improving their productivity. Today I am going to blog about a feature which would be liked by people who maintain the compliance with the Security Standards.

Before the advent of SQL Server 2008, auditing was done using SQL Server Traces and Profiler. Now Auditing is an integral object in SQL Server 2008.

So what is Auditing in SQL Server..

Auditing an instance of SQL Server or a SQL Server database involves tracking and logging events that occur on the system. Based on the information accumulated we would be able to track the changes to the database, access to the database etc. An audit is the combination of several elements into a single package for a specific group of server actions or database actions. The components of SQL Server Audit combine to produce an output that is called an audit, just as a report definition combined with graphics and data elements produces a report. SQL Server Audit uses Extended Events to help create an audit.

While we are working with SQL Server 2008 auditing we need to keep four things in mind:

SQL Server Audit
Server Audit Specification (Events to capture on the Server Instance Level)
Database Audit Specification (Events to capture on a specific database)
Target (Where would be the events be logged)

Note: I will be using the definitions In Books Online to explain you these 4 objects because I think they are perfect and very easy to understand.

SQL Server Audit

The SQL Server Audit object collects a single instance of server or database-level actions and groups of actions to monitor. The audit is at the SQL Server instance level. You can have multiple audits per SQL Server instance. When you define an audit, you specify the location for the output of the results. This is the audit destination. The audit is created in a disabled state, and does not automatically audit any actions. After the audit is enabled, the audit destination receives data from the audit.

Server Audit Specification

The Server Audit Specification object belongs to an audit. You can create one server audit specification per audit, because both are created at the SQL Server instance scope. The server audit specification collects many server-level action groups raised by the Extended Events feature. You can include audit action groups in a server audit specification. Audit action groups are predefined groups of actions, which are the atomic events exposed by the Database Engine. These actions are sent to the audit, which records them in the target.

Server-level audit action groups are described in the topic SQL Server Audit Action Groups and Actions.

Database Audit Specification

The Database Audit Specification object also belongs to a SQL Server Audit. You can create one database audit specification per SQL Server database per audit. The database audit specification collects database-level audit actions raised by the Extended Events feature. You can add either audit action groups or audit events to a database audit specification. Audit events are the atomic actions that can be audited by the SQL Server engine. Audit action groups are predefined groups of actions. Both are at the SQL Server database scope. These actions are sent to the audit, which records them in the target. Database-level audit action groups and audit actions are described in the topic SQL Server Audit Action Groups and Actions.

Target

The results of an audit are sent to a target, which can be a file, the Windows Security event log, or the Windows Application event log. (Writing to the Security log is not available on Windows XP.) Logs must be reviewed and archived periodically to make sure that the target has sufficient space to write additional records. Writing to the Windows Security log requires the SQL Server service account to be added to the Generate security audits policy. By default, the Local System, Local Service, and Network Service are part of this policy. This setting can be configured by using the security policy snap-in (secpol.msc). Additionally, the Audit object access security policy must be enabled for both Success and Failure. This setting can be configured by using the security policy snap-in (secpol.msc). In Windows Vista or Windows Server 2008, you can set the more granular application generated policy from the command line by using the audit policy program (AuditPol.exe). For more information about the steps to enable writing to the Windows Security log,see How to: Write Server Audit Events to the Security Log. For more information about the Auditpol.exe program, see Knowledge Base article 921469, How to use Group Policy to configure detailed security auditing. The Windows event logs are global to the Windows operating system. For more information about the Windows event logs, see Event Viewer Overview. If you need more precise permissions on the audit, use the binary file target. For more information about the audit records written to the target, see SQL Server Audit Records.

NOTE: Any authenticated user can read and write to the Windows Application event log. The Application event log requires lower permissions than the Windows Security event log and is less secure than the Windows Security event log.

Step By Step Walk Through

Now when you have understood Auditing Objects in SQL Server 2008, let me walk you through the process of creating an Audit in SQL Server 2008. I bet that it will be a good fun learning this feature in spite of the seriousness of the role of Auditing. In SQL Server 2008, the product team has made sure that the features are simple to use for the end users in spite of the underlying complexity. So let's start and explore.

Note: You can click on the images below to maximize.

Step 1:

Click open SQL Server 2008 Management Studio and log into it.

Step 2:

Explore the Security node in Object Explorer and select the Audit node.

Step 3:

Right click on the Audit node and select the option "New Audit" from the menu.

Step 4:

Now SQL Server 2008 will open up a dialog box "Create Audit" with a few fields. It is important to understand the significance of each of these fields. The details of these fields are provided below.

Audit name
The name of the audit. This is generated automatically when you create a new audit but is editable.

Queue delay (in milliseconds)
Specifies the amount of time in milliseconds that can elapse before audit actions are forced to be processed. A value of 0 indicates synchronous delivery. The default minimum value is 1000 (1 second). The maximum is 2,147,483,647 (2,147,483.647 seconds or 24 days, 20 hours, 31 minutes, 23.647 seconds).

Shut down server on audit failure
Forces a server shut down when the server instance writing to the target cannot write data to the audit target. The login issuing this must have the SHUTDOWN permission. If the logon does not have this permission, this function will fail and an error message will be raised.

As a best practice, this should only be used in cases where an audit failure could compromise the security or integrity of the system.

Audit destination
Specifies the target for auditing data. The available options are a binary file, the Windows Application log, or the Windows Security log. SQL Server cannot write to the Windows Security log without configuring additional settings in Windows. For more information, see How to: Write Server Audit Events to the Security Log.

Note: Writing to the Security log is not available on Windows XP.

File path
Specifies the location of the folder where audit data is written when the Audit destination is a file. Clicking the button beside this field opens the Browse For Folder dialog to specify a file path or create a folder where the audit file is written.

Maximum rollover files
Specifies the maximum number of audit files to retain in the file system. When the setting of MAX_ROLLOVER_FILES=UNLIMITED, there is no limit imposed on the number of rollover files that will be created. The default value is UNLIMITED. The maximum number of files that can be specified is 2,147,483,647.

Maximum file size (MB)
Specifies the maximum size, in megabytes (MB), for an audit file. The minimum size that you can specify is 1024 KB and the maximum is 2,147,483,647 terabytes (TB). You can also specify UNLIMITED, which does not place a limit on the size of the file. Specifying a value lower than 1024 KB will raise the error MSG_MAXSIZE_TOO_SMALL. The default setting is UNLIMITED.

Reserve disk space
Specifies that space is pre-allocated on the disk equal to the specified maximum file size. This setting can only be used if MAXSIZE is not equal to UNLIMITED. The default setting is OFF.

Now after filling up appropriate values in the dialog box, press OK to create an Audit.

Step 5:

Now once the Audit is created, it could be found under the Security>>Audit node. Now to enable the Audit, just right click on the Server Audit that we have just created and from the menu select "Enable Audit".

You would see a dialog box with the success message, if the operation succeeds.

Step 6:

You can right click on the Audit just created and select the option "View Audit Logs". This opens up a dialog box that contains the audit logs.

You can also script the created policy. Right click on the Audit, select "Script Audit As" >> "Create To" >> (File/ Clipboard / Agent Job).

As we know that Policy Based Management is now an integral part of the SQL Server 2008 so if you would like to create a policy for this Audit then it is very easy to do that. You have to right click on the Audit just created, select the option "Facets" from the menu.

It brings up a dialog box that provides you with the status of the Audit. On the lower right corner of this dialog box you would find a button "Export Current State as Policy".

When you click on the button "Export Current State as Policy", it brings up another dialog box that shows the Policy Name and the condition name which is editable. You can select the appropriate option below these fields to apply this policy on the local server or to save it as a Policy file. If you select the "local server" option, you would see that a Policy and a Condition has been created with the name you have specified in the dialog box.

Step 7:

Now we will create the Server Audit Specification.

Before continuing further I would strongly recommend you to visit the TechNet Article : Server Audit Action Groups and Actions.

Once you have understood the Server Audit Action Groups, explore the node Security >> Audits >> Server Audit Specifications in the Object Explorer in the SQL Server 2008. Right click on the Server Audit Specifications and select "New Server Audit Specification".

When you select this option a dialog box appears in which you would specify Server Audit Specification Name and "Server Audit" that you have created in the Step 6. Thereafter you would specify the Audit Action Groups in the grid below. Once you have selected all the required Audit Action Groups, you would press OK and you would see an Audit Specification created for the server. In this Step I have selected the Audit Action Group "Backup Restore Group" and this event is raised whenever a backup or restore command is issued.

Once it is created, you would see that the Audit Specification is in the disabled state. You have to right click on the Audit Specification that you have just created and select "Enable Server Audit Specification" from the menu.

Just after that, you would see a dialog box saying, "The operation was successful" unless you have done something funny to make it fail. :-)

You may right click on the Server Audit Specification and select Facets from the menu. This brings up a dialog box with a button on the right bottom saying "Export Current State as Policy". Click on that button to create a policy as we have done above.

Step 8:

Now let's try backing up a database on the server. I have used AdventureWorksLT database for the demonstration. Then we will see the logs to assure that our Audit is working.

Explore the nodes in the Object Explorer, Databases >> AdventureWorksLT. Right click on the AdventureWorksLT database and select Tasks >> Backup.

This brings up the following dialog box to create a backup of the database. Please fill in appropriate values in the fields of this dialog box and press the button OK. For more information or help on taking backup please visit Books on Line.

You would see the backup successfully completes.

Now right click on the Server Audit we created in the Object Explorer and select the option View Audit Logs from the menu.

This will bring up the dialog box that will show the details of the backup event. In the picture below you would see the back up event that happened on the AdventureWorksLT database. You can scroll to the right to find the details in the dialog box.

Step 9:

Now we would create a Database Audit Specification. I would use the AdventureWorksLT database for the demonstration. You may visit the TechNet Article : Server Audit Action Groups and scroll down to "Database-Level Audit Action Groups" and "Database-Level Audit Actions" sections in this article to find more information.

The scenario is we want to Audit every select, insert, update, delete operation done on the SalesLT.Product table by anyone.

Explore the Database >> AdventureWorksLT >> Security >> Database Audit Specifications nodes in the Object Explorer. Now right click on the "Database Audit Specifications" node and select "New Database Audit Specification" from the menu.

This will open up a new dialog box with the Title - "Create Database Audit Specification".

Now we need to Give the Database Audit Specification a name and then select the Server Audit name from the drop down list.

Within the grid in the "Audit Action Type" choose "SELECT" from the drop down list, in the "Object Class" select "OBJECT". Click on the button beside Object Name text box, which opens up a dialog box. Select SalesLT.Product table which will bring "SalesLT" in "Object" and "Product" in "Object Name". Now click the button beside the text box under the section "Principal Name", select "public" by browsing the objects in the dialog box that appears once you click the button.

Repeat the operation for the Audit Action Type INSERT, UPDATE, DELETE. Then finally press OK.

This will create a Database Audit Specification for you which is not enabled. Right click on this Database Audit Specification and select "Enable Database Audit Specification" from the menu.

Once it the operation completes.. a dialog box appears confirming the success of the operation.

You can create a policy out of this Database Audit Specification by right clicking on the Database Audit Specification and selecting the option "Facets" and following the procedure in the similar way how we have done previously.

Step 10: (Last Step)

Now we would fire the query "Select * from SalesLT.Product" against the AdventureWorksLT database.

After that you may explore the Security Node in the Object Explorer. <SQL Instance Name> >> Security >> Audits and then right click on the server audit that is already created and select "View Audit Logs" from the menu.

Now the dialog box appears, it has the audit log that says that you have selected the SalesLT.Product table in the AdventureWorksLT Database. You may scroll to the right in the dialog box to find detailed information.

Wow! You have learned to work with this new new feature in just 10 steps.

Wasn't that very easy.

Thanks guys, to take a look at this post, I hope you enjoyed the article. Your comments and feedbacks are valuable so drop me an email. I would be happy to hear back from you, it gives me an opportunity to improve and gives me pleasure to bring new articles.

I will bring in more articles soon so keep a ...

Bye now !

Policy-Based Management : SQL Server 2008

Ravi S.Maniam — Wed, 09 Jul 2008 22:08:41 GMT

NOTE: Declarative Management Framework has been renamed to Policy-Based Management so I just changed the Title of the article, the contents are unchanged.

Hi, I am writing this post after somewhat long time … I hope you all are continuing with your learning on SQL Server 2008. Today I have some time to blog so I am writing something.

So after thinking hard what to write about I thought why not to write about the Declarative Management Framework. A wonderful solution for the DBAs who keep themselves busy patching and closing the mouse holes what other folks have created by violating some of the best practices, may it be naming convention of the Tables or they have created the Stored Proc. in the wrong schema. So if you are wondering what is this “Declarative Management Framework” then, please stop wondering and download the latest SQL Server 2008 November 2007 available, install it, read this article and start practicing. I promise you will like it.

What is Declarative Management Framework

Declarative Management Framework is a policy-based system for managing one or more instances of SQL Server 2008 which means that now rather than turning on/off the physical knobs to do the effective database administration you would have logical knobs to do it which could even be exported to a file for the future use and could be applied to a bunch of SQL Servers in a Group.

DBAs don't have to worry, it is not any other Framework like .Net Framework where you need to reach the Visual Studio and write custom code, test it, deploy and manage it. It is very simple and all the policies could be authored well from the SQL Server 2008 Management Studio.

Components of Declarative Management Framework

Declarative Management Framework has three components:

Policy management
Explicit administration
Automated administration

Policy Management

Policy administrators create policies.

Explicit Administration

Administrators select one or more managed targets and explicitly check that the targets comply with a specific policy, or explicitly make the targets comply with a policy.

Automated Administration

Policy administrators can run policies on demand, or enable automated policy execution by using one of the following execution modes:

Changes are attempted, prevent out-of-compliance. This uses DDL triggers to prevent policy violations.
Changes are attempted, log out-of-compliance. This uses event notification to evaluate a policy when a relevant change occurs.
On schedule, log out-of-compliance. This uses a SQL Server Agent job to periodically evaluate a policy.

When automated policies are not enabled, Declarative Management Framework will have no effect on system performance. If enabled the system will have only negligible effect on the performance depending on the number of policies applied on a particular object.

Declarative Management Framework - Key Terms and Concepts

Managed Target
Entities that are managed by Declarative Management Framework, such as an instance of the SQL Server Database Engine, a database, a table, or an index. All targets in a server instance form a target hierarchy. A target set is the set of targets that results from applying a set of target filters to the target hierarchy, for example, all the tables in the database owned by the HumanResources schema.

Facet
A set of logical properties that model the behavior or characteristics for certain types of managed targets. The number and characteristics of the properties are built into the facet and can be added or removed by only the maker of the facet. A target type can implement one or more management facets, and a management facet can be implemented by one or more target types.

Condition
A Boolean expression that specifies a set of allowed states of a Declarative Management Framework managed target with regard to a management facet.

Policy
A Declarative Management Framework condition and the expected behavior, for example, execution mode, target filters, and schedule. A policy can contain only one condition. Policies can be enabled or disabled.

Category
A user-defined category to help manage policies. Users can classify policies into different policy categories. A policy belongs to one and only one policy category. Database owners can subscribe a database to a set of policy categories. Only policies from its subscribed categories can govern a database. All databases implicitly subscribe to the default policy category.

Execution Mode
Specifies how a policy will be executed. On-demand execution modes are Check and Configure. Automated execution modes are:

Changes are attempted, prevent out-of-compliance
Changes are attempted, log out-of-compliance
On schedule, log out-of-compliance

Effective Policy
The effective policies of a target are those policies that govern this target. A policy is effective with regard to a target only if all the following conditions are satisfied:

The policy is enabled.
The target belongs to the target set of the policy.
The target or one of the targets ancestors subscribes to the policy group that contains this policy.

Usage Scenarios : Examples

Declarative Management Framework would be helpful in resolving the issues presented in the following scenarios:

A company policy prohibits enabling Database Mail or SQL Mail. A policy is created to check the server state of those two features. An administrator compares the server state to the policy. If the server state is out of compliance, the administrator chooses the Configure mode and the policy brings the server state into compliance.
The AdventureWorks database has a naming convention that requires all stored procedures to start with the letters AW_. A policy is created to enforce this policy. An administrator tests this policy and receives a list of stored procedures that are out of compliance. If future stored procedures do not comply with this naming convention, the creation statements for the stored procedures fail.

A Quick Walk Through : Declarative Management Framework

We are going to create a quick policy that will make sure that the CLR integration is not enabled on this instance of SQL Server 2008. I am adding screen shots below, in case they are not clearly visible, click on them and they will be enlarged.

Step 1: We will reach the SQL Server 2008 Management Studio, log in and then expand the Management Node as demonstrated below.

Step 2: Now we will first create a condition so expand the node CONDITION and right click and in the menu select "New Condition". A new dialog box appears, in the "Name" field type in a name for this condition like "Condition_Disable_CLR" or any fancy name you like. In the Facet select "Server Configuration". Please see the screen shot below.

Step 3: In the Expression section reach the Field and select "@ClrIntegrationEnabled" from the Drop Down, Operator should be "=" and in the Value field select "False" from the Drop Down. Press OK and you have created a condition.

Step 4: Now it is the time to create a policy based on this condition. So right click on the "Policies" node in the Management Studio. Select "New Policy" from the menu. This brings up a new dialog box. In the "Name" field type in a name for the policy like "Policy_Disable_CLR". In the "Check Condition" select the condition that you have authored last in this case "Condition_Disable_CLR" which you would find under "Server Configurations". Select the "Execution Mode" as "On Demand" and Press OK.

Congratulations !!! you have created your first policy on the SQL Server 2008 Server.

Step 5: Now expand the "Policies" Node in the Management Studio and locate the Policy that you have created just now.

Step 6: Right click on the Policy and select "Test Policy" this will bring up the dialog box. If the CLR Integration is disabled on this Server instance then it will be notified else if the CLR was enabled anytime then it will be notified.

Policy Not Violated

Step 7: Now I will enable the CLR by executing the System Stored Procedure

sp_configure 'clr enabled', 1

Now we will execute "RECONFIGURE" to make the changes effective.

We will now retest the policy and see the result.

Policy Violated

So, I hope the DBAs will find it comfortable authoring policies for effective administration. If you like or dislike the article please post it .. it helps me to bring better articles every time. I will bring more articles on SQL Server 2008 Enhancements so keep a watch.

I use Windows Live Writer to write my blogs... what do you use ?

SQL Server 2008 - Change Data Capture - Part II

Ravi S.Maniam — Tue, 08 Jul 2008 03:38:00 GMT

Hi ! It's been a long time since I last updated my blog. To continue with the Change Data Capture feature of SQL Server 2008, this is new post that helps you to know how you can write your own stored procedures / functions to get the required data in the fashion you want, using the CDC functions provided by Microsoft.

NOTE: If you haven't read the article "SQL Server 2008 - Change Data Capture - Part I" then I would recommend you to please visit the article first else you won't be able to connect well, what I am trying to express here.

The following function works in the similar fashion like cdc.fn_cdc_get_all_changes_InstanceHumanResourcesEmployee but this function will take the starting time and ending time i.e. the time range and the row filter option. The row filter option will either be 'all' or 'all update old'.

cdc.fn_cdc_get_all_changes_InstanceHumanResourcesEmployee always matches the LSN number provided by you with the LSN present in the CDC table and if it is not found it will throw an error. The reason is it will check for the exact LSN Number so that duplicate records don't creep into the result set. The following function is more generic and will tell you about the changes that happened to a table within a time range. The logic is created in a fashion that if there are no records existing in the table matching the criteria specified by you then it will return an empty set.

This is just an example to demonstrate that how we could write our own SPs and Functions to get the data from the Change Tables.

This function will return all the changes happened to the table

within a specific time period.

It will accept any valid date and time range and accepts row filters

-> all

-> all update old

create function [cdc].[fn_cdc_get_changes_within_time_period]

( @from_time datetime2(7),

@to_time datetime2(7),

@row_filter_option nvarchar(30)

)

RETURNS @return_table TABLE

(

[__$start_lsn] [binary](10) NOT NULL,

[__$seqval] [binary](10) NOT NULL,

[__$operation] [int] NOT NULL,

[__$update_mask] [varbinary](128) NULL,

[EmployeeID] [int] NULL,

[NationalIDNumber] [nvarchar](15) NULL,

[ContactID] [int] NULL,

[LoginID] [nvarchar](256) NULL,

[ManagerID] [int] NULL,

[Title] [nvarchar](50) NULL,

[BirthDate] [datetime] NULL,

[MaritalStatus] [nchar](1) NULL,

[Gender] [nchar](1) NULL,

[HireDate] [datetime] NULL,

[SalariedFlag] [bit] NULL,

[VacationHours] [smallint] NULL,

[SickLeaveHours] [smallint] NULL,

[CurrentFlag] [bit] NULL,

[rowguid] [uniqueidentifier] NULL,

[ModifiedDate] [datetime] NULL

)

BEGIN

DECLARE @from_lsn binary(10),

@to_lsn binary(10);

SELECT @from_lsn = MIN([__$start_lsn])

FROM cdc.InstanceHumanResourcesEmployee_CT

WHERE sys.fn_cdc_map_lsn_to_time ([__$start_lsn]) >= @from_time AND

sys.fn_cdc_map_lsn_to_time ([__$start_lsn]) <= @to_time ;

SELECT @to_lsn = MAX([__$start_lsn])

FROM cdc.InstanceHumanResourcesEmployee_CT

WHERE sys.fn_cdc_map_lsn_to_time ([__$start_lsn]) <= @to_time AND

sys.fn_cdc_map_lsn_to_time ([__$start_lsn]) >= @from_time ;

IF ISNULL(@from_lsn,0) <> 0 AND ISNULL(@to_lsn,0) <> 0 AND @from_time <= @to_time

BEGIN

INSERT INTO @return_table

select

NULL as __$start_lsn,

NULL as __$seqval,

NULL as __$operation,

NULL as __$update_mask, NULL as [EmployeeID],

NULL as [NationalIDNumber],

NULL as [ContactID],

NULL as [LoginID],

NULL as [ManagerID],

NULL as [Title],

NULL as [BirthDate],

NULL as [MaritalStatus],

NULL as [Gender],

NULL as [HireDate],

NULL as [SalariedFlag],

NULL as [VacationHours],

NULL as [SickLeaveHours],

NULL as [CurrentFlag],

NULL as [rowguid],

NULL as [ModifiedDate]

where ( [sys].[fn_cdc_check_parameters]

( N'InstanceHumanResourcesEmployee', @from_lsn, @to_lsn, lower(rtrim(ltrim(@row_filter_option))), 0) = 0)

union all

select t.__$start_lsn as __$start_lsn,

t.__$seqval as __$seqval,

t.__$operation as __$operation,

t.__$update_mask as __$update_mask, t.[EmployeeID], t.[NationalIDNumber], t.[ContactID], t.[LoginID], t.[ManagerID], t.[Title], t.[BirthDate], t.[MaritalStatus], t.[Gender], t.[HireDate], t.[SalariedFlag], t.[VacationHours], t.[SickLeaveHours], t.[CurrentFlag], t.[rowguid], t.[ModifiedDate]

from [cdc].[InstanceHumanResourcesEmployee_CT] t

where (lower(rtrim(ltrim(@row_filter_option))) = 'all')

and ( [sys].[fn_cdc_check_parameters]( N'InstanceHumanResourcesEmployee', @from_lsn, @to_lsn, lower(rtrim(ltrim(@row_filter_option))), 0) = 1)

and (t.__$operation = 1 or t.__$operation = 2 or t.__$operation = 4)

and (t.__$start_lsn <= @to_lsn)

and (t.__$start_lsn >= @from_lsn)

union all

select t.__$start_lsn as __$start_lsn,

t.__$seqval as __$seqval,

t.__$operation as __$operation,

from [cdc].[InstanceHumanResourcesEmployee_CT] t

where (lower(rtrim(ltrim(@row_filter_option))) = 'all update old')

and ( [sys].[fn_cdc_check_parameters]( N'InstanceHumanResourcesEmployee', @from_lsn, @to_lsn, lower(rtrim(ltrim(@row_filter_option))), 0) = 1)

and (t.__$operation = 1 or t.__$operation = 2 or t.__$operation = 4 or

t.__$operation = 3 )

and (t.__$start_lsn <= @to_lsn)

and (t.__$start_lsn >= @from_lsn)

END

RETURN

END

I hope people are enjoying to work with SQL Server 2008, just in case if you have missed these following links, please visit them today.

Keep writing to me & keep a watch on my blog. I will bring new articles, on new features of SQL Server 2008 very soon. Till then ... Bye !