I have a TimeClass_tbl which contains the following fields.
[ID] [Name] [FromTime] [ToTime] [Date(just date, not time)]

I have to write a procedure with input of datetime datatype which can return
the ID of the specific entry matching that parameter. If the 'Date' column
can be null and on matching the date of supplied variable, it should return
the ID of that particular entry, but incase if there are more than one
records returned on matching this date, then i have to check that which entry
conforms to the time duration of 'FromTime' and 'ToTime', just for getting
those number of records and manipulating each record without employing any
extra burden of variables and one after another query i am taking cursors
into account.
If you have any better solution to this problem, i'll be thankfull to you.
--

The best way to post your table structure is as a CREATE TABLE statement,
including keys and constraints. For the moment I'll assume that your table
looks like this:

CREATE TABLE TimeClass (id INTEGER NOT NULL, name VARCHAR(20) NOT NULL,
fromtime DATETIME NOT NULL, totime DATETIME NOT NULL, date DATETIME NULL /*
??? PRIMARY KEY NOT SPECIFIED */)

In this case the query you want could be:

SELECT id
FROM TimeClass
WHERE (@dt >= date AND @dt < DATEADD(DAY,1,date))
OR (@dt >= fromtime AND @dt < totime)

But possibly your problem is due to you storing dates and times separately
(I'm guessing that based on your column names). That's not a design I would
recommend but if you post the table structure and some sample data too then
maybe we can understand your requirements better.

This article explains what information to post to stand the best chance of
getting help with your problem:

http://www.aspfaq.com/etiquette.asp?id=5006

Hope this helps.

--
David Portas
SQL Server MVP

The best way to do it in Oracle may not be the best way in SQL Server.
Cursors in SQL Server are slow which is another good reason to avoid cursors
altogether where you can. If you give us some detail on your problem maybe
someone can suggest a set-based solution instead.

--
David Portas
SQL Server MVP
--