Entries in Sysindexes

Recently a copy of a production database was made in order to try to improve
for an application that was experiencing slowness. Performance had
apparently improved until today. The developers are claiming that the
degredation in performance is due to extra enties in sysindexes with names
starting with '_WA_SYS_'. A more complete example is
'_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
When I execute sp_helpindex on a table with these kind of entires, I do not
see anything that corresponds to this name. I did notice that for a given
table there could be many entries like this. I do see entires in sysindexes
corresponding to actual indexes. I've also noticed that the entries startin
g
with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
Can someone explain what these '_WA_SYS_' entries are and can they be
deleted safely?
There is a mainteneace plan set up to due data & index page reorganization
everyday except Sunday. Could this be what is creating this entires?
Thanks
--
MGI believe those are index column statistics and I am sure they are not the
cause of any degraded performance. IMHO you should not delete them.
Nathan H. Omukwenyi.
"MGeles" <michael.geles@.thomson.com> wrote in message
news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
> Recently a copy of a production database was made in order to try to
> improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do
> not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in
> sysindexes
> corresponding to actual indexes. I've also noticed that the entries
> starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||When the Auto Create Statistics option is enabled, _WA_ indexes are
created for columns that do not have an index.
Somewhere I read, can't find the article right now, that if you are
seeing indexes named that way, it is advisable to add indexes to replace
them, as the Auto created ones are not as efficient as a regular index.
The article also stated that the Auto Create Statistics should not be
disable as any index is better then none.
HTH
Michael
nathan wrote:
> I believe those are index column statistics and I am sure they are not the
> cause of any degraded performance. IMHO you should not delete them.
> Nathan H. Omukwenyi.
>
>
> "MGeles" <michael.geles@.thomson.com> wrote in message
> news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
>|||"Michael T" <michaelteff@.skyline.com> wrote in message
news:uD1bdQlYGHA.4424@.TK2MSFTNGP05.phx.gbl...
> When the Auto Create Statistics option is enabled, _WA_ indexes are
> created for columns that do not have an index.
> Somewhere I read, can't find the article right now, that if you are seeing
> indexes named that way, it is advisable to add indexes to replace them, as
> the Auto created ones are not as efficient as a regular index. The article
> also stated that the Auto Create Statistics should not be disable as any
> index is better then none.
>
Ok. Indexes and Statistics are distinct, but related objects. When you
create an index, statistics are created automatically, but you might want to
create additional statistics on unindexed columns or sets of columns.
See:
Statistics Used by the Query Optimizer in Microsoft SQL Server 2005
http://www.microsoft.com/technet/pr...5/qrystats.mspx
Much of the information is valid for SQL 2000 too.
David|||MGeles,
Those entries are create automatically by sql server when the database
option "auto create statistics" is on. SQL Server create those statistics on
columns used in the "join" clause, or in the "where" clause, and there is no
t
an index associated to them (from where sql server can access distribution
statistics about those columns). These statistics are used by the query
optimizer when creating the execution plan. If you delete those entries, SQL
Server will create them again as soon as it needs them.
Statistical maintenance functionality (autostats) in SQL Server
http://support.microsoft.com/kb/q195565/
AMB
"MGeles" wrote:

> Recently a copy of a production database was made in order to try to impro
ve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do no
t
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindex
es
> corresponding to actual indexes. I've also noticed that the entries start
ing
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||MG-
Check out the link below.
http://www.extremeexperts.com/SQL/FAQ/SysStats.aspx
--
Thomas
"MGeles" wrote:

> Recently a copy of a production database was made in order to try to impro
ve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do no
t
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindex
es
> corresponding to actual indexes. I've also noticed that the entries start
ing
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MGsql

Entries in Sysindexes

