crdate in sysdatabase is not getting changed

[Database Administrator]

Hii,

We used to load a database on daily basis. But, crdate of
that database is not getting changed with current date.
What might be the issue and How to resolve it???

[Database Administrator]

master.dbo.sysdatabases.crdate is the datetime when the database was created
with the first "create database" statement. There is a difference between
that and when a database was last loaded from a dump (which requires that
the database be created first). Did you expect that "crdate" be the date of
the last "load database" event? If this was so in a previous version, I
would have argued that was a bug.

wrote in message
news:48adb4f2.10b3.1681692777@sybase.com...
> Hii,
>
> We used to load a database on daily basis. But, crdate of
> that database is not getting changed with current date.
> What might be the issue and How to resolve it???

[Database Administrator]

Yes, I am expecting that
> "crdate" be the date of the last "load database".

> master.dbo.sysdatabases.crdate is the datetime when the
> database was created with the first "create database"
> statement. There is a difference between that and when a
> database was last loaded from a dump (which requires that
> the database be created first). Did you expect that
> "crdate" be the date of the last "load database" event?
> If this was so in a previous version, I would have argued
> that was a bug.
>
> wrote in message
> news:48adb4f2.10b3.1681692777@sybase.com...
> > Hii,
> >
> > We used to load a database on daily basis. But, crdate
> > of that database is not getting changed with current
> > date. What might be the issue and How to resolve it???
>
>

[Database Administrator]

On Aug 21, 11:33*pm, Rajasekhar Reddy wrote:
> Hii,
>
> * *We used to load a database on daily basis. But, crdate of
> that database is not getting changed with current date.
> * *What might be the issue and How to resolve it???

Are looking at crdate for tempdb and expecting crdate to be updated
while loading any other database ?. This will not be the case because
tempdb is recreated with every reboot of the server and therefore you
will see crdate updated for tempdb

-HTH
Manish Negandhi
[TeamSybase]

[Database Administrator]

"Sherlock, Kevin" wrote in message
news:48ade8bc$1@forums-1-dub...
> master.dbo.sysdatabases.crdate is the datetime when the database was
> created with the first "create database" statement. There is a difference
> between that and when a database was last loaded from a dump (which
> requires that the database be created first). Did you expect that
> "crdate" be the date of the last "load database" event? If this was so in
> a previous version, I would have argued that was a bug.
>
> wrote in message
> news:48adb4f2.10b3.1681692777@sybase.com...
>> Hii,
>>
>> We used to load a database on daily basis. But, crdate of
>> that database is not getting changed with current date.
>> What might be the issue and How to resolve it???
>
>
I mentioned that it would be nice to have an additional last_load_date
column for sysdatabases in ISUG ER 2298. Sybase might be open to
considering this specific request (versus create dates on almost every
system table). An alternative is to audit load database commands. Adequate
but certainly not as convenient.

[Database Administrator]

Not tempdb, any user database....


> On Aug 21, 11:33*pm, Rajasekhar Reddy wrote:
> > Hii,
> >
> > * *We used to load a database on daily basis. But,
> > crdate of that database is not getting changed with
> > current date. * *What might be the issue and How to
> resolve it???
>
> Are looking at crdate for tempdb and expecting crdate to
> be updated while loading any other database ?. This will
> not be the case because tempdb is recreated with every
> reboot of the server and therefore you will see crdate
> updated for tempdb
>
> -HTH
> Manish Negandhi
> [TeamSybase]

[Database Administrator]

"Carl Kayser" wrote in message
news:48ae9168$1@forums-1-dub...
>
> "Sherlock, Kevin" wrote in message
> news:48ade8bc$1@forums-1-dub...
>> master.dbo.sysdatabases.crdate is the datetime when the database was
>> created with the first "create database" statement. There is a
>> difference between that and when a database was last loaded from a dump
>> (which requires that the database be created first). Did you expect that
>> "crdate" be the date of the last "load database" event? If this was so
>> in a previous version, I would have argued that was a bug.
>>
>> wrote in message
>> news:48adb4f2.10b3.1681692777@sybase.com...
>>> Hii,
>>>
>>> We used to load a database on daily basis. But, crdate of
>>> that database is not getting changed with current date.
>>> What might be the issue and How to resolve it???
>>
>>
> I mentioned that it would be nice to have an additional last_load_date
> column for sysdatabases in ISUG ER 2298. Sybase might be open to
> considering this specific request (versus create dates on almost every
> system table). An alternative is to audit load database commands.
> Adequate but certainly not as convenient.
>
I was about to put in an ISUG ER for this but it has ocurred to me that this
column would not be adequate in itself. It seems to me that both a
last_load_db_date and a last_load_tr_date would really be needed. I'm not
sure that it is worth it.

(Some complications. The last_load_db_date should be the begin date/time of
the load since the load could fail. For the other ... hmmm, one could be
doing a recovery to a point in time. I don't know what would be the best
representation of this column.)

[batthink]

Just had a similar problem.

Using master you can get last load date doing this:

select dumptrdate from sysdatabases where name = 'mydb'

Assuming no dumps have taken place.