Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" i
s
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processe
s
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host"
is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3
a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client,
if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in S
P3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) ther
e
> are buttons that will let you change the order, and to check the for serve
r
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipe
s
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John
Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts
Friday, March 30, 2012
named pipes vs tcp
Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
Dan D.
Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John
|||I understand. Thanks.
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John
|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
Dan D.
Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John
|||I understand. Thanks.
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John
|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John
named pipes vs tcp
Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
> > Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> > enable in network libraries. I noticed in EM under current activity and
> > process info for some processes named pipes is used and for other processes
> > something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> > "host" for the process is the server, then it uses LPC but when the "host" is
> > a workstation it uses named pipes. Does it use named pipes for the
> > workstations because it is listed first in the network libraries? Is named
> > pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> > second or just remove named pipes?
> >
> > Thanks,
> > --
> > Dan D.
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
Johnsql
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
> > Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> > enable in network libraries. I noticed in EM under current activity and
> > process info for some processes named pipes is used and for other processes
> > something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> > "host" for the process is the server, then it uses LPC but when the "host" is
> > a workstation it uses named pipes. Does it use named pipes for the
> > workstations because it is listed first in the network libraries? Is named
> > pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> > second or just remove named pipes?
> >
> > Thanks,
> > --
> > Dan D.
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
Johnsql
Friday, March 23, 2012
Name Pipe Hijacking Patch Problem
I've got a little problem. I pushed out the MS Named Pipe patch (MS03-031, q815495) to a SQL 7.0 SP4 server. We have an application that uses Named Pipes. After applying the patch the users weren't able to connect. Administrative users can connect ok.
We turned around and attempted the Patch to the Patch (Q823492) which was supposed to fix this problem. As you can tell it didn't fix the problem. We were able to move the clients over to TCP/IP and get them off of the Named Pipes but we still have processes internal to this application that aren't able to work.
We looked at backing out the patch but that is going to mean a rebuild of the database and this SQL database is almost 40 GB. I would rather find another method if at all possible to resolve this issue. Does anyone have any idea's? Any help is appreciated!
Thanks from a newbie!Hi...
i'm kind of having the same problem here. the applications that runs on SQL7.0 is not working properly now. is there a way that i can uninstall this patch?
thank you
We turned around and attempted the Patch to the Patch (Q823492) which was supposed to fix this problem. As you can tell it didn't fix the problem. We were able to move the clients over to TCP/IP and get them off of the Named Pipes but we still have processes internal to this application that aren't able to work.
We looked at backing out the patch but that is going to mean a rebuild of the database and this SQL database is almost 40 GB. I would rather find another method if at all possible to resolve this issue. Does anyone have any idea's? Any help is appreciated!
Thanks from a newbie!Hi...
i'm kind of having the same problem here. the applications that runs on SQL7.0 is not working properly now. is there a way that i can uninstall this patch?
thank you
Monday, March 19, 2012
Mysterious SQL Server Dropping Tables
We had just setup MS SQL 2000 (SP3), running on Windows 2000 (SP4). Both SQL
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.
> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
Steven Ung
"The source of all greatness lies within you" - Anonymous
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.
> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
Steven Ung
"The source of all greatness lies within you" - Anonymous
Mysterious SQL Server Dropping Tables
We had just setup MS SQL 2000 (SP3), running on Windows 2000 (SP4). Both SQL
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> > This is a newly setup server but we're observing the tables in the SQL
> > server dropping out of no apparent reason. A check on the actual data
> > directory we found that the database .LDF is missing and the EM marks it
> > as
> > 'suspect'.
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.
> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> > This is a newly setup server but we're observing the tables in the SQL
> > server dropping out of no apparent reason. A check on the actual data
> > directory we found that the database .LDF is missing and the EM marks it
> > as
> > 'suspect'.
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.
> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous
Mysterious SQL Server Dropping Tables
We had just setup MS SQL 2000 (SP3), running on Windows 2000 (SP4). Both SQL
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
Steven Ung
"The source of all greatness lies within you" - Anonymous
> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.
> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
Steven Ung
"The source of all greatness lies within you" - Anonymous
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
Steven Ung
"The source of all greatness lies within you" - Anonymous
> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.
> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
Steven Ung
"The source of all greatness lies within you" - Anonymous
Subscribe to:
Posts (Atom)