Capturing SQL code that generates error

I have an application that imports application data based on the Windows Installer .MSI schema into a SQL database. If it possible that the data in the tables exceeds the size allowed in our database. When that happens, an error message is generated. This
is fine as the user has the option to 'Ignore.'
The problem is that I cannot tell what application is being imported when the error message is produced. Is there a method to capturing the 'parent' SQL insert statements so that I can get the application name?
Thanks
Have you considered using Profiler? Let us know if you need help with using
Profiler to capture the statement and the error.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"DanetteB" <DanetteB@.discussions.microsoft.com> wrote in message
news:E5E14CFC-8F1C-49F5-AEE5-40C14448FC86@.microsoft.com...
I have an application that imports application data based on the Windows
Installer .MSI schema into a SQL database. If it possible that the data in
the tables exceeds the size allowed in our database. When that happens, an
error message is generated. This is fine as the user has the option to
'Ignore.'
The problem is that I cannot tell what application is being imported when
the error message is produced. Is there a method to capturing the 'parent'
SQL insert statements so that I can get the application name?
Thanks
|||Vyas -
Thanks for the reply. I have tried the Profiler, but I am not getting the data I need. I'm probably not capturing the correct information. Any suggestions would be much appreciated.
"Narayana Vyas Kondreddi" wrote:

> Have you considered using Profiler? Let us know if you need help with using
> Profiler to capture the statement and the error.
> --
> HTH,
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
> Is .NET important for a database professional?
> http://vyaskn.tripod.com/poll.htm
>
|||Vyas -
I got it - thank you for the Profiler suggestion. I went back into the tool and added the TSQL events.
DanetteB
"DanetteB" wrote:

> Vyas -
> Thanks for the reply. I have tried the Profiler, but I am not getting the data I need. I'm probably not capturing the correct information. Any suggestions would be much appreciated.
>
> "Narayana Vyas Kondreddi" wrote:
>

Capturing SQL code that generates error

I have an application that imports application data based on the Windows Ins
taller .MSI schema into a SQL database. If it possible that the data in the
tables exceeds the size allowed in our database. When that happens, an error
message is generated. This
is fine as the user has the option to 'Ignore.'
The problem is that I cannot tell what application is being imported when th
e error message is produced. Is there a method to capturing the 'parent' SQL
insert statements so that I can get the application name?
ThanksHave you considered using Profiler? Let us know if you need help with using
Profiler to capture the statement and the error.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"DanetteB" <DanetteB@.discussions.microsoft.com> wrote in message
news:E5E14CFC-8F1C-49F5-AEE5-40C14448FC86@.microsoft.com...
I have an application that imports application data based on the Windows
Installer .MSI schema into a SQL database. If it possible that the data in
the tables exceeds the size allowed in our database. When that happens, an
error message is generated. This is fine as the user has the option to
'Ignore.'
The problem is that I cannot tell what application is being imported when
the error message is produced. Is there a method to capturing the 'parent'
SQL insert statements so that I can get the application name?
Thanks|||Vyas -
Thanks for the reply. I have tried the Profiler, but I am not getting the da
ta I need. I'm probably not capturing the correct information. Any suggestio
ns would be much appreciated.
"Narayana Vyas Kondreddi" wrote:

> Have you considered using Profiler? Let us know if you need help with usin
g
> Profiler to capture the statement and the error.
> --
> HTH,
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
> Is .NET important for a database professional?
> http://vyaskn.tripod.com/poll.htm
>|||Vyas -
I got it - thank you for the Profiler suggestion. I went back into the tool
and added the TSQL events.
DanetteB
"DanetteB" wrote:

> Vyas -
> Thanks for the reply. I have tried the Profiler, but I am not getting the
data I need. I'm probably not capturing the correct information. Any suggest
ions would be much appreciated.
>
> "Narayana Vyas Kondreddi" wrote:
>
>

Capturing queries sent to SQL Server

