>> I have an identity field [sic] on a table in SQL Server ... If I
remove a record [sic] from this table, the identity sequence is
broken. <<

Your problem is that you still think in terms of files, records, and
fields and do not understand an RDBMS model of the world. A real SQL
programmer does not use IDENTITY for a host of reasons. What you are
doing in SQL is mimicking a sequence magnetic tape file, circa 1950.

Get a book and learn the basics before you write any more code.

You know Joe, I've had it with your crap. I'm learning SQL myself, and for
the most part I try to use real world solutions and try to stick to the
model as close as possible (I even wrote my first UDF today, thanks to the
BOL and some helpful people on the web). A lot of other people in this
list are learning as well. If you want to contribute something useful, then
by all means do so, otherwise SHUT THE FUCK UP!. I don't believe you were
born with the God like knowledge of SQL you would have us believe you
possess. You had to go through the same learning curve as the rest of us.

I used to respect you, in that the articles you have written have proved
helpful to me in the past. From now on, I plan on avoiding you like the
plague.

Kevin


"--CELKO--" <jcelko212@earthlink.net> wrote in message
news:18c7b3c2.0409011450.10fd20fd@posting.google.c om...
> >> I have an identity field [sic] on a table in SQL Server ... If I
> remove a record [sic] from this table, the identity sequence is
> broken. <<
>
> Your problem is that you still think in terms of files, records, and
> fields and do not understand an RDBMS model of the world. A real SQL
> programmer does not use IDENTITY for a host of reasons. What you are
> doing in SQL is mimicking a sequence magnetic tape file, circa 1950.
>
> Get a book and learn the basics before you write any more code.
>

>> If you want to contribute something useful, then
by all means do so, otherwise SHUT THE FUCK UP!.<<

I did, but you don't know it yet.

>> I don't believe you were born with the God like knowledge of SQL you
would have us believe you possess. <<

Just believe that I have the books and articles that you can Google.

>> You had to go through the same learning curve as the rest of us. <<

NO, I had to go thru **much worse** learning curves. There were no SQL
books when I started and the relational model was brand new and
misunderstood. Why do you think I had to write some?

Kevin, do not learn by climbing that same learning curve; start by
standing on the shoulders of those who went before you. Pick up good
progtamming habits now instead of writing bad code for 5 or 10 years as
some of kind weird learning experience.

In particular, you are confusing the parking space with the VIN number
when you want to track automobiles. Google some of my rants on IDENTITY
and mimicking sequential files in SQL.

--CELKO--
===========================
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
schema are.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!