Sorry for posting that image....

... or is it what's under the kilt that may scare people?:-D

Edited: removed photo

We're using Tivoli Data Protection for SQL Server and it doesn't look that different from the one that you are describing.

We're happy with it, no issues at all.

Alvin Ramard (11/3/2009)

---

Gianluca Sartori (11/3/2009)

---

If my calculations are correct this is post # 9000.

I set 7 posts per page, took the page number, multiplied for PI and divided it by...

If my calculations are correct this is post # 9000.

I set 7 posts per page, took the page number, multiplied for PI and divided it by the distance between Earth...

Maybe it's the same math that states that if I eat an egg and you don't eat at all, each of us had half egg.:-)

Yes, you're right.

This demontrates that you can use any number of posts per page and you'll get the wrong results if your mind is turned OFF.:blush:

....ooops! It's 8924 bottles!

I was using 50 posts per page...

8993 bottles of beer on the wall...

... or kill the...

OK, I need table(s) definition sample data and desired output.

Can you post it? See this article for more information:

http://www.sqlservercentral.com/articles/Best+Practices/61537/

And with ROW_NUMBER

;WITH CTE (N, c1, c2) AS (

SELECT ROW_NUMBER() OVER (ORDER BY c1), c1, c2

...

You can solve it even without ROW_NUMBER().

DECLARE @Table TABLE (

c1 datetime,

c2 int

)

INSERT INTO...

That's because in the other tables you are joining you have the same loan multiple times.

If you don't need the columns in the joined tables, you can use a WHERE...

SELECT DISTINCT LoanId