I use a software package that queries a Microsoft SQL Server 2000 database
from a client side Windows application. The client application has a built
in report generator that allows users to easily produce complex reports.
The client application was written in Delphi, and uses Borland's BDE to
connect to the SQL Server.
I would like to trap the SQL code that is being produced and sent to the
SQL Server from the report generator (so that I can get a get a better
understanding of how to directly query the database outside of the report
generator).
Any suggestions on how to do this? Are there any third party products that
can provide me with this capability?
Thanks,
DeanOne of my favourite tools will do this "Profiler". It is in your SQL Server
program group.
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"dean" <deanbillings@.yahoo.com> wrote in message
news:Xns93B61780A829Bdean918yahoocom@.24.168.128.78...
> I use a software package that queries a Microsoft SQL Server 2000 database
> from a client side Windows application. The client application has a
built
> in report generator that allows users to easily produce complex reports.
> The client application was written in Delphi, and uses Borland's BDE to
> connect to the SQL Server.
> I would like to trap the SQL code that is being produced and sent to the
> SQL Server from the report generator (so that I can get a get a better
> understanding of how to directly query the database outside of the report
> generator).
> Any suggestions on how to do this? Are there any third party products
that
> can provide me with this capability?
> Thanks,
> Dean|||Dean,
You don't need a third party product. Take a look a SQL Profiler that comes
with SQL Server. The following article will help you get the most out of
Profiler http://www.sql-server-performance.com/sql_server_profiler_tips.asp.
J.R.
Largo SQL Tools
The Finest Collection of SQL Tools Available
http://www.largosqltools.com
"dean" <deanbillings@.yahoo.com> wrote in message
news:Xns93B61780A829Bdean918yahoocom@.24.168.128.78...
> I use a software package that queries a Microsoft SQL Server 2000 database
> from a client side Windows application. The client application has a
built
> in report generator that allows users to easily produce complex reports.
> The client application was written in Delphi, and uses Borland's BDE to
> connect to the SQL Server.
> I would like to trap the SQL code that is being produced and sent to the
> SQL Server from the report generator (so that I can get a get a better
> understanding of how to directly query the database outside of the report
> generator).
> Any suggestions on how to do this? Are there any third party products
that
> can provide me with this capability?
> Thanks,
> Dean|||And if you have already looked there and could not find anything but
parameter passing. Get the SPID and find the first calls that define the
procedure.
If it is totally obscure, Net Monitor will show you the text in
any packet sent to your machine.
I think that you should use SQL Profiler so that you have this skill
in your tool bag anyway.
"Largo SQL Tools" <nospam@.yahoo.com> wrote in message
news:unNOnjGSDHA.2676@.TK2MSFTNGP10.phx.gbl...
> Dean,
> You don't need a third party product. Take a look a SQL Profiler that
comes
> with SQL Server. The following article will help you get the most out of
> Profiler
http://www.sql-server-performance.com/sql_server_profiler_tips.asp.
> J.R.
> Largo SQL Tools
> The Finest Collection of SQL Tools Available
> http://www.largosqltools.com
>
> "dean" <deanbillings@.yahoo.com> wrote in message
> news:Xns93B61780A829Bdean918yahoocom@.24.168.128.78...
> > I use a software package that queries a Microsoft SQL Server 2000
database
> > from a client side Windows application. The client application has a
> built
> > in report generator that allows users to easily produce complex reports.
> > The client application was written in Delphi, and uses Borland's BDE to
> > connect to the SQL Server.
> >
> > I would like to trap the SQL code that is being produced and sent to the
> > SQL Server from the report generator (so that I can get a get a better
> > understanding of how to directly query the database outside of the
report
> > generator).
> >
> > Any suggestions on how to do this? Are there any third party products
> that
> > can provide me with this capability?
> >
> > Thanks,
> > Dean
>|||Profiler is definitely your best option. One of the best tools available
and well worth the perceived 'non productive' time spent using/learning it.
"dean" <deanbillings@.yahoo.com> wrote in message
news:Xns93B61780A829Bdean918yahoocom@.24.168.128.78...
> I use a software package that queries a Microsoft SQL Server 2000 database
> from a client side Windows application. The client application has a
built
> in report generator that allows users to easily produce complex reports.
> The client application was written in Delphi, and uses Borland's BDE to
> connect to the SQL Server.
> I would like to trap the SQL code that is being produced and sent to the
> SQL Server from the report generator (so that I can get a get a better
> understanding of how to directly query the database outside of the report
> generator).
> Any suggestions on how to do this? Are there any third party products
that
> can provide me with this capability?
> Thanks,
> Dean