Recently a copy of a production database was made in order to try to improve
for an application that was experiencing slowness. Performance had
apparently improved until today. The developers are claiming that the
degredation in performance is due to extra enties in sysindexes with names
starting with '_WA_SYS_'. A more complete example is
'_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
When I execute sp_helpindex on a table with these kind of entires, I do not
see anything that corresponds to this name. I did notice that for a given
table there could be many entries like this. I do see entires in sysindexes
corresponding to actual indexes. I've also noticed that the entries starting
with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
Can someone explain what these '_WA_SYS_' entries are and can they be
deleted safely?
There is a mainteneace plan set up to due data & index page reorganization
everyday except Sunday. Could this be what is creating this entires?
Thanks
--
MGI believe those are index column statistics and I am sure they are not the
cause of any degraded performance. IMHO you should not delete them.
Nathan H. Omukwenyi.
"MGeles" <michael.geles@.thomson.com> wrote in message
news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
> Recently a copy of a production database was made in order to try to
> improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do
> not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in
> sysindexes
> corresponding to actual indexes. I've also noticed that the entries
> starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||When the Auto Create Statistics option is enabled, _WA_ indexes are
created for columns that do not have an index.
Somewhere I read, can't find the article right now, that if you are
seeing indexes named that way, it is advisable to add indexes to replace
them, as the Auto created ones are not as efficient as a regular index.
The article also stated that the Auto Create Statistics should not be
disable as any index is better then none.
HTH
Michael
nathan wrote:
> I believe those are index column statistics and I am sure they are not the
> cause of any degraded performance. IMHO you should not delete them.
> Nathan H. Omukwenyi.
>
>
> "MGeles" <michael.geles@.thomson.com> wrote in message
> news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
>> Recently a copy of a production database was made in order to try to
>> improve
>> for an application that was experiencing slowness. Performance had
>> apparently improved until today. The developers are claiming that the
>> degredation in performance is due to extra enties in sysindexes with names
>> starting with '_WA_SYS_'. A more complete example is
>> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
>> When I execute sp_helpindex on a table with these kind of entires, I do
>> not
>> see anything that corresponds to this name. I did notice that for a given
>> table there could be many entries like this. I do see entires in
>> sysindexes
>> corresponding to actual indexes. I've also noticed that the entries
>> starting
>> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
>> Can someone explain what these '_WA_SYS_' entries are and can they be
>> deleted safely?
>> There is a mainteneace plan set up to due data & index page reorganization
>> everyday except Sunday. Could this be what is creating this entires?
>> Thanks
>> --
>> MG
>|||"Michael T" <michaelteff@.skyline.com> wrote in message
news:uD1bdQlYGHA.4424@.TK2MSFTNGP05.phx.gbl...
> When the Auto Create Statistics option is enabled, _WA_ indexes are
> created for columns that do not have an index.
> Somewhere I read, can't find the article right now, that if you are seeing
> indexes named that way, it is advisable to add indexes to replace them, as
> the Auto created ones are not as efficient as a regular index. The article
> also stated that the Auto Create Statistics should not be disable as any
> index is better then none.
>
Ok. Indexes and Statistics are distinct, but related objects. When you
create an index, statistics are created automatically, but you might want to
create additional statistics on unindexed columns or sets of columns.
See:
Statistics Used by the Query Optimizer in Microsoft SQL Server 2005
http://www.microsoft.com/technet/prodtechnol/sql/2005/qrystats.mspx
Much of the information is valid for SQL 2000 too.
David|||MGeles,
Those entries are create automatically by sql server when the database
option "auto create statistics" is on. SQL Server create those statistics on
columns used in the "join" clause, or in the "where" clause, and there is not
an index associated to them (from where sql server can access distribution
statistics about those columns). These statistics are used by the query
optimizer when creating the execution plan. If you delete those entries, SQL
Server will create them again as soon as it needs them.
Statistical maintenance functionality (autostats) in SQL Server
http://support.microsoft.com/kb/q195565/
AMB
"MGeles" wrote:
> Recently a copy of a production database was made in order to try to improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindexes
> corresponding to actual indexes. I've also noticed that the entries starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||MG-
Check out the link below.
http://www.extremeexperts.com/SQL/FAQ/SysStats.aspx
--
Thomas
"MGeles" wrote:
> Recently a copy of a production database was made in order to try to improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindexes
> corresponding to actual indexes. I've also noticed that the entries starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG

Enterprise Manager performance

