"Brandon" <bsmith@presentationsdirect.nospam.com> wrote in message
news:uEV6tRHYFHA.3096@TK2MSFTNGP15.phx.gbl...
> Our SQL database show that they haven't been modified or accessed in weeks
> . . . and yet our users are working with applications that access these
> databases on a daily basis. So why would the dates on the database files
> themselves show that it's been weeks since they've been used?
>
> --
> Brandon Smith
> IT Director
> Presentations Direct - Specialized Office Equipment & Supplies
> http://www.presentationsdirect.com
>
>

"Keith Kratochvil" <sqlguy.back2u@comcast.net> wrote in message
news:%23OhHnjHYFHA.3184@TK2MSFTNGP15.phx.gbl...
>I assume that you are talking about the date on the database data and log
>file(s). It is normal that the dates do not change. The dates will not
>change until the file is closed. The file will only be closed when you
>stop SQL Server (or the db is set to autoclose which is generally not
>recommended).
>
>
> It sounds like you may have limited knowledge of and experience with SQL
> Server. I want to take a minute to recommend that you backup your
> databases to disk. You should then backup your backups to tape (or copy
> the files to another computer/server). You can create and schedule jobs
> within SQL Server Enterprise Manager that will back up your databases.
> The following KB article might be helpful:
>
> INF: Disaster Recovery Articles for Microsoft SQL Server
> http://www.support.microsoft.com/?id=307775
>
>
> --
> Keith
>
>
> "Brandon" <bsmith@presentationsdirect.nospam.com> wrote in message
> news:uEV6tRHYFHA.3096@TK2MSFTNGP15.phx.gbl...
>> Our SQL database show that they haven't been modified or accessed in
>> weeks . . . and yet our users are working with applications that access
>> these databases on a daily basis. So why would the dates on the database
>> files themselves show that it's been weeks since they've been used?
>>
>> --
>> Brandon Smith
>> IT Director
>> Presentations Direct - Specialized Office Equipment & Supplies
>> http://www.presentationsdirect.com
>>
>>
>
>

"Brandon" <bsmith@presentationsdirect.nospam.com> wrote in message
news:equ22%23IYFHA.2348@TK2MSFTNGP14.phx.gbl...
> Thanks, but what does backing up the db's have to do with my question? We
> already back up the db's with a full backup every night and a backup of
> the transaction logs every few hours.
>
> --
> Brandon Smith
> IT Director
> Presentations Direct - Specialized Office Equipment & Supplies
> http://www.presentationsdirect.com
>
>
> "Keith Kratochvil" <sqlguy.back2u@comcast.net> wrote in message
> news:%23OhHnjHYFHA.3184@TK2MSFTNGP15.phx.gbl...
>>I assume that you are talking about the date on the database data and log
>>file(s). It is normal that the dates do not change. The dates will not
>>change until the file is closed. The file will only be closed when you
>>stop SQL Server (or the db is set to autoclose which is generally not
>>recommended).
>>
>>
>> It sounds like you may have limited knowledge of and experience with SQL
>> Server. I want to take a minute to recommend that you backup your
>> databases to disk. You should then backup your backups to tape (or copy
>> the files to another computer/server). You can create and schedule jobs
>> within SQL Server Enterprise Manager that will back up your databases.
>> The following KB article might be helpful:
>>
>> INF: Disaster Recovery Articles for Microsoft SQL Server
>> http://www.support.microsoft.com/?id=307775
>>
>>
>> --
>> Keith
>>
>>
>> "Brandon" <bsmith@presentationsdirect.nospam.com> wrote in message
>> news:uEV6tRHYFHA.3096@TK2MSFTNGP15.phx.gbl...
>>> Our SQL database show that they haven't been modified or accessed in
>>> weeks . . . and yet our users are working with applications that access
>>> these databases on a daily basis. So why would the dates on the
>>> database files themselves show that it's been weeks since they've been
>>> used?
>>>
>>> --
>>> Brandon Smith
>>> IT Director
>>> Presentations Direct - Specialized Office Equipment & Supplies
>>> http://www.presentationsdirect.com
>>>
>>>
>>
>>
>
>