Capture user that calls sp_start_job

I have 10 users assigned to SQLAgentOperatorRole. I want to track which of the users calls sp_start_job. I am using Windows authentication. How can I capture the identity of the user that calls sp_start_job?

I want to do something like "INSERT INTO tbJobHistory(JobName, RunDate, User)"

No, unless you run profiler or encapsulate the procedure callo in your own procedure, there is no way to this.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Can't write to SQL Table

I'm not the SQL admin, but I'm trying to help fix a problem. Here's the
situation:
Microsoft SQL Server running Windows 2000 Server. Workstation connecting
via ODBC using SQL Driver.
We have a program on the workstation that pulls information from a single
table. There are over 800 tables in the database. For some reason the
application "scans" the entire database every time it pulls data from the
table we need. This takes a very long time. To try to combat this, we
created a restricted ID that only has access to the table we want. Now
reading from the table much faster.
However, now we can't write to the table. The table name is
"ups_work_table". When we try to write data to it, we get an error
"ups_work_table_trig_ins No data found for row".
So the admin person (as I understand it) made the ID part of a group that
has greater rights. The problem here is that again the ID has access to all
the tables and reading/writing is painfully slow. There has been talk of
groups & roles and how the group settings override the settings of the ID.
So restricting the access of the ID is defeated by giving it greater rights.
My question is: How can we restrict the ID to access a single table and
give that ID read, write, insert, & delete permissions for that table?
Thanks.
Hi
The error "ups_work_table_trig_ins No data found for row" looks like an
error getting raised by some code in the "ups_work_table" insert trigger.
Have a look at that trigger. Possibly, a lookup is beign done on some other
data, and because a specific user is expected by the code, it fails.
Regards
Mike
"Terry Olsen" wrote:

> I'm not the SQL admin, but I'm trying to help fix a problem. Here's the
> situation:
> Microsoft SQL Server running Windows 2000 Server. Workstation connecting
> via ODBC using SQL Driver.
> We have a program on the workstation that pulls information from a single
> table. There are over 800 tables in the database. For some reason the
> application "scans" the entire database every time it pulls data from the
> table we need. This takes a very long time. To try to combat this, we
> created a restricted ID that only has access to the table we want. Now
> reading from the table much faster.
> However, now we can't write to the table. The table name is
> "ups_work_table". When we try to write data to it, we get an error
> "ups_work_table_trig_ins No data found for row".
> So the admin person (as I understand it) made the ID part of a group that
> has greater rights. The problem here is that again the ID has access to all
> the tables and reading/writing is painfully slow. There has been talk of
> groups & roles and how the group settings override the settings of the ID.
> So restricting the access of the ID is defeated by giving it greater rights.
> My question is: How can we restrict the ID to access a single table and
> give that ID read, write, insert, & delete permissions for that table?
> Thanks.
>
>

Can't write to SQL Table

I'm not the SQL admin, but I'm trying to help fix a problem. Here's the
situation:
Microsoft SQL Server running Windows 2000 Server. Workstation connecting
via ODBC using SQL Driver.
We have a program on the workstation that pulls information from a single
table. There are over 800 tables in the database. For some reason the
application "scans" the entire database every time it pulls data from the
table we need. This takes a very long time. To try to combat this, we
created a restricted ID that only has access to the table we want. Now
reading from the table much faster.
However, now we can't write to the table. The table name is
"ups_work_table". When we try to write data to it, we get an error
"ups_work_table_trig_ins No data found for row".
So the admin person (as I understand it) made the ID part of a group that
has greater rights. The problem here is that again the ID has access to all
the tables and reading/writing is painfully slow. There has been talk of
groups & roles and how the group settings override the settings of the ID.
So restricting the access of the ID is defeated by giving it greater rights.
My question is: How can we restrict the ID to access a single table and
give that ID read, write, insert, & delete permissions for that table?
Thanks.Hi
The error "ups_work_table_trig_ins No data found for row" looks like an
error getting raised by some code in the "ups_work_table" insert trigger.
Have a look at that trigger. Possibly, a lookup is beign done on some other
data, and because a specific user is expected by the code, it fails.
Regards
Mike
"Terry Olsen" wrote:

