June 4, 2008 at 3:09 pm
mailsar (6/4/2008)
Hi noel,I appreciate your suggestion.What do you mean by publication management issues?
Thanks,
Kayal
Depending how you configure your publication you can come across several "unexpected" things like system stored procedures that are called which you were not expecting; failover procedures are also dependend on some publication settings and if on top of that you have to do this kind of stuff accross many DB and many Servers; simplicity becomes "important".
* Noel
June 6, 2008 at 2:17 pm
If you made up your mind that's good because you are the one that will have to live with it. There are times when an identity column works and times when your own sequential column works better. If you are not worried about gaps then identity works well but some clients do't like gaps in their sequential numbers then you have to do your own thing.
:-PManie Verster
Developer
Johannesburg
South Africa
I can do all things through Christ who strengthens me. - Holy Bible
I am a man of fixed and unbending principles, the first of which is to be flexible at all times. - Everett Mckinley Dirkson (Well, I am trying. - Manie Verster)
June 8, 2008 at 7:07 pm
I have a really simple question for my half a braincell which has never been exposed to replication.
Can anyone explain why the gaps appear in identity columns. I really dont care, but just really curious what leads to the gaps (without the obvious being the delete statement being issued)
~PD
June 8, 2008 at 7:25 pm
Yes... it's so the system doesn't have to wait until your insert is done before anyone else can do an insert. If your insert fails (or you change your mind) and is rolled back, gaps occur because the ID's had already been reserved.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2008 at 7:31 pm
Ahhhhhh that makes sense and explains quite a lot.
Thanks
~PD
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply