exile360

New Database numbering format

56 posts in this topic

Greetings all :)

We have changed our database numbering scheme so that it is compatible with new features in our upcoming 1.60 version of Malwarebytes Anti-Malware. This change also enhances our users' ability to be able to decipher when a database was created and released. The number '9' at the beginning of the database version is there for compatibility (since our previous naming scheme reached over 8000, thus the '9' at the beginning tells the product that any database that starts with this new naming scheme is newer than the one that is installed).

Below is an example:

911122006

Here's how these numbers break down:

  • As stated above, the number 9 tells older versions of Malwarebytes Anti-Maware that used the old database naming scheme that this database is newer than any of the previous 8xxx database versions
  • The 11 that follows the 9 represents the year
  • The 12 that follows the 11 represents the month
  • The 20 that follows the 12 represents the day
  • The 06 that follows the 20 represents the number of the database released on that particular day, so in this case, the database 911122006 is the 6th database released on December 20th, 2011

For our upcoming release, Malwarebytes Anti-Malware 1.60, the database version will appear as below:

v2011.12.20.06

Here's how this database format breaks down:

  • v represents version
  • 2011 represents the year
  • 12 represents the month
  • 20 represents the day
  • 06 represents the number of the database released on that particular day, so as above, v2011.12.20.06 would be the 6th database released on December 20th, 2011

Using this new naming scheme, a user or support helper can easily determine if the database used is fairly current or badly outdated.

Share this post


Link to post

Neato, thanks for the information :)

Share this post


Link to post

Sweet ;) nice update. trying out now the 1.60 beta on Windows 7 PRO SP1 x64...

Share this post


Link to post

Was wondering why the database naming changed. I thought the database file was hijacked or something. :P

Share this post


Link to post

Always looking good!

TH

Share this post


Link to post

I think it should be yyyy instead of yy for clarity sake.

Share this post


Link to post

Nice work guys :)

Share this post


Link to post

Was wondering why the database naming changed. I thought the database file was hijacked or something. :P

Me too. Too early in the morning for this stuff :-(

Share this post


Link to post

I think it should be yyyy instead of yy for clarity sake.

We couldn't for backwards compatibility reasons.

Share this post


Link to post

We couldn't for backwards compatibility reasons.

Perhaps for v2.0 then? :)

Share this post


Link to post

What is the correct database version I cant seem to get mine to update?

Share this post


Link to post

What is the correct database version I cant seem to get mine to update?

Date: 20/12/2011 21:52:33

Database version: v2011.12.20.06

Fingerprints loaded: 350980

Share this post


Link to post

ok I uninstalled and reinstalled after using mbam-clean seems up to date now.

Share this post


Link to post

"Using this new naming scheme, a user or support helper can easily determine if the database used is fairly current or badly outdated."

Why not just use the date, directly above the update version? Or is that also going away?

I've no problem with the new version designation at all. When it changed I imagined a new MBAM was on the way.

Will MBAM now automatically work with our Anti-Virus programs, or do we integrate them in the same old way, so that they ignore one another?

Share this post


Link to post

Thanks and looking forward beyond the new Beta release.

Some in this thread are hotlinking to announcement posts elsewhere <_<

This does not allow the reader the benefit of the full thread.

Those at MBAM that have my Twitter have been notified.

Regards,

Share this post


Link to post

Perhaps for v2.0 then? :)

YYYY is the format for 1.60 already (in beta now) :)

Share this post


Link to post

"Using this new naming scheme, a user or support helper can easily determine if the database used is fairly current or badly outdated."

Why not just use the date, directly above the update version? Or is that also going away?

We will use the date in the UI still, this naming scheme gets more specific though. It tells you which number of database it is on a particular day, something the date info does not tell you.

Will MBAM now automatically work with our Anti-Virus programs, or do we integrate them in the same old way, so that they ignore one another?

Unfortunately no, exclusions are still often required (and a good idea anyway). We don't develop those other companies' products, so there's not much we can do to make them work better alongside our product.

Share this post


Link to post

Well, that puts an end to my "fun with MBAM Pro updates" tracking. :P Tho the dated format is a really good and welcome move.

My initial install of v1.44 on January 30, 2010 started with database 3458. And the last one I noticed was yesterday's 8406. That calculates out to a most excellent average of seven updates a day - a rate unmatched by almost everyone else in the industry.

Looking forward to v1.6.

Good luck and best wishes to the Malwarebytes crew in 2012 and beyond!

Share this post


Link to post

I am not running the beta, so got a shock when I did my defs update this morning... but my mind is at peace when I found this thread that explains it all. :)

Share this post


Link to post

Hey guys.

I am in Venezuela. South America, more or less USA Eastern time zone, and I have noticed that with this new database numbering format I get tomorrow updates, 911122201, today, late in the afternoon . I thought MBAM was in California, USA almost 4 hours earlier than me. Unless MBAM has servers in Europe and I am getting the updates from there it does not make any sence.

Any thoughts.

Share this post


Link to post

Hey guys.

I am in Venezuela. South America, more or less USA Eastern time zone, and I have noticed that with this new database numbering format I get tomorrow updates, 911122201, today, late in the afternoon . I thought MBAM was in California, USA almost 4 hours earlier than me. Unless MBAM has servers in Europe and I am getting the updates from there it does not make any sence.

Any thoughts.

Yes, our home office is in San Jose, California. We're using the GMT for the database release date so that it is universal.

Share this post


Link to post
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.