Often times in code you want to assign one variable to another, but only if the variable is not null. If it is null, you want to populate the target variable with another ( perhaps default ) value. The code normally may look like this using the C# Conditional Operator:

string fileName = tempFileName != null ? tempFileName : “Untitled”;

If tempFileName is not null, fileName = tempFileName, else fileName = “Untitled“.

This can now be abbreviated as follows using the Null-Coalescing Operator:

string fileName = tempFileName ?? “Untitled”;

The logic is the same. If tempFileName is not null, fileName = tempFileName, else fileName = “Untitled“.

The Null-Coalescing Operator comes up a lot with nullable types, particular when converting from a nullable type to its value type:

int? count = null;

int amount = count ?? default(int);

Since count is null, amount will now be the default value of an integer type ( zero ).

These Conditional and Null-Coalescing Operators aren’t the most self-describing operators , but I do love programming in C#!

Reference : http://source.witssquare.com

There are three ways to retrieve the current datetime in SQL SERVER.
CURRENT_TIMESTAMP, GETDATE(), {fn NOW()}

CURRENT_TIMESTAMP
CURRENT_TIMESTAMP is a nondeterministic function. Views and expressions that reference this column cannot be indexed. CURRENT_TIMESTAMP can be used to print the current date and time every time that the report is produced.

GETDATE()
GETDATE is a nondeterministic function. Views and expressions that reference this column cannot be indexed. GETDATE can be used to print the current date and time every time that the report is produced.

{fn Now()}
The {fn Now()} is an ODBC canonical function which can be used in T-SQL since the OLE DB provider for SQL Server supports them. {fn Now()} can be used to print the current date and time every time that the report is produced.

If you run following script in Query Analyzer. I will give you same results. If you see execution plan there is no performance difference. It is same for all the three select statement.
SELECT CURRENT_TIMESTAMP
GO
SELECT {fn NOW()}
GO
SELECT GETDATE()
GO

Performance:
There is absolutely no difference in using any of them. As they are absolutely same.

My Preference:
I like GETDATE(). Why? Why bother when they are same!!!

Convert Date Format for like this [dd-MMM-yyyy].

Select Substring(Convert(Varchar(10),getdate(),111), Len(Convert(Varchar(10),getdate(),111))-1,2) + ‘-’ +
Substring(Convert(Varchar(20),getdate(),0),1,3) + ‘-’ + Substring(Convert(Varchar(10),getdate(),111),1,4)As Date

1. As per functionality both GET and POST methods were same.Difference is GET method will be showing the information information to the users.But in the case of POST method information will not be shown to the user.

2. The data passed using the GET method would be visible to the user of the website in the browser address bar but when we pass the information using the POST method the data is not visible to the user directly.

3. Also in GET method characters were restricted only to 256 characters.But in the case of POST method characters were not restricted.
Get method will be visible to the user as it sended appended to the UML, put Post will not be visible as it is sent encapsulated within the HTTP request body.

4. About the data type that can be send, with Get method you can only use text as it sent as a string appended with the URL, but with post is can text or binary.

5. About form default, Get is the defualt method for any form, if you need to use the post method, you have to change the value of the attribute “method” to be Post.

Get method has maximum length restricted to 256 characters as it is sent appended with the URL, but the Post method hasn’t.

Reference : http://source.witssquare.com