Well this trigger is just plain wrong if multiple rows can be affected in one shot!

The Trigger can probably be written in just two statements 1 update and one insert!...

Well, let's hope that his shop is not 24/7 and even if it is not depending on the data 12 hours can be devastating for certain companies

>>The database is set up with 'truncate transaction log with checkpoint' option.So may be thats why we dont have earlier transaction logs.<<

Well, you have learned the hard way that Production DB...

Glad to help!

looks like in the end you are listening and hope fully do this client side.

The three loops I was mentioning were:

1. for the number of roots

2.for the spacing of them

3.for...

just Wrap the query in a select statement SQL is smart enough!

select X

from

( THE QUERY) derived

I may depending on how much weight the order by have in the Total Query cost: ie.: if the order by operates in small resultant set it may be not a...

I think that where you need to sharpen the pencil is on the optimizations job. You could make it scripted so that you pick an choose what needs to be...

Ok, I am on it!

I am assuming your database is in Full reovery mode, Right?

and that you have all TRN logs backups since last Full DB Backup right?

no matter what you do Backup the...

select Id

from Employee

where  Right(convert(char(6),DOB,12) ,4) between '0201' and '0515'

With Brute force, it will all depend on how soon you find the match

Think of it as a Dictionary Attack,  sometimes they...

Like I said before, Don't try to reinvent the wheel!

Find your self a book of polynomial root detection and you will save plenty of time!!!

but if you plan to...

When you run the 1st Case  you actually CLOSED the connection before the second EXEC.

In the 2nd instance ALL SQL is executed as mentioned above within the SAME SCOPE!

hth

well for a fixed number of values you may try to implement Ruffinis' method for polinomial root detection. I have to brush up my math!