CREATE TABLE [##tbReferenceDataTemp]
(
[AccountAbbrv] [VARCHAR](100) NULL,
[CountryAbbrv] [VARCHAR](100) NULL,
[OCC] [VARCHAR](5) NULL,
[Region] [VARCHAR](100) NULL
)
END

INSERT INTO [##tbReferenceDataTemp]

SELECT wcs.[Account Abbreviation],wcs.[Country Abbreviation],wcs.[OCC Code],wcs.[Account Region] FROM wcs

select @sql = ‘bcp ##tbReferenceDataTemp out c:\Details.txt -c -t, -r”\n” -T -S’ + @@servername
exec master..xp_cmdshell @sql

–Rowcount Details
SELECT @ROWCOUNT=COUNT(1) FROM ##tbReferenceDataTemp
SET @ROWCOUNT=@ROWCOUNT+2
SET @RowcountDetails=@ROWCOUNT

–Transmission Date
SELECT @Transmissiondate=CONVERT(VARCHAR(10),GETDATE(),112)
SELECT @Header=’echo’+’ H,’+'Txt,’+@Transmissiondate+’ >> c:\Header.txt’
exec master..xp_cmdshell @Header

–Filename creation
SET @FileName=’ATT_ISTARS_WCS_REFDATA_’+@Transmissiondate+’.TXT’

–Trailer Information
SELECT @Trailer=’echo’+’ TRAILER,’+@RowcountDetails+’ >> c:\’+@FileName

–Copy the Header information to Details information
SELECT @Copyfile=’copy /Y c:\Header.txt + c:\Details.txt ‘+’C:\’+@FileName

exec master..xp_cmdshell @Copyfile
exec master..xp_cmdshell @Trailer

–Deleting the Temporary files
exec master..xp_cmdshell ‘del c:\Details.txt’
exec master..xp_cmdshell ‘del c:\Header.txt’

drop table ##tbReferenceDataTemp
END TRY
BEGIN CATCH

Let us create one very simple CLR where we will print current system datetime.

1) Open Microsoft Visual Studio >> Click New Project >> Select Visual C# >> Database >> SQL Server Project

2) Either choose from existing database connection as reference or click on Add New Reference. In my example I have selected Add New Reference
3) If you have selected existing reference skip to next step or add database reference as displayed in image.
4) Once database reference is added following project will be displayed in Solution Explorer. Right click on Solution Explorer >> Click on Add >> Stored Procedure.
5) Add new stored procedure template from following screen.
6) Once template added it will look like following image.
7) Now where it suggest to //Put your code here. Replace it with code displayed in the image. Once the code is complete do following two steps.
a) Click on menu bar >> Build >> Build ProjectName
b) Click on menu bar >> Build >> Deploy ProjectName
Building and Deploying project should give successful message

using System;
using System.Data;
using System.Data.SqlClient;
using System.Data.SqlTypes;
using Microsoft.SqlServer.Server;

public partial class StoredProcedures
{
[Microsoft.SqlServer.Server.SqlProcedure]
public static void CLRSPTest()
{
SqlPipe sp;
sp = SqlContext.Pipe;
String strCurrentTime = “Current System DateTime is: “
+ System.DateTime.Now.ToString();
sp.Send(strCurrentTime);
}
};
Now open SQL Server Management Studio and run following script in Query Editor. It should return current system datetime. Running it again the time will change.
USE AdventureWorks
GO
EXEC dbo.CLRSPTest
GO

