.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
| >|
| >
| >.
| >
|

...is null or not an object error

I am working in html/asp within VisInterDev 6.0. Everything was working fine until I moved a text box from one page to another. I took it from within a form on one page to a form on another (and made the necessary changes in the two pages).

Here is the code that is generating the error:

<body onload="java script:eventreg3.dist.focus();">

However I am using syntactically indentical code on other pages that work fine so I know the problem is not with that line.

It appears that it is not able to find the "dist" text box, but I have been over and over the html and can't find an issue. If I take that line out (keeping the <body> of course) it doesn't generate an error but my submit button doesn't work.

I have also noted that VisInterDev appears to eliminate, or not put in, double quotes around tag attributes. For instance, size="2" appears as size=2. I thought the double quotes were a requirement?

ANy help here? Thanks a ton!!!could it be the space between java and script?

rudy|||but that wasn't it. That space didn't actually exist in the code itself. Sorry for wasting your time. I have no idea what the deal is.

(Repost) Problems installing SQL 2005 Express after trying VS.NET 2005 Beta 2

Repost: This message had moved into another thread. Not sure why so I thought I'd repost as a new thread just to make sure it gets read ok :)
-
Hi Everyone,
I recently installed Visual Studio .NET 2005 Beta 2 which included SQL 2005 Community Technology Preview. After installing it all, I was no longer able to connect to my SQL 2000 instance in Enterprise Manager. The application opened ok but whenever I tried to browse the server or register it again, it was giving me an error relating to named pipes which really confused me since I was trying to connect to a SQL 2000 database through the SQL 2000 application. I was able to use the 2005 equivalent application (the name eludes me right now) to connect to the \SQLEXPRESS instance. All this time I could still connect to the default instance through Query Analyser and my .NET Web Applications that used SQL databases.
I later had to uninstall the betas because I needed a newer version of the .NET Framework to work with DotNetNuke 4.0. (A whole other story there...)
After uninstalling everything relating to the betas (which I had to do carefully in a prescribed order) I found that I couldn't even open Enterprise Manager properly. It had a big error message in the main display window. I discovered from a forum somewhere that I had to re-register a dll file to fix it. I did this and everything was back to normal.
(pause for breath)
OK, so then I downloaded Visual Web Developer 2005 Express Edition and installed it. Everything was great until the end of the SQL Server 2005 Express Edition setup when I was told it had failed to install. I haven't looked through ALL the log files but in the summary log file, the following message is reported for all three errors:
"[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe."
I am running Windows XP, SP2 with everything up to date in Windows Update. The Beta 2 of VS.NET was the only beta software I've installed. I'm not trying to connect to a different machine or anything either. VS and SQL are both on the same machine. The only other thing that may be relevant is that the SQL 2000 I have is an evaulation version. I don't think that affects it but you never know. It's often the most overlooked variable that trips you.
Does anyone have any suggestions about how to remedy this?
Thanks for taking the time to read about my problem :)Update:
I solved the problem by backing up my data and re-installing Windows. I now have Visual Web Developer and SQL 2005 Express running alongside Visual Studio 2003 Enterprise Developer, MSDE and SQL 2000.
I don't know if there was a simpler solution but I had spent too much time on it already. Hurrah for my new Maxtor OneTouch II external 300GB beast that carried the burden of my data during these difficult hours!

(Repost) Problems installing SQL 2005 Express after trying VS.NET 2005 Beta 2

Repost: This message had moved into another thread. Not sure why so I thought I'd repost as a new thread just to make sure it gets read ok :)
-
Hi Everyone,
I recently installed Visual Studio .NET 2005 Beta 2 which included SQL 2005 Community Technology Preview. After installing it all, I was no longer able to connect to my SQL 2000 instance in Enterprise Manager. The application opened ok but whenever I tried to browse the server or register it again, it was giving me an error relating to named pipes which really confused me since I was trying to connect to a SQL 2000 database through the SQL 2000 application. I was able to use the 2005 equivalent application (the name eludes me right now) to connect to the \SQLEXPRESS instance. All this time I could still connect to the default instance through Query Analyser and my .NET Web Applications that used SQL databases.
I later had to uninstall the betas because I needed a newer version of the .NET Framework to work with DotNetNuke 4.0. (A whole other story there...)
After uninstalling everything relating to the betas (which I had to do carefully in a prescribed order) I found that I couldn't even open Enterprise Manager properly. It had a big error message in the main display window. I discovered from a forum somewhere that I had to re-register a dll file to fix it. I did this and everything was back to normal.
(pause for breath)
OK, so then I downloaded Visual Web Developer 2005 Express Edition and installed it. Everything was great until the end of the SQL Server 2005 Express Edition setup when I was told it had failed to install. I haven't looked through ALL the log files but in the summary log file, the following message is reported for all three errors:
"[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe."
I am running Windows XP, SP2 with everything up to date in Windows Update. The Beta 2 of VS.NET was the only beta software I've installed. I'm not trying to connect to a different machine or anything either. VS and SQL are both on the same machine. The only other thing that may be relevant is that the SQL 2000 I have is an evaulation version. I don't think that affects it but you never know. It's often the most overlooked variable that trips you.
Does anyone have any suggestions about how to remedy this?
Thanks for taking the time to read about my problem :)Update:

I solved the problem by backing up my data and re-installing Windows. I

now have Visual Web Developer and SQL 2005 Express running alongside

Visual Studio 2003 Enterprise Developer, MSDE and SQL 2000.

I don't know if there was a simpler solution but I had spent too much

time on it already. Hurrah for my new Maxtor OneTouch II external 300GB

beast that carried the burden of my data during these difficult hours!