> I'm not the SQL admin, but I'm trying to help fix a problem. Here's the
> situation:
> Microsoft SQL Server running Windows 2000 Server. Workstation connecting
> via ODBC using SQL Driver.
> We have a program on the workstation that pulls information from a single
> table. There are over 800 tables in the database. For some reason the
> application "scans" the entire database every time it pulls data from the
> table we need. This takes a very long time. To try to combat this, we
> created a restricted ID that only has access to the table we want. Now
> reading from the table much faster.
> However, now we can't write to the table. The table name is
> "ups_work_table". When we try to write data to it, we get an error
> "ups_work_table_trig_ins No data found for row".
> So the admin person (as I understand it) made the ID part of a group that
> has greater rights. The problem here is that again the ID has access to a
ll
> the tables and reading/writing is painfully slow. There has been talk of
> groups & roles and how the group settings override the settings of the ID.
> So restricting the access of the ID is defeated by giving it greater right
s.
> My question is: How can we restrict the ID to access a single table and
> give that ID read, write, insert, & delete permissions for that table?
> Thanks.
>
>

Can't view Locks / Process ID

Hi,
We have SQL 7 running on Windows 2000 Server. For some reason we are
unable to view Locks / Process ID from workstations running Windows XP
SP2 with Enterprise Manager. Nothing shows up in the window on the
right. All it's says at the top of the window is "There are no items to
show in this view" If we use Enterprise Manager on the server, we can
view the Locks / Process ID. We can view both, Process Info and Locks /
Object from the workstations and server, just not the Locks / Process
ID. We used to, but I don't know what changed. I'm thinking it might
have to do with upgrading to XP SP2, or a Windows update, but I'm not
sure.
Has anyone out there experienced this? Or does anyone know the
solution?
Thanks,
MarkHave you tried reinstalling the Client tools on Affected boxes. Also if you
could start the profiler trace in the background and check if its running
any queries.
HTH
Vishal|||Vishal Gandhi wrote:
> Have you tried reinstalling the Client tools on Affected boxes. Also if yo
u
> could start the profiler trace in the background and check if its running
> any queries.
> HTH
> Vishal
I have tried reinstalling the client tools. I even installed them on a
new PC. Same results. I don't know much about SQL, I did start the
profiler and it was capturing data. I'm not sure what you mean by
running it in the background and see if it is running any queries.
Thanks,
Mark|||Vishal Gandhi wrote:
> Have you tried reinstalling the Client tools on Affected boxes. Also if yo
u
> could start the profiler trace in the background and check if its running
> any queries.
> HTH
> Vishal
I have tried reinstalling the client tools. I even installed them on a
new PC. Same results. I don't know much about SQL, I did start the
profiler and it was capturing data. I'm not sure what you mean by
running it in the background and see if it is running any queries.
Thanks,
Mark

Can't view Locks / Process ID

