table1: In timings history
EMPID pk INTIME EFFECTIVE_DATE END_DATE
ENTERED_BY
tabl2 intiming
EMPID pk INTIME EFFECTIVE_DATE END_DATE enteredby
ta3
emptimings
ENTRYTIME pk EMPID TIMETYPE INOUT IP_ADDRESS
i want to calculate emp salary after deducting leaves and break timings
and other cuttingsddl means
CREATE TABLE TABLENAME ETC
SAMPLE DATA MEANS : insert into
--
Regards
R.D
--Knowledge gets doubled when shared
"raghu veer" wrote:
> table1: In timings history
> EMPID pk INTIME EFFECTIVE_DATE END_DATE
> ENTERED_BY
> tabl2 intiming
> EMPID pk INTIME EFFECTIVE_DATE END_DATE enteredby
> ta3
> emptimings
> ENTRYTIME pk EMPID TIMETYPE INOUT IP_ADDRESS
>
> i want to calculate emp salary after deducting leaves and break timings
> and other cuttings
>
>
Monday, March 19, 2012
details about finetuning queries
Labels:
database,
details,
effective_date,
end_date,
end_dateentered_bytabl2,
finetuning,
historyempid,
intime,
intimingempid,
microsoft,
mysql,
oracle,
queries,
server,
sql,
table1,
timings
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment