Could Not Access IIS Metabase

Some times ASP.net applications hosted on iis could not load and start giving errors like
"Could not Access IIS Metabase" or "The process account used to run ASP.NET must have read access to the IIS metabase"
After spending a lot of time on it and trying a lot of things like
Installing aspnet user using aspnet_regiis -i
Reinstalling IIS
Reparing visual studio
Granting access to IUser and Aspnet user to root directory and the direcotry where these files were stored
etc ,
I finally got rid of this situation by
Adding Aspnet user to the Administrator pool of this machine and it worked for me
but it was not a good idea so i tried  with ASPNet User  like
aspnet_regiis -ga ASPNET 
and it worked for me .
hope this will work for you as well.

Optional Paramertes Queries in SQL

We often require to implemnet some search mechanism , in which we provide some input parameters and result set includes result based on those parameters
if we provide all parameters and use all of them in our select query then everything is good, but when we say use can provide some of them and others will not be a part of select statement , here we have some confusion
there are two approaches for this scenerio
No 1 is use IsNull Check
Say we have a parameter @Id and a column Id in table we can write query like
Select * from Employee
Where Id=IsNLL(@Id,Id)
So here if @id parameter is not provided and will contain null , no search criteria will be applied and all employees will be returned
this thing can be exteneded to multiple parameters as well like
Select * from Employee
Where Id=IsNLL(@Id,Id)
AND Name = ISNULL(@Name,Name)
Problem
this is good for all those table columns which does not contain NULl ,
but will fail on those column fields which can contain null values
so in order to avoid such mistakes we can use above queries by modifying a bit
No 2

Select * from Employee
Where ( @Id is null or Id=@Id) AND
(@Name is null or Name=@Name)