Hi,
We have SQL 7 running on Windows 2000 Server. For some reason we are
unable to view Locks / Process ID from workstations running Windows XP
SP2 with Enterprise Manager. Nothing shows up in the window on the
right. All it's says at the top of the window is "There are no items to
show in this view" If we use Enterprise Manager on the server, we can
view the Locks / Process ID. We can view both, Process Info and Locks /
Object from the workstations and server, just not the Locks / Process
ID. We used to, but I don't know what changed. I'm thinking it might
have to do with upgrading to XP SP2, or a Windows update, but I'm not
sure.
Has anyone out there experienced this? Or does anyone know the
solution?
Thanks,
MarkHave you tried reinstalling the Client tools on Affected boxes. Also if you
could start the profiler trace in the background and check if its running
any queries.
HTH
Vishal|||Vishal Gandhi wrote:
> Have you tried reinstalling the Client tools on Affected boxes. Also if you
> could start the profiler trace in the background and check if its running
> any queries.
> HTH
> Vishal
I have tried reinstalling the client tools. I even installed them on a
new PC. Same results. I don't know much about SQL, I did start the
profiler and it was capturing data. I'm not sure what you mean by
running it in the background and see if it is running any queries.
Thanks,
Mark|||Vishal Gandhi wrote:
> Have you tried reinstalling the Client tools on Affected boxes. Also if you
> could start the profiler trace in the background and check if its running
> any queries.
> HTH
> Vishal
I have tried reinstalling the client tools. I even installed them on a
new PC. Same results. I don't know much about SQL, I did start the
profiler and it was capturing data. I'm not sure what you mean by
running it in the background and see if it is running any queries.
Thanks,
Mark

Cant view Locks / Process ID

Hi,

We have SQL 7 running on Windows 2000 Server. For some reason we are
unable to view Locks / Process ID from workstations running Windows XP
SP2 with Enterprise Manager. Nothing shows up in the window on the
right. All it's says at the top of the window is "There are no items to
show in this view" If we use Enterprise Manager on the server, we can
view the Locks / Process ID. We can view both, Process Info and Locks /
Object from the workstations and server, just not the Locks / Process
ID. We used to, but I don't know what changed. I'm thinking it might
have to do with upgrading to XP SP2, or a Windows update, but I'm not
sure.

Has anyone out there experienced this? Or does anyone know the
solution?

Thanks,
Mark(mfanny@.gmail.com) writes:
> We have SQL 7 running on Windows 2000 Server. For some reason we are
> unable to view Locks / Process ID from workstations running Windows XP
> SP2 with Enterprise Manager. Nothing shows up in the window on the
> right. All it's says at the top of the window is "There are no items to
> show in this view" If we use Enterprise Manager on the server, we can
> view the Locks / Process ID. We can view both, Process Info and Locks /
> Object from the workstations and server, just not the Locks / Process
> ID. We used to, but I don't know what changed. I'm thinking it might
> have to do with upgrading to XP SP2, or a Windows update, but I'm not
> sure.

I find it a bit difficult to believe that Windows XP SP2 would matter,
at least when it comes to the communication with SQL Server. But maybe
some interaction with the MMC has broken.

If you use any Profiler, can you detect wether Locks / ProcessID generate
any calls to SQL Server?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Can't use system DSN to log user on

HI,
I have attempted to connect a user to a SQL 2000 server, running on a
Windows 2000 server using Windows Authentication and always get the
follwoing error message:
Connection failed
SQLstate:'28000'
sql server error: 18456
[microsoft][odbc sql server driver][sql server] login
failed for user "Domain\user1"
Can anyone explain to me why this is happening? I've looked at the
SQL Server Agent Properties and on the Connection tab it specifies use
Windows Authentication, but yet I can't get any Domain user to connect
to the server?!
Thanks,
Art
Hi,
You have to give that domain user to authenticate to SQL Server.
1. Login to SQL Server using Query analyzer with a user with sysadmin role
2. Execute the below commmands:-
sp_grantlogin '[domainname\Groupname]'
eg:
EXEC sp_grantlogin '[Finance\RPTGROUP]'
Command to give access previlage to the user to database.
sp_grantdbaccess '[domainname\Groupname]','user_name_in_database'
Eg:
use dbname
go
EXEC sp_grantdbaccess '[Finance\RPTGROUP]','RPTGROUP'
After this login to domain user and tr to create the system DSN.
Thanks
Hari
MCDBA
"Art Billings" <abillings@.principle-tech.com> wrote in message
news:8c11e0tjdn66knipdut4te4vnb92e8gbtj@.4ax.com...
> HI,
> I have attempted to connect a user to a SQL 2000 server, running on a
> Windows 2000 server using Windows Authentication and always get the
> follwoing error message:
> Connection failed
> SQLstate:'28000'
> sql server error: 18456
> [microsoft][odbc sql server driver][sql server] login
> failed for user "Domain\user1"
> Can anyone explain to me why this is happening? I've looked at the
> SQL Server Agent Properties and on the Connection tab it specifies use
> Windows Authentication, but yet I can't get any Domain user to connect
> to the server?!
> Thanks,
> Art
|||Thanks for the response to my query. Didn't expect one, so that was a
pleasant surprise. We worked it out, turns out that the Domain Users
group had not been given expicit access to any of the databases. Once
we configured that, then allowed them public access and execute rights
on the stored procedure we were developing, everything worked as smooth
as silk. Imagine that!!
Thanks again!
Art
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

