Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
uberman
Posting Yak Master
159 Posts |
 Posted - 2006-05-15 : 05:10:55
|
| We have a system that could have one of 12 (currently) patches appliedMost customers have patches 1-6, 12Some customers have patches 1-6, 10-12One customer has patches 1-6, 7, 8, 12One customer has patches 1-6, 9-12We cant just say .12 for all customers 'cos althougth they all do have patch 12 it doesnt mean they have patches 1 - 12!Basically we are trying to work out if there is an "at a glance" or at least an "at a longer glance with quick transform" way of numbering/versioning what is released to our customers so we can easily work out what combination of patches have been appliedWith a relatively small set of customers and a short time span we kinda hold this information in our heads, but with dev, testing and upgrade systems also having patch combination it is getting a bit trickySo, how would you do patch versioning given this situation (we thought of binary numbers, but as we got to patch 12 the numbers started to look worringly big!) |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-05-15 : 05:15:34
|
| You could do it with a bit mask (suspect that's what you mean by a binary number) or just add a table or text file or whatever at the client (or in your control system) which has a row for each patch installed.You could also use this for patch installation - check the patch history to see what's been installed and whether the patch they are trying to install is ok or needs something else first.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Patch Versioning : How do you do yours?