And I've seen many where the developers thought it worked like a charm until suddenly there were duplicate key errors.

If you insist on maintaining the sequence yourself you've got...

Why overwrite at all? Each log backup to an individual file, each full backup to an individual file. Then there's no chance of overwriting the wrong file, they can...

Dugi (1/12/2010)

---

I said before that large and medium DBs have tables that the Identity Col has generated value with combination, and the last value can be sequence number that generated...

I stand by what I said earlier. What happens if shortly after the full backup you find that a table something has messed up data and you need to restore...

I have never posted such a link because, as far as I know, there's no legal downloadable eBook of any of the Inside SQL Server series. Go and buy the...

I would rather suggest one file per backup. That way you don't overwrite every day. Problem with your design is, say 20 minutes after you did the backup with init,...

Have you looked up that traceflag (search engine of your choice)? Have you examined info given regarding when...

Dugi (1/12/2010)

---

I said, because meant if you start form 1 till 2 000 000 000 will take long time (maybe 1 year on large companies like banks and telephony), I...

First things first, that trigger will not work correctly when more than one row is inserted into the table. You're selecting values from the inserted table into variables, what's going...

Why do you say that? There's no inherent restriction that stops tables from having 2 billion rows. It's easily possible on larger...

That's not a limitation of identity. That's a limitation of the data type you used on that column. As I said, identity is not a data type. The data type...

What do you mean by 'limit'?

Identity is not a data type, it's just a property of a numeric column. You can set identity on an int column for a max...

Can you be more specific? Sample for what regarding locking?

All SQL queries take locks without you having to do anything. In the default isolation level shared locks are released as...

No way to ensure that in SQL 2000/2005. Just make sure the backups are secured so that unauthorised people can't get at them.

The post was in the SQl 2008 forum,...

If it's...