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 hangs

Hi,
I have a production server which has about six user databases. Recently,
when I try to do a restore ( I wanted to see the available backup sets) on
any of the databases using Enterprise Manager (All Tasks -> Restore) it
hangs. However, it promptly brings a pop up window when I do the All Tasks ->
Backup. What might be causing it to behave this way?
Thanks in advance.
Hi
Perhaps you need to delete a backup history
http://weblogs.sqlteam.com/geoffh/archive/2008/01/21/MSDB-Performance-Tuning.aspx
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:B67B18F5-2ACD-49E5-A7EA-AA5A65487B68@.microsoft.com...
> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All
> Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.
|||We are seeing this too. The only change we have done recently is applying
SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
from a device. Specifically, it hangs when we click "Add" on the Specify
Backup dialog. We have no problems using the "From Database" option, so I do
not believe it has anything to do with MSDB indexes.
"ronnie" wrote:

> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.
|||I have narrowed this down to the command "insert #avmed exec
master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
xpStar90.dll. Has anyone ever seen what might cause this?
"Brent" wrote:
[vbcol=seagreen]
> We are seeing this too. The only change we have done recently is applying
> SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> from a device. Specifically, it hangs when we click "Add" on the Specify
> Backup dialog. We have no problems using the "From Database" option, so I do
> not believe it has anything to do with MSDB indexes.
> "ronnie" wrote:
|||Restarting the server resolved this.
"Brent" wrote:
[vbcol=seagreen]
> I have narrowed this down to the command "insert #avmed exec
> master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> xpStar90.dll. Has anyone ever seen what might cause this?
> "Brent" wrote:
|||I tried deleting the backuphistory but it didn't work. Maybe I need to
restart the server.
"Brent" wrote:
[vbcol=seagreen]
> Restarting the server resolved this.
> "Brent" wrote:
|||Our SQL Instance is clustered, so we failed over to the other node and
everything is fine. As soon as we restarted the node where things were
hanging, we started getting alerts on that the C drive is going bad. I think
this is why it was having trouble calling the dll. You may have a similar
issue. Are you using any monitoring tools like Sitescope to monitor the
hardware? You may have a drive that is going bad.
"ronnie" wrote:
[vbcol=seagreen]
> I tried deleting the backuphistory but it didn't work. Maybe I need to
> restart the server.
> "Brent" wrote:

Enterprise Manager hangs