Not sure what category this belongs to, so sqlserver.server it is...
Anyway, I am experiencing signficant performance problems using SS2K
Enterprise Manager. Any action, including something as simple as expanding
the list of databases on a server takes takes an incredibly long time.
Some examples...
1. Expanding the database folder to show the databases on a server takes
upwards of 2 minutes to complete
2. Saving a DTS package takes upwards of 2 minutes
3. Opening up a DTS package, and then double clicking on a Transform Data
Task can take upwards of 5 minutes.
I am the only one in our group that is having these problems, and our dba is
at a loss. Any suggestions?
I am running WinXP SP1
What method are you using to connect to your SQL Server? TCP/IP, Named
Pipes, Shared Memory?
Perhaps you need to enable TCP/IP and connect that way...
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
> Not sure what category this belongs to, so sqlserver.server it is...
> Anyway, I am experiencing signficant performance problems using SS2K
> Enterprise Manager. Any action, including something as simple as
> expanding
> the list of databases on a server takes takes an incredibly long time.
> Some examples...
> 1. Expanding the database folder to show the databases on a server takes
> upwards of 2 minutes to complete
> 2. Saving a DTS package takes upwards of 2 minutes
> 3. Opening up a DTS package, and then double clicking on a Transform Data
> Task can take upwards of 5 minutes.
> I am the only one in our group that is having these problems, and our dba
> is
> at a loss. Any suggestions?
> I am running WinXP SP1
|||This is a dumb question, but how do I tell? I added all of my servers via
the New SQL Server registration in Enterprise Manager. I don't get asked a
connection method, and there is no option to adjust that within any of my
Properties menus.
"Warren Brunk" wrote:

> What method are you using to connect to your SQL Server? TCP/IP, Named
> Pipes, Shared Memory?
> Perhaps you need to enable TCP/IP and connect that way...
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> */
>
> "Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
> news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
>
>
|||SQL 2005
http://msdn2.microsoft.com/en-us/library/ms190611.aspx
SQL 2000
http://www.verio.com/support/documen...fm?doc_id=4027
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Glenn Coello" <GlennCoello@.discussions.microsoft.com> wrote in message
news:F2CEF464-DA3F-42A5-850C-93573DD5FA96@.microsoft.com...[vbcol=seagreen]
> This is a dumb question, but how do I tell? I added all of my servers via
> the New SQL Server registration in Enterprise Manager. I don't get asked
> a
> connection method, and there is no option to adjust that within any of my
> Properties menus.
> "Warren Brunk" wrote:
|||Since you said you were using SQL Server 2000 and the EM, do the following:
Start -> All Programs -> SQL Server -> Client Network Utility -> General tab
You will want to check this on both the client and the server to see which
protocols are enabled on each.
At least this will get you the protocols enabled - I don't know about fixing
the solution to your problem however, sorry. This is one place to start, as
Warren mentioned.
"Glenn Coello" <GlennCoello@.discussions.microsoft.com> wrote in message
news:F2CEF464-DA3F-42A5-850C-93573DD5FA96@.microsoft.com...[vbcol=seagreen]
> This is a dumb question, but how do I tell? I added all of my servers via
> the New SQL Server registration in Enterprise Manager. I don't get asked
> a
> connection method, and there is no option to adjust that within any of my
> Properties menus.
> "Warren Brunk" wrote:

Enterprise Manager performance

Not sure what category this belongs to, so sqlserver.server it is...
Anyway, I am experiencing signficant performance problems using SS2K
Enterprise Manager. Any action, including something as simple as expanding
the list of databases on a server takes takes an incredibly long time.
Some examples...
1. Expanding the database folder to show the databases on a server takes
upwards of 2 minutes to complete
2. Saving a DTS package takes upwards of 2 minutes
3. Opening up a DTS package, and then double clicking on a Transform Data
Task can take upwards of 5 minutes.
I am the only one in our group that is having these problems, and our dba is
at a loss. Any suggestions?
I am running WinXP SP1What method are you using to connect to your SQL Server? TCP/IP, Named
Pipes, Shared Memory?
Perhaps you need to enable TCP/IP and connect that way...
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
> Not sure what category this belongs to, so sqlserver.server it is...
> Anyway, I am experiencing signficant performance problems using SS2K
> Enterprise Manager. Any action, including something as simple as
> expanding
> the list of databases on a server takes takes an incredibly long time.
> Some examples...
> 1. Expanding the database folder to show the databases on a server takes
> upwards of 2 minutes to complete
> 2. Saving a DTS package takes upwards of 2 minutes
> 3. Opening up a DTS package, and then double clicking on a Transform Data
> Task can take upwards of 5 minutes.
> I am the only one in our group that is having these problems, and our dba
> is
> at a loss. Any suggestions?
> I am running WinXP SP1|||This is a dumb question, but how do I tell? I added all of my servers via
the New SQL Server registration in Enterprise Manager. I don't get asked a
connection method, and there is no option to adjust that within any of my
Properties menus.
"Warren Brunk" wrote:

