Working on one of my project on asp.net and Sql Server has made me learn a lot about both of these technologies. I’ll be sharing my learning and the tricky things which I have learnt here in the form of quick tips.
Here’s the first one. Keep an sharp eye when using NULL in where clause because things wouldn’t be working correctly without you even noticing. Following are the few things which new developers tends to do wrong. And they would’t notice because Sql Server wouldn’t raise any error for these.
- Checking for NULL values
- Checking for NULL in “IN” condition
Many times there comes a situation when we have to add a conditional where part in stored procedure’s query based on the parameters that are been passed to the SP. Let’s take up an example with the following requirement.
We’ll create a SP “FindProduct” which will have two parameters @id and @searchString and it will return the posts that meet the passed parameters. We want to create our procedure as such that it search for the product if one of these parameter is passed.
“Hello World!”. That Looks familiar isn’t it? We mad guys “The Coders” used to start learning every new thing with this. So Here I am getting a chance again to write “hello world”.
Hi Guys, I am Ankit, a Web Developer and Team Leader. I am starting out this blog hoping to learn from you guys so be right there.. A lot of interesting stuff to follow I guess.