Hi,
I have a production server which has about six user databases. Recently,
when I try to do a restore ( I wanted to see the available backup sets) on
any of the databases using Enterprise Manager (All Tasks -> Restore) it
hangs. However, it promptly brings a pop up window when I do the All Tasks ->
Backup. What might be causing it to behave this way?
Thanks in advance.Hi
Perhaps you need to delete a backup history
http://weblogs.sqlteam.com/geoffh/archive/2008/01/21/MSDB-Performance-Tuning.aspx
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:B67B18F5-2ACD-49E5-A7EA-AA5A65487B68@.microsoft.com...
> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All
> Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.|||We are seeing this too. The only change we have done recently is applying
SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
from a device. Specifically, it hangs when we click "Add" on the Specify
Backup dialog. We have no problems using the "From Database" option, so I do
not believe it has anything to do with MSDB indexes.
"ronnie" wrote:
> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.|||I have narrowed this down to the command "insert #avmed exec
master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
xpStar90.dll. Has anyone ever seen what might cause this?
"Brent" wrote:
> We are seeing this too. The only change we have done recently is applying
> SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> from a device. Specifically, it hangs when we click "Add" on the Specify
> Backup dialog. We have no problems using the "From Database" option, so I do
> not believe it has anything to do with MSDB indexes.
> "ronnie" wrote:
> > Hi,
> >
> > I have a production server which has about six user databases. Recently,
> > when I try to do a restore ( I wanted to see the available backup sets) on
> > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > Backup. What might be causing it to behave this way?
> >
> > Thanks in advance.|||Restarting the server resolved this.
"Brent" wrote:
> I have narrowed this down to the command "insert #avmed exec
> master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> xpStar90.dll. Has anyone ever seen what might cause this?
> "Brent" wrote:
> > We are seeing this too. The only change we have done recently is applying
> > SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> > from a device. Specifically, it hangs when we click "Add" on the Specify
> > Backup dialog. We have no problems using the "From Database" option, so I do
> > not believe it has anything to do with MSDB indexes.
> >
> > "ronnie" wrote:
> >
> > > Hi,
> > >
> > > I have a production server which has about six user databases. Recently,
> > > when I try to do a restore ( I wanted to see the available backup sets) on
> > > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > > Backup. What might be causing it to behave this way?
> > >
> > > Thanks in advance.|||I tried deleting the backuphistory but it didn't work. Maybe I need to
restart the server.
"Brent" wrote:
> Restarting the server resolved this.
> "Brent" wrote:
> > I have narrowed this down to the command "insert #avmed exec
> > master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> > master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> > xpStar90.dll. Has anyone ever seen what might cause this?
> >
> > "Brent" wrote:
> >
> > > We are seeing this too. The only change we have done recently is applying
> > > SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> > > from a device. Specifically, it hangs when we click "Add" on the Specify
> > > Backup dialog. We have no problems using the "From Database" option, so I do
> > > not believe it has anything to do with MSDB indexes.
> > >
> > > "ronnie" wrote:
> > >
> > > > Hi,
> > > >
> > > > I have a production server which has about six user databases. Recently,
> > > > when I try to do a restore ( I wanted to see the available backup sets) on
> > > > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > > > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > > > Backup. What might be causing it to behave this way?
> > > >
> > > > Thanks in advance.|||Our SQL Instance is clustered, so we failed over to the other node and
everything is fine. As soon as we restarted the node where things were
hanging, we started getting alerts on that the C drive is going bad. I think
this is why it was having trouble calling the dll. You may have a similar
issue. Are you using any monitoring tools like Sitescope to monitor the
hardware? You may have a drive that is going bad.
"ronnie" wrote:
> I tried deleting the backuphistory but it didn't work. Maybe I need to
> restart the server.
> "Brent" wrote:
> > Restarting the server resolved this.
> >
> > "Brent" wrote:
> >
> > > I have narrowed this down to the command "insert #avmed exec
> > > master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> > > master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> > > xpStar90.dll. Has anyone ever seen what might cause this?
> > >
> > > "Brent" wrote:
> > >
> > > > We are seeing this too. The only change we have done recently is applying
> > > > SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> > > > from a device. Specifically, it hangs when we click "Add" on the Specify
> > > > Backup dialog. We have no problems using the "From Database" option, so I do
> > > > not believe it has anything to do with MSDB indexes.
> > > >
> > > > "ronnie" wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have a production server which has about six user databases. Recently,
> > > > > when I try to do a restore ( I wanted to see the available backup sets) on
> > > > > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > > > > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > > > > Backup. What might be causing it to behave this way?
> > > > >
> > > > > Thanks in advance.

Enterprise Manager Connection Issues

Hello,
I am having trouble connecting from enterprise
manager to a sql 2000 box. I can connect to all of our
other production boxes. This is a new box that we built
and I cannot connect. When I go to register it in
Enterprise Manager the error message says "Driver Not
Capable". I'm not sure exactly what this means. All I'm
trying to do is connect to the box. Is there a driver
either on my local laptop or on the server side that
isn't set up right or maybe needs to be updated? I can
open up the database locally on the server and I can
register other servers on it and have that server
registered to other servers. I know other people on my
team are not able to connect to it as well, so I know
it's not just me. Any help would be greatly
appreciated. Thanks.
-Craig CoffaroHello -
The error message "Driver not capable" indicates the problem
to be with the SQL driver. Check the registry entry
HKEY_LOCAL_MACHNE\Software\ODBC\ODBCINST
.INI
Check the driver location in the above registry entry. Check for
SQLsrv32.dll version. If the registry location is pointing to incorrect
file, change it and make it point to the correct one.
Have you installed Crystal reports after installing SQL server?
Regards,
Chandra
This posting is provided "AS IS" with no warranties, and confers no rights.
"Craig Coffaro" <craig.coffaro@.kroger.com> wrote in message
news:902d01c4052c$5d59e990$a501280a@.phx.gbl...
> Hello,
> I am having trouble connecting from enterprise
> manager to a sql 2000 box. I can connect to all of our
> other production boxes. This is a new box that we built
> and I cannot connect. When I go to register it in
> Enterprise Manager the error message says "Driver Not
> Capable". I'm not sure exactly what this means. All I'm
> trying to do is connect to the box. Is there a driver
> either on my local laptop or on the server side that
> isn't set up right or maybe needs to be updated? I can
> open up the database locally on the server and I can
> register other servers on it and have that server
> registered to other servers. I know other people on my
> team are not able to connect to it as well, so I know
> it's not just me. Any help would be greatly
> appreciated. Thanks.
> -Craig Coffaro|||Chandra,
Yes I did install Crystal Reports 6 last week and ever since then
I have had problems with my SQL connections. Thanks for the advice and
I will give this a try. Thanks again.
Craig
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Chandra,
One other question I have is when I go to the registry:
HKEY_LOCAL_MACHNE\Software\ODBC\ODBCINST
.INI and I go down to SQL Server
I see in the window on the right, Driver and Setup both have the same
path with the sqlsrv32.dll in it. I also see DrverODBCver being
03.50...what exactly am I looking for or what do I need to be doing
witht this info? Is there a version of the ODBC driver that I should be
updating? Where exactly can I find this? Or is it the path
C:\WINDOWS\SYSTEM\sqlsrv32.dll that is the problem, if this is the
problem what path should it be? How does the installation of Crystal
Reports affect SQL? Any help you have for me Chandra is greatly
apprecaited. Thanks.
-Craig Coffaro
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||I'm not clear on what your question is. Do you need to find the version of
MDAC? If so, you can download the MDAC Component Checker from
microsoft.com/downloads.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Enterprise Manager - SQL Server does not exist or access denied

