.mdf & .ldf Data stamp doesn't change

We just moved from an old SQL 7 server to a new SQL 2000
server (detatch & attach method)
Since the move, the .mdf & .ldf file data stamps don't
change unless I reboot or stop the SQL services. Data
appears to be correct.
FYI - this is the second instance of SQL on this box, 1st
instance doesn't seem to have this problem.
I am getting some performance monitor messages indicating
excessive paging still working on that.
This on a new HP dl380 with 1.5 GB of RAM and a HP MSA
1000 SAN which was configured with ample of memory for the
DB & Application.
Any ideas would be appreciated
Thanks
LizHello Liz,
Thank you for your posting! From your post I understand that the .mdf &
.ldf file data stamps don't change unless you reboot or stop the SQL
services.
Based on my research, this behavior is as desinged. The .mdf & .ldf files
are opened by SQL server service to read/write data. "last modified date"
is updated only when physical file structure is updated. Another scenario -
exception - is that when SQL server service restarts "last modified date"
is reset. This means when "last modified date" for an mdf occurred when
SQL Data Engine grow/reduce file size. In the case for log file ldf, "last
modified date" is changed when VLF (Virtual Log File) is added/reduced.
We are not able to use "last modified date" to determine if data of a
database is modified. we conclude that during numerous data update, it
could be a performance hit if "last modified date" is updated every time.
We Recommend using tool such as SQL Profiler trace to validate if
transaction that modified records is completed.
If you have further questions on the issue, please feel free to let me
know.
Thanks & Regards,
Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| Content-Class: urn:content-classes:message
| From: "Liz Groom" <liz.groom@.mcafeetaft.com>
| Sender: "Liz Groom" <liz.groom@.mcafeetaft.com>
| Subject: .mdf & .ldf Data stamp doesn't change
| Date: Mon, 21 Jul 2003 15:34:59 -0700
| Lines: 21
| Message-ID: <048401c34fd8$518e0ce0$a401280a@.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNP2FGOZoCsY1CuQcqmkgv+iZSkkw==| Newsgroups: microsoft.public.sqlserver.server
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:297048
| NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| We just moved from an old SQL 7 server to a new SQL 2000
| server (detatch & attach method)
|
| Since the move, the .mdf & .ldf file data stamps don't
| change unless I reboot or stop the SQL services. Data
| appears to be correct.
|
| FYI - this is the second instance of SQL on this box, 1st
| instance doesn't seem to have this problem.
| I am getting some performance monitor messages indicating
| excessive paging still working on that.
|
| This on a new HP dl380 with 1.5 GB of RAM and a HP MSA
| 1000 SAN which was configured with ample of memory for the
| DB & Application.
|
|
| Any ideas would be appreciated
|
| Thanks
| Liz
||||Thanks Peter! Glad to know that it's not a problem --
Nothing like being a little paranoid! :)
Liz
>--Original Message--
>Hello Liz,
>Thank you for your posting! From your post I understand
that the .mdf &
>.ldf file data stamps don't change unless you reboot or
stop the SQL
>services.
>Based on my research, this behavior is as desinged.
The .mdf & .ldf files
>are opened by SQL server service to read/write
data. "last modified date"
>is updated only when physical file structure is updated.
Another scenario -
>exception - is that when SQL server service
restarts "last modified date"
>is reset. This means when "last modified date" for an
mdf occurred when
>SQL Data Engine grow/reduce file size. In the case for
log file ldf, "last
>modified date" is changed when VLF (Virtual Log File) is
added/reduced.
>We are not able to use "last modified date" to determine
if data of a
>database is modified. we conclude that during numerous
data update, it
>could be a performance hit if "last modified date" is
updated every time.
>We Recommend using tool such as SQL Profiler trace to
validate if
>transaction that modified records is completed.
>If you have further questions on the issue, please feel
free to let me
>know.
>Thanks & Regards,
>Peter Yang
>MCSE2000, MCSA, MCDBA
>Microsoft Partner Online Support
>Get Secure! - www.microsoft.com/security
>=====================================================>When responding to posts, please "Reply to Group" via
>your newsreader so that others may learn and benefit
>from your issue.
>=====================================================>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>--
>| Content-Class: urn:content-classes:message
>| From: "Liz Groom" <liz.groom@.mcafeetaft.com>
>| Sender: "Liz Groom" <liz.groom@.mcafeetaft.com>
>| Subject: .mdf & .ldf Data stamp doesn't change
>| Date: Mon, 21 Jul 2003 15:34:59 -0700
>| Lines: 21
>| Message-ID: <048401c34fd8$518e0ce0$a401280a@.phx.gbl>
>| MIME-Version: 1.0
>| Content-Type: text/plain;
>| charset="iso-8859-1"
>| Content-Transfer-Encoding: 7bit
>| X-Newsreader: Microsoft CDO for Windows 2000
>| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>| Thread-Index: AcNP2FGOZoCsY1CuQcqmkgv+iZSkkw==>| Newsgroups: microsoft.public.sqlserver.server
>| Path: cpmsftngxa06.phx.gbl
>| Xref: cpmsftngxa06.phx.gbl
microsoft.public.sqlserver.server:297048
>| NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
>| X-Tomcat-NG: microsoft.public.sqlserver.server
>|
>| We just moved from an old SQL 7 server to a new SQL
2000
>| server (detatch & attach method)
>|
>| Since the move, the .mdf & .ldf file data stamps don't
>| change unless I reboot or stop the SQL services. Data
>| appears to be correct.
>|
>| FYI - this is the second instance of SQL on this box,
1st
>| instance doesn't seem to have this problem.
>| I am getting some performance monitor messages
indicating
>| excessive paging still working on that.
>|
>| This on a new HP dl380 with 1.5 GB of RAM and a HP MSA
>| 1000 SAN which was configured with ample of memory for
the
>| DB & Application.
>|
>|
>| Any ideas would be appreciated
>|
>| Thanks
>| Liz
>|
>.
>|||Hello Liz,
Thank you for your reply. We look forward to helping you in the future.
Thanks & Regards,
Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| Content-Class: urn:content-classes:message
| From: "Liz Groom" <liz.groom@.mcafeetaft.com>
| Sender: "Liz Groom" <liz.groom@.mcafeetaft.com>
| References: <048401c34fd8$518e0ce0$a401280a@.phx.gbl>
<GZtC16$TDHA.2560@.cpmsftngxa06.phx.gbl>
| Subject: RE: .mdf & .ldf Data stamp doesn't change
| Date: Tue, 22 Jul 2003 08:23:20 -0700
| Lines: 111
| Message-ID: <07b101c35065$2f00dad0$a001280a@.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNQZS8AWWlh2cE/T2y0N1QaoloMBg==| Newsgroups: microsoft.public.sqlserver.server
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:297137
| NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Thanks Peter! Glad to know that it's not a problem --
| Nothing like being a little paranoid! :)
| Liz
|
| >--Original Message--
| >Hello Liz,
| >
| >Thank you for your posting! From your post I understand
| that the .mdf &
| >.ldf file data stamps don't change unless you reboot or
| stop the SQL
| >services.
| >
| >Based on my research, this behavior is as desinged.
| The .mdf & .ldf files
| >are opened by SQL server service to read/write
| data. "last modified date"
| >is updated only when physical file structure is updated.
| Another scenario -
| >exception - is that when SQL server service
| restarts "last modified date"
| >is reset. This means when "last modified date" for an
| mdf occurred when
| >SQL Data Engine grow/reduce file size. In the case for
| log file ldf, "last
| >modified date" is changed when VLF (Virtual Log File) is
| added/reduced.
| >
| >We are not able to use "last modified date" to determine
| if data of a
| >database is modified. we conclude that during numerous
| data update, it
| >could be a performance hit if "last modified date" is
| updated every time.
| >
| >We Recommend using tool such as SQL Profiler trace to
| validate if
| >transaction that modified records is completed.
| >
| >If you have further questions on the issue, please feel
| free to let me
| >know.
| >
| >Thanks & Regards,
| >
| >Peter Yang
| >MCSE2000, MCSA, MCDBA
| >Microsoft Partner Online Support
| >
| >Get Secure! - www.microsoft.com/security
| >
| >=====================================================| >When responding to posts, please "Reply to Group" via
| >your newsreader so that others may learn and benefit
| >from your issue.
| >=====================================================| >This posting is provided "AS IS" with no warranties, and
| confers no rights.
| >
| >
| >--
| >| Content-Class: urn:content-classes:message
| >| From: "Liz Groom" <liz.groom@.mcafeetaft.com>
| >| Sender: "Liz Groom" <liz.groom@.mcafeetaft.com>
| >| Subject: .mdf & .ldf Data stamp doesn't change
| >| Date: Mon, 21 Jul 2003 15:34:59 -0700
| >| Lines: 21
| >| Message-ID: <048401c34fd8$518e0ce0$a401280a@.phx.gbl>
| >| MIME-Version: 1.0
| >| Content-Type: text/plain;
| >| charset="iso-8859-1"
| >| Content-Transfer-Encoding: 7bit
| >| X-Newsreader: Microsoft CDO for Windows 2000
| >| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| >| Thread-Index: AcNP2FGOZoCsY1CuQcqmkgv+iZSkkw==| >| Newsgroups: microsoft.public.sqlserver.server
| >| Path: cpmsftngxa06.phx.gbl
| >| Xref: cpmsftngxa06.phx.gbl
| microsoft.public.sqlserver.server:297048
| >| NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
| >| X-Tomcat-NG: microsoft.public.sqlserver.server
| >|
| >| We just moved from an old SQL 7 server to a new SQL
| 2000
| >| server (detatch & attach method)
| >|
| >| Since the move, the .mdf & .ldf file data stamps don't
| >| change unless I reboot or stop the SQL services. Data
| >| appears to be correct.
| >|
| >| FYI - this is the second instance of SQL on this box,
| 1st
| >| instance doesn't seem to have this problem.
| >| I am getting some performance monitor messages
| indicating
| >| excessive paging still working on that.
| >|
| >| This on a new HP dl380 with 1.5 GB of RAM and a HP MSA
| >| 1000 SAN which was configured with ample of memory for
| the
| >| DB & Application.
| >|
| >|
| >| Any ideas would be appreciated
| >|
| >| Thanks
| >| Liz
| >|
| >
| >.
| >
|