Jquery Bubbling and capturing

http://javascript.info/tutorial/bubbling-and-capturing

Jquery add href to a tag

 $('#workFlowlink1').attr('href', '#');
 $('#workFlowlink2').attr('href', '#');

$('#workFlowlink1').attr('href', '../Webpages/Workflow.aspx');
$('#workFlowlink2').attr('href', '../Webpages/Workflow.aspx');

C# Difference between ref and out parameters

http://www.dotnet-tricks.com/Tutorial/csharp/K0Hb060414-Difference-between-ref-and-out-parameters.html

SQL nested case when then

 CASE
WHEN alertcon.alert_type = 'E'
THEN
CASE
    WHEN alertgat.gateway_id = 'M' THEN escUser.login_id
    WHEN alertgat.gateway_id = 'E' THEN escUser.email_id
    ELSE ''
END
WHEN alertcon.alert_type = 'R'
THEN
CASE
   WHEN alertgat.gateway_id = 'M' THEN escUser.login_id
   WHEN alertgat.gateway_id = 'E' THEN escUser.email_id
    ELSE ''
END
END as Recepient

How to insert values to identity column in SQL Server

http://www.dotnet-tricks.com/Tutorial/sqlserver/4UXH230213-How-to-insert-values-to-identity-column-in-SQL-Server.html

Static Cursors

A static cursor populates the result set at the time of cursor creation and query result is cached for the lifetime of the cursor. A static cursor can move forward and backward direction. A static cursor is slower and use more memory in comparison to other cursor. Hence you should use it only if scrolling is required and other types of cursors are not suitable.

No UPDATE, INSERT, or DELETE operations are reflected in a static cursor (unless the cursor is closed and reopened). By default static cursors are scrollable. SQL Server static cursors are always read-only.

1. SET NOCOUNT ON
2. DECLARE @Id int
3. DECLARE @name varchar(50)
4. DECLARE @salary int
5. DECLARE cur_emp CURSOR
6. STATIC FOR
7. SELECT EmpID,EmpName,Salary from Employee
8. OPEN cur_emp
9. IF @@CURSOR_ROWS > 0
10. BEGIN
11. FETCH NEXT FROM cur_emp INTO @Id,@name,@salary
12. WHILE @@Fetch_status = 0
13. BEGIN
14. PRINT 'ID : '+ convert(varchar(20),@Id)+', Name : '+@name+ ', Salary : '+convert(varchar(20),@salary)
15. FETCH NEXT FROM cur_emp INTO @Id,@name,@salary
16. END
17. END
18. CLOSE cur_emp
19. DEALLOCATE cur_emp
20. SET NOCOUNT OFF

The ‘NULL’ Debate, and a few other interesting facts

http://blogs.msdn.com/b/sqljourney/archive/2012/04/18/the-null-debate-and-a-few-other-interesting-facts.aspx?CommentPosted=true#commentmessage