Reference : Pinal Dave (http://blog.SQLAuthority.com)

http://blog.sqlauthority.com/2008/10/19/sql-server-introduction-to-clr-simple-example-of-clr-stored-procedure/

1. HttpWatch to show the network traffic.
Here’s how the network traffic looked before any optimization:

And we can see there are totally 22 requests and spend 9 seconds to get the 654k result. It is a really terrible in performance.
2. ScriptReferenceProfiler to show the JavaScript reference.
ScriptReferenceProfiler is an open source tool on CodePlex, for analysis the JavaScript references of ASP.NET AJAX, we can simply add the following code to our page in order to show the JavaScript references imported by ScriptManager.

We can see, before any optimization, there are 17 references found on this page, include the Microsoft Ajax Core runtime, asynchronous postback scripts, Ajax Control Toolkit Extender scripts and so on:

Optimization in web.config
To optimize the ASP.NET AJAX in our web application, first of all, we need to make sure the Compression and Caching is enabled in our web.config:

1. Enable The Caching:
We know, in the development of web application, enable the caching is a must operation. To enable the caching of ASP.NET AJAX, we need make sure the enableCaching property of scriptResourceHandler is set to true.

As our expected, the page response more quickly in the second time, the expend time is coming from 12.862 seconds down to 0.409seconds; and the received size from server decrease from 692K to 14K.

2. Enable The Compression:
The Caching will saving almost 95% of the network traffic in the second time we request the page, however, the first page request still ask for a huge data from server. How to reduce the first request? don’t worry, set enableCompression property of scriptResourceHandler to true will help:

As we can see in the screen shot, many script files are getting smaller. and the total size decrease form 692K to 183K, about 1/4 compare to before.

♣Note: The compression is not work in Internet Explorer 6.0, because there is an known bug in IE 6, that cause the mistake might be occur when receiving the Gzip header. So the develop team close all the compression ability in IE 6.

Optimization in ScriptManager
The ScriptManager control manages client script for AJAX-enabled ASP.NET Web pages. By default, the ScriptManager control registers the script for the Microsoft AJAX Library with the page. This enables client script to use the type system extensions and to support features such as partial-page rendering and Web-service calls. Following, we need to setting the property of ScriptManager to optimize the performance of ASP.NET AJAX.

1. ScriptMode for Release
In one of Scott Guthrie’s post, he explain that we should avoid when deploying an ASP.NET application into production leave the switch on within the application’s web.config file.

It will cause:

1) The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)

2) Code can execute slower (since some additional debug paths are enabled)

3) Much more memory is used within the application at runtime

4) Scripts and images downloaded from the WebResources.axd handler are not cached

In this scenario, we can set the ScriptManager on the page run into the release mode to like the following:

2. EnablePartialRendering Yes or No?
There is another property in ScriptManager named EnablePartialRendering, it gets or sets a value that enables partial rendering of a page, which in turn enables you to update regions of the page individually by using UpdatePanel controls.

So, if we using the UpdatePanel in the page, we must set this property to true, conversely, if the UpdatePanel is not using in our page, it would be better that we set the EnablePartialRendering to false.

That will cause the unnecessary file “MicrosoftAjaxWebForm.js”, which is used to the partial rendering not import to our page.

3. LoadScriptBeforeUI
ScriptManager control has LoadScriptsBeforeUI property which we can set to “False” in order to postpone several script downloads after the content is downloaded and shown. This adds the script references end of the tag. As a result, we will see the content first and then the additional scripts, exteders, AJAX Control Toolkit scripts get downloaded and initialized.

This will make the page show quikly, and provide a better User Experience.

Script Combining
In the previous talk, we can see the download size is coming down, but the number of requests is still more than 20

1. ToolkitScriptManager
There is a ToolkitScriptManager control in the AJAX Control Toolkit, we can replace the default control with this, it supports the ability to dynamically merge multiple client-side Javascript scripts into a single file that is downloaded to the client at runtime. Better yet, only the Javascript needed by the specific controls on the page are included within the combined download, to make it as small as possible.

As the screen shot shows, It is a big savings in requests – we now get one request for Toolkit scripts instead of 12. In this scenario, we also got about a 50% download speed improvement by only having one request.

2. CompositeScript
If you are using ASP.NET 3.5 with SP1, there is a more powerful tool to combining the Script file – CompositeScript.

First, We can use the ScriptReferenceProfiler to show the JavaScript references

and then, we can add and elements as children of the ScriptManager control.

Then, Copy the script references from the page and paste them into the element inside the ScriptManager control, the result mark up is following:

Run the page and view the traffic. We will see just one script reference now instead of all the script inside the element

Taken from:

http://lancezhang.wordpress.com/2008/11/15/aspnet-ajax-performance/

REST can be described as an architecture style. The acronym REST stands for ‘Representational State Transfer’, this means that every unique URI is representation of some object and you can get the content of this object using HTTP GET as well as you can use POST, PUT and DELETE to play with content of this object.

REST – An Architecture style, not a standard

This is really good to know that REST is not a standard as you will not see any W3C standards putting any REST specifications. The reason is that REST is simply an architecture style, you can’t pack a toolkit of this; instead you can use this style during writing your web services. Though REST is an architecture style but it use certain standards like:

· HTTP

· text/xml, text/html, etc (MIME types)

· URL
How to Call REST Web Service using SQL CLR

REST based web services are most of the time in form of URI, to consume these web services one has to write SQL CLR stored procedures. I have taken an example to make standard PUT and POST calls to REST based web services, this code can be used to practically make call to any REST web services that have PUT or POST payload. Below code snippet describes .NET code written to make CLR stored procedures

