Author Topic: DB Time: NOT OK using MSSQL  (Read 7013 times)

Offline djamell

  • Jr. Member
  • **
  • Posts: 17
DB Time: NOT OK using MSSQL
« Reply #15 on: June 13, 2009, 11:35:12 AM »
Bump, please.

Offline roundstiv

  • Newbie
  • *
  • Posts: 1
also having issues
« Reply #16 on: September 15, 2009, 03:29:32 PM »
but mine are a bit different.
the result from the DB now check is not a result set but just the integer '4' and the value of mysql_error() is empty. which then produces a value for $tz_db of 0 (zero)

When I connect to the dB and run 'select unix_timestamp(now())' I get a value that matches almost.
compare
125304272
1253042731
 Does that seem odd?

MySQL 5.0.84
PHP 5.3.0

daspeac

  • Guest
DB Time: NOT OK using MSSQL
« Reply #17 on: November 17, 2009, 12:08:20 PM »
Hi folks, as you see, in some cases the root cause of database corruption is not known, therefore even experienced database administrators encounter problems. You may try the repair sql 2005 bkp file application and eliminate database errors, even if you do not know why it happened, it works automatically