Can't use system DSN to log user on

HI,
I have attempted to connect a user to a SQL 2000 server, running on a
Windows 2000 server using Windows Authentication and always get the
follwoing error message:
Connection failed
SQLstate:'28000'
sql server error: 18456
[microsoft][odbc sql server driver][sql server] login
failed for user "Domain\user1"
Can anyone explain to me why this is happening? I've looked at the
SQL Server Agent Properties and on the Connection tab it specifies use
Windows Authentication, but yet I can't get any Domain user to connect
to the server'!
Thanks,
ArtHi,
You have to give that domain user to authenticate to SQL Server.
1. Login to SQL Server using Query analyzer with a user with sysadmin role
2. Execute the below commmands:-
sp_grantlogin '[domainname\Groupname]'
eg:
EXEC sp_grantlogin '[Finance\RPTGROUP]'
Command to give access previlage to the user to database.
sp_grantdbaccess '& #91;domainname\Groupname]','user_name_in
_database'
Eg:
use dbname
go
EXEC sp_grantdbaccess '[Finance\RPTGROUP]','RPTGROUP'
After this login to domain user and tr to create the system DSN.
Thanks
Hari
MCDBA
"Art Billings" <abillings@.principle-tech.com> wrote in message
news:8c11e0tjdn66knipdut4te4vnb92e8gbtj@.
4ax.com...
> HI,
> I have attempted to connect a user to a SQL 2000 server, running on a
> Windows 2000 server using Windows Authentication and always get the
> follwoing error message:
> Connection failed
> SQLstate:'28000'
> sql server error: 18456
> [microsoft][odbc sql server driver][sql server] login
> failed for user "Domain\user1"
> Can anyone explain to me why this is happening? I've looked at the
> SQL Server Agent Properties and on the Connection tab it specifies use
> Windows Authentication, but yet I can't get any Domain user to connect
> to the server'!
> Thanks,
> Art|||Thanks for the response to my query. Didn't expect one, so that was a
pleasant surprise. We worked it out, turns out that the Domain Users
group had not been given expicit access to any of the databases. Once
we configured that, then allowed them public access and execute rights
on the stored procedure we were developing, everything worked as smooth
as silk. Imagine that!!
Thanks again!
Art
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

Can't upgrade sql server 2000 from professional to standard edition.