Hi there,

We have a production server in our environment that I am the only one in the company who is having a problem hitting with Enterprise manager. The server is called 'PRODSQLSRV'. When I ping the server, I get the IP. When I try to connect to it using Enterprise manager, it shows up on the list of available servers, but then when I move it from the left box to the right box of the 'New SQL Server Registration' process, take the rest of the defaults, I get the message 'PRODSQLSRV - SQL Server does not exist or access denied'.

I have checked and I have both TCP/IP and Named Pipes enabled. At the suggestion of the Network admin, I manually typed in the server and domain name as 'PRODSQLSRV.VOLCANO.COM' (all names have been changed to protect the innocent) which is the server name + domain name. With this 'Enterprise manager works fine getting to the server. All this would be fine and good I guess, but none of our vendor written software which accesses that server works on my machine either. And they are not enclined to change their software just for my machine.

If anyone has any suggestions, it would be greatly appreciated. Thanks! - Eric-

I am not sure what is cuasing.. it may be dns resolution issue...

You can add the name in host file or

You can create an alias in sql server "Client Network utility" to resolve this issue.

|||I tried both the HOST file entry and the Client Network Utility suggestion and neither one resolved the issue. Sorry. |||

looks more of a DNS issue but did you try registering with IP address only and not with the name, checking the TCPIP port at the server and client, all the required services at the server running and if other ppl in your network able to get it in their EM

|||Turned out that we had two machines with the same IP hard coded in them. Thanks for pointing me in the right direction. _- Eric -

Enterprise Manager - SQL Server does not exist or access denied

Hi there,

We have a production server in our environment that I am the only one in the company who is having a problem hitting with Enterprise manager. The server is called 'PRODSQLSRV'. When I ping the server, I get the IP. When I try to connect to it using Enterprise manager, it shows up on the list of available servers, but then when I move it from the left box to the right box of the 'New SQL Server Registration' process, take the rest of the defaults, I get the message 'PRODSQLSRV - SQL Server does not exist or access denied'.

I have checked and I have both TCP/IP and Named Pipes enabled. At the suggestion of the Network admin, I manually typed in the server and domain name as 'PRODSQLSRV.VOLCANO.COM' (all names have been changed to protect the innocent) which is the server name + domain name. With this 'Enterprise manager works fine getting to the server. All this would be fine and good I guess, but none of our vendor written software which accesses that server works on my machine either. And they are not enclined to change their software just for my machine.

If anyone has any suggestions, it would be greatly appreciated. Thanks! - Eric-

I am not sure what is cuasing.. it may be dns resolution issue...

You can add the name in host file or

You can create an alias in sql server "Client Network utility" to resolve this issue.

|||I tried both the HOST file entry and the Client Network Utility suggestion and neither one resolved the issue. Sorry. |||

looks more of a DNS issue but did you try registering with IP address only and not with the name, checking the TCPIP port at the server and client, all the required services at the server running and if other ppl in your network able to get it in their EM

|||Turned out that we had two machines with the same IP hard coded in them. Thanks for pointing me in the right direction. _- Eric -