|
![](/i/fill.gif) |
"Darren New" <dne### [at] san rr com> wrote in message
news:4ae9ea6b$1@news.povray.org...
> Captain Jack wrote:
>> There weren't any queries against the column, and it wasn't even used in
>> any JOIN's. I s'pose it made sense to somebody, somewhere...
>
> Makes me wonder why you even had the column, let alone the index.
I never did figure it out for sure, but the column was named "rowguid", so
I'm guessing that whoever created it thought it was required for
replicating, or something. Replication had never been set up for the
database, though, so that's about the end of my guesses.
Once I got the front end application cleaned up, it (and a bunch of other
crappy design problems) went off to visit Atlantis wearing lead coated
uranium swim fins.
Funny, the performance of writing new records improved after I got rid of
that column...
>
> I once managed a database with no autoincrement columns at all. :-) All
> the primary keys came from the people using the database from outside the
> company.
I've always felt that if we could get rid of clients, vendors, and the need
for a budget, programming would be a really fun occupation. :D
Post a reply to this message
|
![](/i/fill.gif) |