Hello Members,
I by accident installed SQL server 2000 personal edition
on a Windows 2000 server. I want to upgrade it to
standard edition to allow for more threads and users.
When i put in the standard cd and get to the upgrade
screen, the option for upgrade is grade out and I can't
click it.
Does anybody know why this happens and what I can do to
upgrade to the standard edition.
Regards,
Bill Gianoukos.
PS.. please also feel free to email me responses to
billg@.otpas.com>--Original Message--
>Hello Members,
>
>I by accident installed SQL server 2000 personal edition
>on a Windows 2000 server. I want to upgrade it to
>standard edition to allow for more threads and users.
>When i put in the standard cd and get to the upgrade
>screen, the option for upgrade is grade out and I can't
>click it.
>Does anybody know why this happens and what I can do to
>upgrade to the standard edition.
>Regards,
>Bill Gianoukos.
>PS.. please also feel free to email me responses to
>billg@.otpas.com
>.
>
You can not easily upgrade, install new instance and
migrate database over.|||Hi,
Not sure what you meant by " You can not easily upgrade".It *is* possible to
upgrade pers edition to std edition.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
<anonymous@.discussions.microsoft.com> wrote in message
news:c4d601c43864$cb6cd990$a301280a@.phx.gbl...
> >--Original Message--
> >Hello Members,
> >
> >
> >I by accident installed SQL server 2000 personal edition
> >on a Windows 2000 server. I want to upgrade it to
> >standard edition to allow for more threads and users.
> >When i put in the standard cd and get to the upgrade
> >screen, the option for upgrade is grade out and I can't
> >click it.
> >
> >Does anybody know why this happens and what I can do to
> >upgrade to the standard edition.
> >
> >Regards,
> >Bill Gianoukos.
> >
> >PS.. please also feel free to email me responses to
> >billg@.otpas.com
> >
> >.
> >
> You can not easily upgrade, install new instance and
> migrate database over.|||Bill,
I dont know why the upgrade option is grayed out in this case.Did you check
the log files for any hints/error messages?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Bill Gianoukos" <anonymous@.discussions.microsoft.com> wrote in message
news:c20f01c4384c$ef1ece60$a601280a@.phx.gbl...
> Hello Members,
>
> I by accident installed SQL server 2000 personal edition
> on a Windows 2000 server. I want to upgrade it to
> standard edition to allow for more threads and users.
> When i put in the standard cd and get to the upgrade
> screen, the option for upgrade is grade out and I can't
> click it.
> Does anybody know why this happens and what I can do to
> upgrade to the standard edition.
> Regards,
> Bill Gianoukos.
> PS.. please also feel free to email me responses to
> billg@.otpas.com
>

Can't upgrade sql server 2000 from professional to standard edition.

>--Original Message--
>Hello Members,
>
>I by accident installed SQL server 2000 personal edition
>on a Windows 2000 server. I want to upgrade it to
>standard edition to allow for more threads and users.
>When i put in the standard cd and get to the upgrade
>screen, the option for upgrade is grade out and I can't
>click it.
>Does anybody know why this happens and what I can do to
>upgrade to the standard edition.
>Regards,
>Bill Gianoukos.
>PS.. please also feel free to email me responses to
>billg@.otpas.com
>.
>
You can not easily upgrade, install new instance and
migrate database over.Hi,
Not sure what you meant by " You can not easily upgrade".It *is* possible to
upgrade pers edition to std edition.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
<anonymous@.discussions.microsoft.com> wrote in message
news:c4d601c43864$cb6cd990$a301280a@.phx.gbl...
>
> You can not easily upgrade, install new instance and
> migrate database over.

Can't upgrade sql server 2000 from professional to standard edition.

Hello Members,
I by accident installed SQL server 2000 personal edition
on a Windows 2000 server. I want to upgrade it to
standard edition to allow for more threads and users.
When i put in the standard cd and get to the upgrade
screen, the option for upgrade is grade out and I can't
click it.
Does anybody know why this happens and what I can do to
upgrade to the standard edition.
Regards,
Bill Gianoukos.
PS.. please also feel free to email me responses to
billg@.otpas.comBill,
I dont know why the upgrade option is grayed out in this case.Did you check
the log files for any hints/error messages?
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Bill Gianoukos" <anonymous@.discussions.microsoft.com> wrote in message
news:c20f01c4384c$ef1ece60$a601280a@.phx.gbl...
> Hello Members,
>
> I by accident installed SQL server 2000 personal edition
> on a Windows 2000 server. I want to upgrade it to
> standard edition to allow for more threads and users.
> When i put in the standard cd and get to the upgrade
> screen, the option for upgrade is grade out and I can't
> click it.
> Does anybody know why this happens and what I can do to
> upgrade to the standard edition.
> Regards,
> Bill Gianoukos.
> PS.. please also feel free to email me responses to
> billg@.otpas.com
>

Can't upgrade sql server 2000 from professional to standard edition.