using System;

using System.Data;

using System.Data.SqlClient;

using System.Data.SqlTypes;

using Microsoft.SqlServer.Server;

using System.Net;

using System.IO;

public partial class StoredProcedures

{

[Microsoft.SqlServer.Server.SqlProcedure]

public static void SampleWSPut(SqlString weburl, out SqlString returnval)

{

string url = Convert.ToString(weburl);

string feedData=string.Empty;

try

{

HttpWebRequest request = null;

HttpWebResponse response = null;

Stream stream = null;

StreamReader streamReader = null;

request = (HttpWebRequest)WebRequest.Create(url);

request.Method = “PUT”; // you have to change to

//PUT/POST/GET/DELETE based on your scenerio…

request.ContentLength = 0;

response = (HttpWebResponse)request.GetResponse();

stream = response.GetResponseStream();

streamReader = new StreamReader(stream);

feedData = streamReader.ReadToEnd();

response.Close();

stream.Dispose();

streamReader.Dispose();

}

catch (Exception ex)

{

SqlContext.Pipe.Send(ex.Message.ToString());

}

returnval = feedData;

}

[Microsoft.SqlServer.Server.SqlProcedure]

public static void SampleWSPost(SqlString weburl, out SqlString returnval)

{

string url = Convert.ToString(weburl);

string feedData = string.Empty;

try

{

HttpWebRequest request = null;

HttpWebResponse response = null;

Stream stream = null;

StreamReader streamReader = null;

request = (HttpWebRequest)WebRequest.Create(url);

request.Method = “POST”;

response = (HttpWebResponse)request.GetResponse();

stream = response.GetResponseStream();

streamReader = new StreamReader(stream);

feedData = streamReader.ReadToEnd();

response.Close();

stream.Dispose();

streamReader.Dispose();

}

catch (Exception ex)

{

SqlContext.Pipe.Send(ex.Message.ToString());

}

returnval = feedData;

}

};

The above code depicts that we have used HttpWebRequest class object to create an URI based request, and later we have defined the type of method to make this URI calls, that is ‘PUT’ and ‘POST’. You can change this method based on your payload request.

When the above code will be compiled in assembly and later registered as an assembly in SQL Server, we’ll create two CLR stored procedures to bind assembly stored procedure methods with them.

Generate Assembly and Register in SQL Server

The code here guide you to create assembly of class and later register this assembly in SQL Server

¾ Generate Assembly

// Creates StoredProcedures.dll

csc /t:library StoredProcedures.cs

¾ Register Assembly in SQL Server

USE [SampleDB]

GO

CREATE ASSEMBLY SPAssembly

FROM ‘C:\SampleCLRSP\StoredProcedures.dll’

WITH PERMISSION_SET = UNSAFE;

GO

Create CLR Stored Procedure

I have put the T-SQL scripts here to create your CLR stored procedure to make call to any REST web service for PUT and POST payload

USE [SampleDB]

GO

/****** Object: StoredProcedure [dbo].[SampleWSPut] Script Date: 06/18/2008 06:02:32 ******/

CREATE PROCEDURE [dbo].[SampleWSPut]

@weburl [nvarchar](4000),

@returnval [nvarchar](2000) OUTPUT

WITH EXECUTE AS CALLER

AS

EXTERNAL NAME [SPAssembly].[StoredProcedures].[SampleWSPut]

GO

/****** Object: StoredProcedure [dbo].[SampleWSPost] Script Date: 06/18/2008 06:02:19 ******/

CREATE PROCEDURE [dbo].[SampleWSPost]

@weburl [nvarchar](4000),

@returnval [nvarchar](2000) OUTPUT

WITH EXECUTE AS CALLER

AS

EXTERNAL NAME [SPAssembly].[StoredProcedures].[SampleWSPost]

Calling CLR stored procedures

Below example shows that how can you make call to REST based web services using CLR stored procedures. CLR stored procedures written by us make call to REST web service and collect the response send by them, response could be a simple HTTP response message, for example 100, 200, 401 etc. or it could be full XML or MIME message returned to your application.

Declare @Response NVARCHAR(2000)

EXECUTE SampleWSPOST ‘http://sampledev03/wcfweb/calendarWS.svc/?appid=MMM&AuctionCode=ABC&months=4′,@Response OUT

SELECT @Response

GO

Declare @Response NVARCHAR(2000)

EXECUTE SampleWSPUT ‘http://sampledev03/wcfweb/calendarWS.svc/?appid=MMM&AuctionCode=ABC&months=4′,@Response OUT

SELECT @Response