> What method are you using to connect to your SQL Server? TCP/IP, Named
> Pipes, Shared Memory?
> Perhaps you need to enable TCP/IP and connect that way...
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> */
>
> "Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
> news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
>
>|||SQL 2005
http://msdn2.microsoft.com/en-us/library/ms190611.aspx
SQL 2000
http://www.verio.com/support/docume...cfm?doc_id=4027
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Glenn Coello" <GlennCoello@.discussions.microsoft.com> wrote in message
news:F2CEF464-DA3F-42A5-850C-93573DD5FA96@.microsoft.com...[vbcol=seagreen]
> This is a dumb question, but how do I tell? I added all of my servers via
> the New SQL Server registration in Enterprise Manager. I don't get asked
> a
> connection method, and there is no option to adjust that within any of my
> Properties menus.
> "Warren Brunk" wrote:
>|||Since you said you were using SQL Server 2000 and the EM, do the following:
Start -> All Programs -> SQL Server -> Client Network Utility -> General tab
You will want to check this on both the client and the server to see which
protocols are enabled on each.
At least this will get you the protocols enabled - I don't know about fixing
the solution to your problem however, sorry. This is one place to start, as
Warren mentioned.
"Glenn Coello" <GlennCoello@.discussions.microsoft.com> wrote in message
news:F2CEF464-DA3F-42A5-850C-93573DD5FA96@.microsoft.com...[vbcol=seagreen]
> This is a dumb question, but how do I tell? I added all of my servers via
> the New SQL Server registration in Enterprise Manager. I don't get asked
> a
> connection method, and there is no option to adjust that within any of my
> Properties menus.
> "Warren Brunk" wrote:
>

Enterprise Manager performance

