Strange behaviour of parameter Toad for SQL Server 6.6.0.963

Toady I see a strange beahviour.

I connect to a DB, I select aDB and press right click of mouse over it. At this point I select - view details - and i see a lot of parameters.

Under backup- there is a value - Last Full Backup -. In my case for all DB's present on my server tha value is equal to 8 May 2016 at 8 :24 am.

See my screenshot in attach for detail :

What do you mean - Last Full Backup ?

Is this the last time I have done a valid full backup of my DB ?

Today at 8:24 am I don't any backup's of my DB. I backup only a DB, with another name but not all DB's present on my server.

If I open same parameters on last Toad for SQL Server Beta 6.7.0.172 I obtain the same information.

Can someone clarify the situation ?

I use Microsft SQL Server 2012 Developer edition with service pack 3 in italian Language and my notebook use Microsoft Windows 7 professional with service pack 1 plus last Windows update from the Microsoft's web site.

Best regards,

Sergio

Hi Sergio,

Thank you for your posting.

Yes, the time is the last time valid full backup of the DB.

And I try to do a full backup, the other DB backup time properties are affected.

Are there any Auto job to run the backup in your server?

Regards,

Kelly

Hi Kelly,

many thank's for your help.

Are there any Auto job to run the backup in your server?

No.

Best regards,

Sergio

Hi Sergio,

I try to use SQL Server Management Studio to connect my server. And see the backup datetime is same with ToadSS. Would you like try this also?

Is there possible your Server time is not the same with your local time?

Best Regards,

Kelly

Hi Kelly,

I confirm that SSMS show me the same value of TOADSS.

I try another server, SQL Server 2014 Advanced Express Edition with service pack 1 and all is correct.

Every DB show the correct date and time for everyone DB.

Is there possible your Server time is not the same with your local time?

I think no, because my server is my notebook, and TOAD SS is installed on it...

At this point i think that the problem is of SQL Server 2012.

What's do you think of ths my consideration ?

Best regards,

Sergio