Hello Members,
I by accident installed SQL server 2000 personal edition
on a Windows 2000 server. I want to upgrade it to
standard edition to allow for more threads and users.
When i put in the standard cd and get to the upgrade
screen, the option for upgrade is grade out and I can't
click it.
Does anybody know why this happens and what I can do to
upgrade to the standard edition.
Regards,
Bill Gianoukos.
PS.. please also feel free to email me responses to
billg@.otpas.com
Bill,
I dont know why the upgrade option is grayed out in this case.Did you check
the log files for any hints/error messages?
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Bill Gianoukos" <anonymous@.discussions.microsoft.com> wrote in message
news:c20f01c4384c$ef1ece60$a601280a@.phx.gbl...
> Hello Members,
>
> I by accident installed SQL server 2000 personal edition
> on a Windows 2000 server. I want to upgrade it to
> standard edition to allow for more threads and users.
> When i put in the standard cd and get to the upgrade
> screen, the option for upgrade is grade out and I can't
> click it.
> Does anybody know why this happens and what I can do to
> upgrade to the standard edition.
> Regards,
> Bill Gianoukos.
> PS.. please also feel free to email me responses to
> billg@.otpas.com
>

Can't upgrade sql server 2000 from professional to standard edition.

>--Original Message--
>Hello Members,
>
>I by accident installed SQL server 2000 personal edition
>on a Windows 2000 server. I want to upgrade it to
>standard edition to allow for more threads and users.
>When i put in the standard cd and get to the upgrade
>screen, the option for upgrade is grade out and I can't
>click it.
>Does anybody know why this happens and what I can do to
>upgrade to the standard edition.
>Regards,
>Bill Gianoukos.
>PS.. please also feel free to email me responses to
>billg@.otpas.com
>.
>
You can not easily upgrade, install new instance and
migrate database over.
Hi,
Not sure what you meant by " You can not easily upgrade".It *is* possible to
upgrade pers edition to std edition.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
<anonymous@.discussions.microsoft.com> wrote in message
news:c4d601c43864$cb6cd990$a301280a@.phx.gbl...
> You can not easily upgrade, install new instance and
> migrate database over.

Can't uninstall Analysis Services 2000

I have both SQL 2000 and SQL 2005 on my computer. I am running Windows XP Pro, SP2. SQL 2000 was installed first, then, 3 months later, SQL 2005 was installed, too.

My client needs me to work with SQL 2000 Analysis Services (my client is on a SQL 2K platform). I have the full SQL 2005 Developer Edition on my machine, along with the SQL 2005 Analysis Services, SSIS, Visual Studio, SSMS, etc. I also have SQL 2000 Developer Edition, but I don't see SQL 2000 Analysis Services on the machine nor running under services. In addition, there is no Analysis Services on my machine.

Therefore, I wanted to install SQL 2000 Analysis services onto my machine. However, when I do, I get the message:
"To install a new version of Analysis Services, you must first remove your existing version."

However, I cannot uninstall Analysis Services. It does not show up under Add/Remove New Programs in Control Panel. There is no MSSQLServerOLAPService service running. I do have a two Analysis Service services running with other names: BUCKNOFF2005 (which is, obviously, my 2005 Analysis Services) and MSSQLSERVER, which also displays in my SQL 2000 SQL Server Service Manager, so there might be some artifacts from an old install of SQL 2000 Analysis on my machine.

SQL 2005 Analysis Services runs fine, by the way.

So I am stuck. I can neither install nor uninstall. Bottom line, how can I uninstall SQL 2000 Analysis Services (without reformatting my hard drive or starting over again on another computer)? If I can do that, then I can reinstall it. Right now, as a temporary solution, I borrowed a laptop from my client and installed Analysis Services 2000 for the 2 days that I will be working with it -- but I need to get this fixed on my own laptop which I take from client to client.

AS 2000 should have separate entry in Add/Remove programs "Microsoft SQL Server 2000 Analysis Services".

If you dont have the entry, you dont have AS2000 installed on your machine.

Now about installing AS2000 on top AS2005.

You can try uninstalling SQL Server 2005 from your machine, installing AS2000 and then installing SQL 2005 back into the same configuration.

It is bit of the hassle, but looks like your are trying to fit pretty custom configuration into your laptop and you might need to work a bit harder to get there.

Hope that helps.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Hi,

Microsoft should warn people about this kind of things!!! It is completly ilogic and in terms of development it's a ***.

Best Regards

Jo?o Marto