Not sure what category this belongs to, so sqlserver.server it is...
Anyway, I am experiencing signficant performance problems using SS2K
Enterprise Manager. Any action, including something as simple as expanding
the list of databases on a server takes takes an incredibly long time.
Some examples...
1. Expanding the database folder to show the databases on a server takes
upwards of 2 minutes to complete
2. Saving a DTS package takes upwards of 2 minutes
3. Opening up a DTS package, and then double clicking on a Transform Data
Task can take upwards of 5 minutes.
I am the only one in our group that is having these problems, and our dba is
at a loss. Any suggestions?
I am running WinXP SP1What method are you using to connect to your SQL Server? TCP/IP, Named
Pipes, Shared Memory?
Perhaps you need to enable TCP/IP and connect that way...
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
> Not sure what category this belongs to, so sqlserver.server it is...
> Anyway, I am experiencing signficant performance problems using SS2K
> Enterprise Manager. Any action, including something as simple as
> expanding
> the list of databases on a server takes takes an incredibly long time.
> Some examples...
> 1. Expanding the database folder to show the databases on a server takes
> upwards of 2 minutes to complete
> 2. Saving a DTS package takes upwards of 2 minutes
> 3. Opening up a DTS package, and then double clicking on a Transform Data
> Task can take upwards of 5 minutes.
> I am the only one in our group that is having these problems, and our dba
> is
> at a loss. Any suggestions?
> I am running WinXP SP1|||This is a dumb question, but how do I tell? I added all of my servers via
the New SQL Server registration in Enterprise Manager. I don't get asked a
connection method, and there is no option to adjust that within any of my
Properties menus.
"Warren Brunk" wrote:
> What method are you using to connect to your SQL Server? TCP/IP, Named
> Pipes, Shared Memory?
> Perhaps you need to enable TCP/IP and connect that way...
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> */
>
> "Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
> news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
> > Not sure what category this belongs to, so sqlserver.server it is...
> >
> > Anyway, I am experiencing signficant performance problems using SS2K
> > Enterprise Manager. Any action, including something as simple as
> > expanding
> > the list of databases on a server takes takes an incredibly long time.
> >
> > Some examples...
> >
> > 1. Expanding the database folder to show the databases on a server takes
> > upwards of 2 minutes to complete
> >
> > 2. Saving a DTS package takes upwards of 2 minutes
> >
> > 3. Opening up a DTS package, and then double clicking on a Transform Data
> > Task can take upwards of 5 minutes.
> >
> > I am the only one in our group that is having these problems, and our dba
> > is
> > at a loss. Any suggestions?
> >
> > I am running WinXP SP1
>
>|||SQL 2005
http://msdn2.microsoft.com/en-us/library/ms190611.aspx
SQL 2000
http://www.verio.com/support/documents/view_article.cfm?doc_id=4027
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Glenn Coello" <GlennCoello@.discussions.microsoft.com> wrote in message
news:F2CEF464-DA3F-42A5-850C-93573DD5FA96@.microsoft.com...
> This is a dumb question, but how do I tell? I added all of my servers via
> the New SQL Server registration in Enterprise Manager. I don't get asked
> a
> connection method, and there is no option to adjust that within any of my
> Properties menus.
> "Warren Brunk" wrote:
>> What method are you using to connect to your SQL Server? TCP/IP, Named
>> Pipes, Shared Memory?
>> Perhaps you need to enable TCP/IP and connect that way...
>> --
>> /*
>> Warren Brunk - MCITP - SQL 2005, MCDBA
>> www.techintsolutions.com
>> */
>>
>> "Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
>> news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
>> > Not sure what category this belongs to, so sqlserver.server it is...
>> >
>> > Anyway, I am experiencing signficant performance problems using SS2K
>> > Enterprise Manager. Any action, including something as simple as
>> > expanding
>> > the list of databases on a server takes takes an incredibly long time.
>> >
>> > Some examples...
>> >
>> > 1. Expanding the database folder to show the databases on a server
>> > takes
>> > upwards of 2 minutes to complete
>> >
>> > 2. Saving a DTS package takes upwards of 2 minutes
>> >
>> > 3. Opening up a DTS package, and then double clicking on a Transform
>> > Data
>> > Task can take upwards of 5 minutes.
>> >
>> > I am the only one in our group that is having these problems, and our
>> > dba
>> > is
>> > at a loss. Any suggestions?
>> >
>> > I am running WinXP SP1
>>|||Since you said you were using SQL Server 2000 and the EM, do the following:
Start -> All Programs -> SQL Server -> Client Network Utility -> General tab
You will want to check this on both the client and the server to see which
protocols are enabled on each.
At least this will get you the protocols enabled - I don't know about fixing
the solution to your problem however, sorry. This is one place to start, as
Warren mentioned.
"Glenn Coello" <GlennCoello@.discussions.microsoft.com> wrote in message
news:F2CEF464-DA3F-42A5-850C-93573DD5FA96@.microsoft.com...
> This is a dumb question, but how do I tell? I added all of my servers via
> the New SQL Server registration in Enterprise Manager. I don't get asked
> a
> connection method, and there is no option to adjust that within any of my
> Properties menus.
> "Warren Brunk" wrote:
>> What method are you using to connect to your SQL Server? TCP/IP, Named
>> Pipes, Shared Memory?
>> Perhaps you need to enable TCP/IP and connect that way...
>> --
>> /*
>> Warren Brunk - MCITP - SQL 2005, MCDBA
>> www.techintsolutions.com
>> */
>>
>> "Glenn Coello" <Glenn Coello@.discussions.microsoft.com> wrote in message
>> news:99E9B96E-B46C-41CE-9D32-ED045594F0C2@.microsoft.com...
>> > Not sure what category this belongs to, so sqlserver.server it is...
>> >
>> > Anyway, I am experiencing signficant performance problems using SS2K
>> > Enterprise Manager. Any action, including something as simple as
>> > expanding
>> > the list of databases on a server takes takes an incredibly long time.
>> >
>> > Some examples...
>> >
>> > 1. Expanding the database folder to show the databases on a server
>> > takes
>> > upwards of 2 minutes to complete
>> >
>> > 2. Saving a DTS package takes upwards of 2 minutes
>> >
>> > 3. Opening up a DTS package, and then double clicking on a Transform
>> > Data
>> > Task can take upwards of 5 minutes.
>> >
>> > I am the only one in our group that is having these problems, and our
>> > dba
>> > is
>> > at a loss. Any suggestions?
>> >
>> > I am running WinXP SP1
>>

Enterprise manager and packages

Good day

I'm experiencing the following problem with Microsoft's Enterprise Manager:
When trying to open a package to edit it I get an error stating that the Server does not exists. However people connecting from another computer can use Enterprise Manager to open packages.

When I try to create a connection within a new package and I specify the server's name I get the same error however using 127.0.0.1 or localhost I do not get this error.

Please help

ThanxBecause 127.0.0.1 and (localhost) work fine, it would appear that your problem lies with WINS and/or DNS. My first guess would be a problem in your lmhosts (http://support.microsoft.com/default.aspx?scid=kb;en-us;314884) file (on your machine), probably an incorrect entry for the machine itself.

Try to ping your own machine (substituting you machine name instead of myhost) using:ping myhost -a-PatP|||Is your network library correctly in SQL client utilities ? You must have TCP/IP and/or Named pipes.