Skip to main content

Enhancements to Top Keyword in Yukon

There are loads of new features in Sql Server 2005 code named Yukon. Out of which in this article let me explain briefly the enhancements made to TOP keyword in this version of the product.

Let us first create a sample table and populate some dummy records into it.

Create table TestTopOptionYukon
(
YearOfSales Int,
SalesQuarter Int,
Amount money
)
go

Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2003, 1, 100)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2003, 2, 200)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2003, 3, 300)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2003, 4, 400)
go

Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2004, 1, 500)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2004, 2, 600)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2004, 3, 700)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2004, 4, 800)
go

Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2005, 1, 900)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2005, 2, 1000)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2005, 3, 1100)
Insert into TestTopOptionYukon (YearOfSales, SalesQuarter, Amount) Values (2005, 4, 1200)
go

The below code snippet would work in both SQL Server 2000 and SQL Server 2005

/*
TSQL stops proceessing when they have been affected by the specified no of rows
*/

Set RowCount 2

-- First two records salesquarter would be set as 999
Begin Tran
Update TestTopOptionYukon SET SalesQuarter = 999
If @@RowCount = 0
Begin
Print 'No Record found'
Set RowCount 0
End
Commit Tran

To list all the records again we need to set the RowCount as 0.

Set RowCount 0
Select * from TestTopOptionYukon

The below code snippet would work only in SQL Server 2005.

As you could see Set Rowcount statement is not used at all. Instead we have made use of TOP keyword.

Begin Tran
Update TOP (2) TestTopOptionYukon SET SalesQuarter = 999
If @@RowCount = 0
Begin
Print 'No Record found'
Set RowCount 0
End
Commit Tran

Passing parameters to the TOP keyword

One of the feature which was missing in Sql Server 2000 was passing parameters to the TOP keyword. That is now possible in Yukon.

Declare @topValue Int
Set @topValue = 2
Select Top (@topValue) * from TestTopOptionYukon

Even if you give decimal Values it takes only the integer part and ignores the decimal part. The below query would list the Top 2 records.

Declare @topValue Int
Set @topValue = 2.9
Select Top (@topValue) * from TestTopOptionYukon

Listing Top n percentage of records from a table

Declare @topValue Int
Set @topValue = 25
Select TOP (@topValue) Percent * from TestTopOptionYukon

Out of all the coolest enhancement is we could now pass a query as a parameter to TOP keyword.

The below code snippet helps us in finding out the top half of the exisitng records.

--It would list 50% of the records i.e, in our case top 6 records
Select TOP (Select cast((Select Count(*)/2 from TestTopOptionYukon) as int)) * from TestTopOptionYukon

Comments

Popular posts from this blog

Registry manipulation from SQL

Registry Manupulation from SQL Server is pretty easy. There are 4 extended stored procedure in SQL Server 2000 for the purpose of manupulating the server registry. They are: 1) xp_regwrite 2) xp_regread 3) xp_regdeletekey 4) xp_regdeletevalue Let us see each one of them in detail! About xp_regwrite This extended stored procedure helps us to create data item in the (server’s) registry and we could also create a new key. Usage: We must specify the root key with the @rootkey parameter and an individual key with the @key parameter. Please note that if the key doesn’t exist (without any warnnig) it would be created in the registry. The @value_name parameter designates the data item and the @type the type of the data item. Valid data item types include REG_SZ and REG_DWORD . The last parameter is the @value parameter, which assigns a value to the data item. Let us now see an example which would add a new key called " TestKey ", and a new data item under it called TestKeyValue :

Screen scraping using XmlHttp and Vbscript ...

I wrote a small program for screen scraping any sites using XmlHttp object and VBScript. I know I haven't done any rocket science :) still I thought of sharing the code with you all. XmlHttp -- E x tensible M arkup L anguage H ypertext T ransfer P rotocol An advantage is that - the XmlHttp object queries the server and retrieve the latest information without reloading the page. Source code: < html > < head > < script language ="vbscript"> Dim objXmlHttp Set objXmlHttp = CreateObject("Msxml2.XMLHttp") Function ScreenScrapping() URL == "UR site URL comes here" objXmlHttp.Open "POST", url, False objXmlHttp.onreadystatechange = getref("HandleStateChange") objXmlHttp.Send End Function Function HandleStateChange() If (ObjXmlHttp.readyState = 4) Then msgbox "Screenscrapping completed .." divShowContent.innerHtml = objXmlHttp.responseText End If End Function </ script > < head > < body > &l

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul