Count records when RecordSource is a Stored Procedure

I have a stored procedure named mySP that looks basically like this:
Select Field1, Field2
From tblMyTable
Where Field 3 = 'xyz'

What I do is to populate an Access form:
DoCmd.Openform "frmMyFormName"
Forms!myFormName.RecordSource = "mySP"

What I want to do in VBA is to open frmContinuous(a datasheet form) if
mySP returns more than one record or open frmDetail if mySP returns
only one record.

I'm stumped as to how to accomplish this, without running mySP twice:
once to count it and once to use it as a recordsource.
Thanks,
lq"Lauren Quantrell" <laurenquantrell@.hotmail.com> wrote in message
news:47e5bd72.0404260611.33a36012@.posting.google.c om...
> I have a stored procedure named mySP that looks basically like this:
> Select Field1, Field2
> From tblMyTable
> Where Field 3 = 'xyz'
> What I do is to populate an Access form:
> DoCmd.Openform "frmMyFormName"
> Forms!myFormName.RecordSource = "mySP"
> What I want to do in VBA is to open frmContinuous(a datasheet form) if
> mySP returns more than one record or open frmDetail if mySP returns
> only one record.
> I'm stumped as to how to accomplish this, without running mySP twice:
> once to count it and once to use it as a recordsource.
> Thanks,
> lq

I don't know much about VBA, but if you return the results of the procedure
in an ADO RecordSet object, then you should be able to count the rows on the
client side, and format the data accordingly. You might get a better answer
in an Access newsgroup, though.

Simon

Couldn't call a procedure

Hi,
I am using MSSQL-2000. I couldn't call a procedure from a client (windows
98) but its working fine when i call it from window2000 system.
What is the reason for this?
Thanks,
SouraHi,
This will not happen. Even from client you are loging into SQL Server
machine using some tools.
Could you please exactly say how you are calling the procedure.
Thanks
Hari
SQL SERVER MVP
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:0F6D09C0-7057-4651-AEFF-A18C73691659@.microsoft.com...
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>|||Hi
Please tell us what is the authentication that u are using.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"SouRa" wrote:
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>

Couldn't call a procedure

Hi,
I am using MSSQL-2000. I couldn't call a procedure from a client (windows
98) but its working fine when i call it from window2000 system.
What is the reason for this?
Thanks,
SouraHi,
This will not happen. Even from client you are loging into SQL Server
machine using some tools.
Could you please exactly say how you are calling the procedure.
Thanks
Hari
SQL SERVER MVP
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:0F6D09C0-7057-4651-AEFF-A18C73691659@.microsoft.com...
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>|||Hi
Please tell us what is the authentication that u are using.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"SouRa" wrote:

> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>

Couldn't call a procedure

Hi,
I am using MSSQL-2000. I couldn't call a procedure from a client (windows
98) but its working fine when i call it from window2000 system.
What is the reason for this?
Thanks,
Soura
Hi,
This will not happen. Even from client you are loging into SQL Server
machine using some tools.
Could you please exactly say how you are calling the procedure.
Thanks
Hari
SQL SERVER MVP
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:0F6D09C0-7057-4651-AEFF-A18C73691659@.microsoft.com...
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>
|||Hi
Please tell us what is the authentication that u are using.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
"SouRa" wrote:

> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>
sql

Could you write a special stored procedure for me in SQL 2005?

When I execute the SQL "select TagName from Th_TagTable where IDTopic=@.IDTopic" , it return several rows such as
TagName= http://www.hothelpdesk.com

TagName= http://www.hellocw.com
TagName= http://www.supercoolbookmark.com

I hope there is a stored procedure which can join all TagName into a single string and return,
it means when I pass @.IDTopic to the stored procedure, it return "http://www.hothelpdesk.com, http://www.hellocw.com, http://www.supercoolbookmark.com"

How can write the stored procedure?

The best answer to this question is in this post: http://databases.aspfaq.com/general/how-do-i-concatenate-strings-from-a-column-into-a-single-row.html

If you are using 2005, be sure and use the FOR XML PATH solution. It does not have of the issues that the 2000 solutions did, unless you used a cursor (which is equally heinous

Could you write a special stored procedure for me in SQL 2005?

Could you write a special stored procedure for me in SQL 2005?

When I execute the SQL "select TagName from Th_TagTable whereIDTopic=@.IDTopic" , it return several rows such as
TagName= Sport
TagName= New
TagName= Health

I hope there is a stored procedure which can join all TagName into a single string and return,
it means when I pass @.IDTopic to the stored procedure, it return "Sport,New,Health"

How can write the stored procedure?

Hi,

You can use the below t-sql stateents to get the desired list of tagnames. COALESCE is the key of the below script

DECLARE @.IdTopic int
SET @.IdTopic = 1

DECLARE @.str AS nvarchar(255)

SELECT
@.str = COALESCE(@.str + ', ', '') + tagname
FROM Th_TagTable (NoLock)
WHERE IdTopic = @.IdTopic

SELECT @.str

You can better create a user-defined function instead of a stored procedure to get similar values.

Check the article and sample athttp://kodyaz.com/articles/article.aspx?articleid=29 which gets the list of a book's authors.

Eralper

http://www.kodyaz.com

|||Thanks!

Could Stored Procedure or Trigger choose another database?

Hello all, I need some advice or clue here.
I want to crate a stored procedure or trigger from database A that will
change of have effect on another database B. Is this could be done? I
try to use sql syntax "use B;" in stored procedure that created on
database A, but it said that use syntax couldn't be used in stored
procedure."Lemune" <alfredosilitonga@.gmail.com> wrote in message
news:1147850181.634882.15120@.i39g2000cwa.googlegroups.com...
> Hello all, I need some advice or clue here.
> I want to crate a stored procedure or trigger from database A that will
> change of have effect on another database B. Is this could be done? I
> try to use sql syntax "use B;" in stored procedure that created on
> database A, but it said that use syntax couldn't be used in stored
> procedure.
>
Do you mean something like
create procedure FOO as
(
select * from bar
)
where bar is in a different database?
If so, 3-part names
select * from dbname.owner.table
so
create procedure FOO as
(
select * from baz.dbo.bar
)|||Lemune,
yes you can change the datbase context inside a stored procedure even
thought the "Use" keyword is not allowed.
One way is creating a string variable and build up the syntax you need,
when execute it through sp_executesql.
Declare @.myQuery nvarchar(2000)
set @.myQuery = ' USE ' + @.dbname + CHAR(13) + 'SELECT * from myTable'
Exec sp_executesql @.myQuery
Another option is symply using the 3 part name:
Select * from myDb.dbo.myTable
If you try to loop through all datbases on a server have a look at
sp_MSforeachDB. It gives you an easy way to run the same command on all
databases.
Markus|||Thanks for your information and MarkusB too, I try booth your method
and it work well.
But I have another problem, assume that I want to create stored
procedure that work from A.dbo.Incomming to check a value from
B.dbo.Data and than the result value is send to A.dbo.Outgoing in one
stored procedure. I'm using MS Sql Server 7. I also have read that in
MS SQL 2003 have stored functions that return value.|||I have another question, how stored procedure in SQL Server 7 could
return value (like function)?|||Inside the proc, you do:
RETURN -101
And the calling code, of TSQL:
DECLARE @.retval int
EXEC @.retval = myproc
Return codes are int only and should be used to communicate status (success
or fail). You can also
return values through output parameters:
CREATE PROC myproc @.parm varchar(5) OUT
AS
SET @.parm = 'Hello'
GO
DECLARE @.x varchar(5)
EXEC myproc @.parm = @.x OUT
Both return codes and out parameters can both be retrieved from your program
ming API (ADO.NET, for
example) as well.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Lemune" <alfredosilitonga@.gmail.com> wrote in message
news:1147948815.225334.130080@.i40g2000cwc.googlegroups.com...
>I have another question, how stored procedure in SQL Server 7 could
> return value (like function)?
>|||Thank you very much.|||I have another question again :-). Could Stored Procedure or Trigger
choose another database that is on difference engine? For example, I
have database A on engine or instance name Server1 that has a stored
procedure Stored_Proc_1 and in this stored procedure I want to access
some table on database B on engine Server2. I have username and
password on Server2.

Could Stored Procedure or Trigger choose another database?

Hello all, I need some advice or clue here.
I want to crate a stored procedure or trigger from database A that will
change of have effect on another database B. Is this could be done? I
try to use sql syntax "use B;" in stored procedure that created on
database A, but it said that use syntax couldn't be used in stored
procedure."Lemune" <alfredosilitonga@.gmail.com> wrote in message
news:1147850181.634882.15120@.i39g2000cwa.googlegroups.com...
> Hello all, I need some advice or clue here.
> I want to crate a stored procedure or trigger from database A that will
> change of have effect on another database B. Is this could be done? I
> try to use sql syntax "use B;" in stored procedure that created on
> database A, but it said that use syntax couldn't be used in stored
> procedure.
>
Do you mean something like
create procedure FOO as
(
select * from bar
)
where bar is in a different database?
If so, 3-part names
select * from dbname.owner.table
so
create procedure FOO as
(
select * from baz.dbo.bar
)|||Lemune,
yes you can change the datbase context inside a stored procedure even
thought the "Use" keyword is not allowed.
One way is creating a string variable and build up the syntax you need,
when execute it through sp_executesql.
Declare @.myQuery nvarchar(2000)
set @.myQuery = ' USE ' + @.dbname + CHAR(13) + 'SELECT * from myTable'
Exec sp_executesql @.myQuery
Another option is symply using the 3 part name:
Select * from myDb.dbo.myTable
If you try to loop through all datbases on a server have a look at
sp_MSforeachDB. It gives you an easy way to run the same command on all
databases.
Markus|||Thanks for your information and MarkusB too, I try booth your method
and it work well.
But I have another problem, assume that I want to create stored
procedure that work from A.dbo.Incomming to check a value from
B.dbo.Data and than the result value is send to A.dbo.Outgoing in one
stored procedure. I'm using MS Sql Server 7. I also have read that in
MS SQL 2003 have stored functions that return value.|||I have another question, how stored procedure in SQL Server 7 could
return value (like function)?|||Inside the proc, you do:
RETURN -101
And the calling code, of TSQL:
DECLARE @.retval int
EXEC @.retval = myproc
Return codes are int only and should be used to communicate status (success or fail). You can also
return values through output parameters:
CREATE PROC myproc @.parm varchar(5) OUT
AS
SET @.parm = 'Hello'
GO
DECLARE @.x varchar(5)
EXEC myproc @.parm = @.x OUT
Both return codes and out parameters can both be retrieved from your programming API (ADO.NET, for
example) as well.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Lemune" <alfredosilitonga@.gmail.com> wrote in message
news:1147948815.225334.130080@.i40g2000cwc.googlegroups.com...
>I have another question, how stored procedure in SQL Server 7 could
> return value (like function)?
>|||Thank you very much.|||I have another question again :-). Could Stored Procedure or Trigger
choose another database that is on difference engine? For example, I
have database A on engine or instance name Server1 that has a stored
procedure Stored_Proc_1 and in this stored procedure I want to access
some table on database B on engine Server2. I have username and
password on Server2.

Could Stored Procedure or Trigger choose another database on difference engine?

Could Stored Procedure or Trigger
choose another database that is on difference engine? For example, I
have database A on engine or instance name Server1 that has a stored
procedure Stored_Proc_1 and in this stored procedure I want to access
some table on database B on engine Server2. I have username and
password on Server2.
I know that we can access different database on the same engine or
instance name, using to methods:
1. Using 3-part names ex: on the sp we say Select * from
myDb.dbo.myTable
2. Creating a string variable and build up the syntax that needed, ex:
Declare @.myQuery nvarchar(2000)
set @.myQuery = ' USE ' + @.dbname + CHAR(13) + 'SELECT * from
myTable'
Exec sp_executesql @.myQueryHi Lemune,
You can configure a linked server and then use 4 part name to access objects
on a different server.
Server_Name.DB_Name.Schema.Object
Note that there is a lot more overhead involved in this type of query
(distributed query) than accessing objects in DBs on the same server
instance.
Look in Books On Line for "Configuring linked servers"
HTH
Ami
"Lemune" <alfredosilitonga@.gmail.com> wrote in message
news:1148281973.632093.46050@.i39g2000cwa.googlegroups.com...
> Could Stored Procedure or Trigger
> choose another database that is on difference engine? For example, I
> have database A on engine or instance name Server1 that has a stored
> procedure Stored_Proc_1 and in this stored procedure I want to access
> some table on database B on engine Server2. I have username and
> password on Server2.
> I know that we can access different database on the same engine or
> instance name, using to methods:
> 1. Using 3-part names ex: on the sp we say Select * from
> myDb.dbo.myTable
> 2. Creating a string variable and build up the syntax that needed, ex:
> Declare @.myQuery nvarchar(2000)
> set @.myQuery = ' USE ' + @.dbname + CHAR(13) + 'SELECT * from
> myTable'
> Exec sp_executesql @.myQuery
>|||This problem occur because I develop a program for sms services. My
program use database to store incoming massage and out massage, If the
massage is having the right keyword it will do some task. And the task
is involved with another database. If according to myself I would
rather make my database on my client database (just adding my table to
my client database) or maybe adding my database to my client database
engine. But for some reason, my client refuses that method. So, I have
so make stored procedure on my program database engine that will
connect to my client database. I use this method so that I don't have
to change my program code each time my client use that rule :-).

Could not locate entry in sysdatabases for database 'MYSQL

Hi
I am trying to run a stored procedure on a linked MySQL server
i can select from the MySQL server, so i know that there is a valid
link
i can run the stored procedure on the MySQL server using the command
call triodent.UpdateDownloadTable
but when i try to execute
exec MYSQL.triodent.UpdateDownloadTable
i get the "could not locate..." error
is it because MySQL is using call rather than exec? if so doesn't
anyone have an idea for the syntax?
many Thanks
Ian
Try
exec MYSQL.triodent..UpdateDownloadTable
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
<ian.tiesdell@.hotmail.co.uk> wrote in message
news:9f6c966a-b884-4efe-b037-2b339fb5d236@.q1g2000prf.googlegroups.com...
> Hi
> I am trying to run a stored procedure on a linked MySQL server
> i can select from the MySQL server, so i know that there is a valid
> link
> i can run the stored procedure on the MySQL server using the command
> call triodent.UpdateDownloadTable
> but when i try to execute
> exec MYSQL.triodent.UpdateDownloadTable
> i get the "could not locate..." error
> is it because MySQL is using call rather than exec? if so doesn't
> anyone have an idea for the syntax?
> many Thanks
> Ian
|||thanks jason but i get
Msg 7212, Level 17, State 1, Line 3
Could not execute procedure 'UpdateDownloadTable' on remote server
'MYSQL'.
:-(
|||That's progress. It sounds like it is permissions now. Verify the linked
server user has the rights to execute on MySQL.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
<ian.tiesdell@.hotmail.co.uk> wrote in message
news:f098afcc-03ba-4977-9698-f38b83f34499@.b9g2000prh.googlegroups.com...
> thanks jason but i get
> Msg 7212, Level 17, State 1, Line 3
> Could not execute procedure 'UpdateDownloadTable' on remote server
> 'MYSQL'.
> :-(
|||jason wrote:
> That's progress. It sounds like it is permissions now. Verify the linked
> server user has the rights to execute on MySQL.
>
Also check the properties for the linked server and verify RPC is turned on.
|||sorry to be dim but how do i check this?
i've looked at server objects/linked servers security settings and i
have
connections will be made using this security context
remote login root
with password and then the password
RPC is turned on
Data Access is True
Ian
|||ian.tiesdell@.hotmail.co.uk wrote:
> sorry to be dim but how do i check this?
> i've looked at server objects/linked servers security settings and i
> have
> connections will be made using this security context
> remote login root
> with password and then the password
> RPC is turned on
> Data Access is True
> Ian
Well, if you looked at the linked server properties and saw the RPC is
enabled (there are two options), then that is all you need to do.
Jeff
|||so if the security settings are Ok and the syntax is OK?
what else could be wrong?
using
exec MYSQL.triodent..UpdateDownloadTable
Msg 7212, Level 17, State 1, Line 1
Could not execute procedure 'UpdateDownloadTable' on remote server
'MYSQL'
|||ian.tiesdell@.hotmail.co.uk wrote:
> so if the security settings are Ok and the syntax is OK?
> what else could be wrong?
> using
> exec MYSQL.triodent..UpdateDownloadTable
> Msg 7212, Level 17, State 1, Line 1
> Could not execute procedure 'UpdateDownloadTable' on remote server
> 'MYSQL'
Only thing I can think of is maybe permission issues in 'MYSQL'? I
don't know 'MYSQL' - so I really can't help with that side.
|||I think it could be mySQL causing the problem - what i've done is to
mimic the actions of the stored proc using update statements from
MSSQL over to the linked server
thanks for your input
Ian

Could not locate entry in sysdatabases for database 'MYSQL

Hi
I am trying to run a stored procedure on a linked MySQL server
i can select from the MySQL server, so i know that there is a valid
link
i can run the stored procedure on the MySQL server using the command
call triodent.UpdateDownloadTable
but when i try to execute
exec MYSQL.triodent.UpdateDownloadTable
i get the "could not locate..." error
is it because MySQL is using call rather than exec? if so doesn't
anyone have an idea for the syntax?
many Thanks
IanTry
exec MYSQL.triodent..UpdateDownloadTable
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
<ian.tiesdell@.hotmail.co.uk> wrote in message
news:9f6c966a-b884-4efe-b037-2b339fb5d236@.q1g2000prf.googlegroups.com...
> Hi
> I am trying to run a stored procedure on a linked MySQL server
> i can select from the MySQL server, so i know that there is a valid
> link
> i can run the stored procedure on the MySQL server using the command
> call triodent.UpdateDownloadTable
> but when i try to execute
> exec MYSQL.triodent.UpdateDownloadTable
> i get the "could not locate..." error
> is it because MySQL is using call rather than exec? if so doesn't
> anyone have an idea for the syntax?
> many Thanks
> Ian|||thanks jason but i get
Msg 7212, Level 17, State 1, Line 3
Could not execute procedure 'UpdateDownloadTable' on remote server
'MYSQL'.
:-(|||That's progress. It sounds like it is permissions now. Verify the linked
server user has the rights to execute on MySQL.
--
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
<ian.tiesdell@.hotmail.co.uk> wrote in message
news:f098afcc-03ba-4977-9698-f38b83f34499@.b9g2000prh.googlegroups.com...
> thanks jason but i get
> Msg 7212, Level 17, State 1, Line 3
> Could not execute procedure 'UpdateDownloadTable' on remote server
> 'MYSQL'.
> :-(|||jason wrote:
> That's progress. It sounds like it is permissions now. Verify the linked
> server user has the rights to execute on MySQL.
>
Also check the properties for the linked server and verify RPC is turned on.|||sorry to be dim but how do i check this?
i've looked at server objects/linked servers security settings and i
have
connections will be made using this security context
remote login root
with password and then the password
RPC is turned on
Data Access is True
Ian|||ian.tiesdell@.hotmail.co.uk wrote:
> sorry to be dim but how do i check this?
> i've looked at server objects/linked servers security settings and i
> have
> connections will be made using this security context
> remote login root
> with password and then the password
> RPC is turned on
> Data Access is True
> Ian
Well, if you looked at the linked server properties and saw the RPC is
enabled (there are two options), then that is all you need to do.
Jeff|||so if the security settings are Ok and the syntax is OK?
what else could be wrong?
using
exec MYSQL.triodent..UpdateDownloadTable
Msg 7212, Level 17, State 1, Line 1
Could not execute procedure 'UpdateDownloadTable' on remote server
'MYSQL'|||ian.tiesdell@.hotmail.co.uk wrote:
> so if the security settings are Ok and the syntax is OK?
> what else could be wrong?
> using
> exec MYSQL.triodent..UpdateDownloadTable
> Msg 7212, Level 17, State 1, Line 1
> Could not execute procedure 'UpdateDownloadTable' on remote server
> 'MYSQL'
Only thing I can think of is maybe permission issues in 'MYSQL'? I
don't know 'MYSQL' - so I really can't help with that side.|||I think it could be mySQL causing the problem - what i've done is to
mimic the actions of the stored proc using update statements from
MSSQL over to the linked server
thanks for your input
Ian

Could not locate entry (stored procedure error)

hello everyone,

I am using VS 2005 and sql server 2000. I have a web application which uses a connectionstring with a user id and pwd. Everything is fine, I can execute normal sql statements from the code behind. I cannot execute a stored procedure...I get this error.

Could not locate entry in sysdatabases for database 'exec usp_add2DB (my parameters are included here, deleted for simplicity reasons)

No entry found with that name. Make sure that the name is entered correctly.

I have given execute permission for the user, and the name of the storedproc is correct. the name of the server is also correct...pls pls help me what is wrong here...

Post the code you have and someone here can help.|||

Thank you for the response.here is the code...shortened for simplicity sake.

BtnClick event:

string sql = exec sp_add2DB '" + tShiptoSiteNo.Text +"','" txtShipToSiteName.Text

ClassA a = new ClassA("dev_connectionstr");

if(a.ExecuteSP(sql))

{

Response.Write("executed");

}

I am using enterprise library 2.0: (Everything is set up properly,pretty confident about it ,because many apps i am using it).

In Class A:

public class A :BaseDAO

{

public bool ExecuteSP(string sql)
{
DbCommand dbCommand = SqlDatabase.GetStoredProcCommand(sql);

int a = SqlDatabase.ExecuteNonQuery(dbCommand);
return true;}

In web.config:

<connectionStrings>
<add name ="dev_connectionstr" connectionString ="Data Source=ServerName;Initial Catalog=TestDB;User ID=test_user;Password=xxxx" providerName ="System.Data.SqlClient"/>
</connectionStrings>

Thanks for the help.

|||

Hi sankar,

When executing a stored procedure, you cannot list your parameters after the stored procedure name and execute with EXEC.

You need to create a SqlCommand object, and make CommandText as "sp_add2DB". Then use SqlCommand.Parameters.Add() method to add the parameters one by one. After this is done, open the connection and call SqlCommand.ExecuteNonQuery to execute it.

|||Thanks a lot for the reply Kevin Yu....tht explains why! Thank you very much!.

Could not get the column information from the OLE DB provider IBMDA400

Hello

I'm trying to get data from as400 server to sql server, trough a job.
The job executes a stored procedure that retrieves data from a view in an other database on the same server. That view gets the data from as400.
Now, when i run the mentioned stored procedure in the query analyzer, everything works fine, but when the stored procedure is executed from the scheduled job, it fails each time giving the error

"Could not get the column information from the OLE DB provider 'IBMDA400'. [SQLSTATE 42000] (Error 7350). The step failed."

on random points during that process (by that i mean the lenght of time it runs)

does anyone know what the diffrence is between executing an sp in query analyzer or using a job, keeping in mind retrieving data from as400?

thanksSQLAgent service account should have the same permissions as yours. If you're piping data from AS/400 using linked server, make sure mapping entry exists for SQLAgent account as well.

Could not find xp_sqlagent_proxy_account

Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
> > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > account. It says successfully, but I cannot find any local account
> > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > Have you tried changing this from the Services applet?
> >
> > John
> >
> > "Min" wrote:
> >
> > > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > > account. It says successfully, but I cannot find any local account
> > > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > I don't have a SQL 7 system to check, but the if you can't find the stored
> > procedure in the master database using Enterprise Manager, then it was either
> > deleted for security or does not exist in that version.
> >
> > The local users are accessed through the Server applet in control panel. The
> > services applet in control panel will allow you to select a different user
> > for the service to be run as.
> >
> > John|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
John
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> >
> > If the machine is NT workstation you can manage local users using
> > musrmgr.exe but this is not available on NT Server.
> >
> > What account is the service running under in the services applet? Usually
> > the account would be a domain user with restricted privileges.|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via SQLMonster.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>|||Thanks. I guess my question now is really:
How can I create a proxy account correctly? Thru EM, I unchecked the box,
clicked "reset ..." and message came back saying " successfully". But I am
still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
non-admin account.
Also, there is no utility on NT server to verify the account.
"John Bell" wrote:
> Hi
> See inline:
> "Min" wrote:
> > So is it right for SQL Server 7, the only way to reset proxy account is thru
> > EM, not programatically?
> Probably but I don't have a system to check this. There may be a way to
> write your own process to do this, but whether this is a justified effort for
> a version of the product that is so old, I don't know. You may want to trace
> what happens when you use EM and see what if you can do the same.
> >
> > Does it mean for NT Server, there is no way I can check to verify if the
> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
> > the "reset proxy" account button in "Job System", it says "successfully" but
> > there is an error log entry for agent says "SQLAgentCmdExec password
> > verification failed, required client privilege not held".
> Is there anything in the Event log?
> >
> > We use a domain acount for both SQL and Agent services. It is in local
> > administrator group.
> You may also want to check:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
> John
> >
> > Thanks again!
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> > >
> > > If the machine is NT workstation you can manage local users using
> > > musrmgr.exe but this is not available on NT Server.
> > >
> > > What account is the service running under in the services applet? Usually
> > > the account would be a domain user with restricted privileges.|||Yes...use Enterprise Manager and the Reset Proxy on the Job
System tab in SQL Agent Properties. Refer to the following
for more info:
INF: Reset Proxy and the SQLAgentCmdExec Account
http://support.microsoft.com/?id=264155
But your issues are likely related to the service account,
not the proxy account. In regards to the 1314 error, that's
generally related to rights of the MSSQLServer service
account, *not* the proxy account. So it's that account that
is missing the rights of either/both Act as part of
operating system and increase quotas. You could also be
missing Replace process level token based on some of what
you posted earlier. I'm pretty sure there is a Knowledge
base article on this somewhere.
Sounds like you have some issues with the MSSQLServer
service account and that you may have changed it through the
services applet instead of Enterprise Manager. If you change
the service account through Enterprise Manager, the
permissions and rights will be set correctly.
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Okay...and right after I posted, I found the other KB
article I mentioned that has more info on error 1314:
PRB: Error 1314 Raised By xp_cmdshell When Executed as
Non-SA User
http://support.microsoft.com/?id=248391
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Thanks ... I have tried to follow both articles (actually almost every
article online that I can dig out). It is still not working even though EM
says "successfully". I decided to use another technology instead of
XP_cmdshell. My guess is that some kind of security patches blocked it.
"Sue Hoegemeier" wrote:
> Okay...and right after I posted, I found the other KB
> article I mentioned that has more info on error 1314:
> PRB: Error 1314 Raised By xp_cmdshell When Executed as
> Non-SA User
> http://support.microsoft.com/?id=248391

Could not find stored procedure spc_AddInformation.

After designing the database and completing the Java class to enter data into the database, I decided to take it home to work on the other pages for this application. (The data was transferring to the database with no problem at work). I restored the database and brought it home with me to setup it up on my pc at home. I setup the database at home and was able to load the driver and connect to the database but for some reason it can't find the stored procedure. The stored procedure is in the database but for some reason I keep getting this message -

SQL error.java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Could not find stored procedure 'spc_AddInformation'.

I've worked all day to find the problem but no luck. Can somebody let me know what the problem could be? It's not the code in the Java class because Im connecting to the database and the stored procedure name is correct in the code. What could be the problem? Thank You.Already answered in another forum - due to the login being used on the new server.

Could not find stored procedure 'sp_MSupd_xxxxxx'

I created a pull subscription to pull information from a production
database. When I started the subscription, the error "Could not find stored
procedure 'sp_MSupd_tablename'" showed.
I deleted the subscription in the subscriber and drop the distribution by
running the "Disable Publishing and Distribution Wizard" in the distributor.
Then, I recreated both the distribution and subscription from the very
beginning once again. However, the same error still showed.
I'd be grateful is anybody can help.
Thanks in advance!
KM
If you have used @.sync_type = None in sp_addsubscription or in the
subscription wizard, 'Initialize subscription' page, you select 'no, the
subscriber already has the schema and data' you may get this error. The
system tables for replication will be created on the subscriber in either
case but you'll need to manually create the stored procedures on the
subscriber if you use this option otherwise you'll have the above error when
you change a row on the publisher. Use sp_scriptpublicationcustomprocs
(assuming you have >= sp1) to create a script which creates the procedures
and run this script on the subscriber.
HTH,
Paul Ibison
"krygim" <krygim@.hotmail.com> wrote in message
news:ewJovUqhEHA.1356@.TK2MSFTNGP09.phx.gbl...
> I created a pull subscription to pull information from a production
> database. When I started the subscription, the error "Could not find
stored
> procedure 'sp_MSupd_tablename'" showed.
>
> I deleted the subscription in the subscriber and drop the distribution by
> running the "Disable Publishing and Distribution Wizard" in the
distributor.
> Then, I recreated both the distribution and subscription from the very
> beginning once again. However, the same error still showed.
>
> I'd be grateful is anybody can help.
>
>
> Thanks in advance!
>
> KM
>
|||Hi Paul,
Thanks a lot for your information. However, I was not able to find
sp_scriptpublicationcustomprocs in BOL. Could you show me how to use of the
procedure?
Thanks in advance.
KM
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:e4pQoWrhEHA.1184@.TK2MSFTNGP12.phx.gbl...
> If you have used @.sync_type = None in sp_addsubscription or in the
> subscription wizard, 'Initialize subscription' page, you select 'no, the
> subscriber already has the schema and data' you may get this error. The
> system tables for replication will be created on the subscriber in either
> case but you'll need to manually create the stored procedures on the
> subscriber if you use this option otherwise you'll have the above error
when[vbcol=seagreen]
> you change a row on the publisher. Use sp_scriptpublicationcustomprocs
> (assuming you have >= sp1) to create a script which creates the procedures
> and run this script on the subscriber.
> HTH,
> Paul Ibison
>
> "krygim" <krygim@.hotmail.com> wrote in message
> news:ewJovUqhEHA.1356@.TK2MSFTNGP09.phx.gbl...
> stored
by
> distributor.
>
|||This scenario may not be exactly yours, but you'll get the
idea:
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;320499

>--Original Message--
>Hi Paul,
>Thanks a lot for your information. However, I was not
able to find
>sp_scriptpublicationcustomprocs in BOL. Could you show me
how to use of the[vbcol=seagreen]
>procedure?
>Thanks in advance.
>KM
>
>"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
>news:e4pQoWrhEHA.1184@.TK2MSFTNGP12.phx.gbl...
sp_addsubscription or in the[vbcol=seagreen]
you select 'no, the[vbcol=seagreen]
this error. The[vbcol=seagreen]
subscriber in either[vbcol=seagreen]
procedures on the[vbcol=seagreen]
the above error[vbcol=seagreen]
>when
sp_scriptpublicationcustomprocs[vbcol=seagreen]
creates the procedures[vbcol=seagreen]
from a production[vbcol=seagreen]
error "Could not find[vbcol=seagreen]
the distribution[vbcol=seagreen]
>by
Wizard" in the[vbcol=seagreen]
subscription from the very[vbcol=seagreen]
showed.
>
>.
>
|||Thanks
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:2c3f01c486c2$b82bc470$a301280a@.phx.gbl...[vbcol=seagreen]
> This scenario may not be exactly yours, but you'll get the
> idea:
> http://support.microsoft.com/default.aspx?scid=kb;EN-
> US;320499
>
> able to find
> how to use of the
> sp_addsubscription or in the
> you select 'no, the
> this error. The
> subscriber in either
> procedures on the
> the above error
> sp_scriptpublicationcustomprocs
> creates the procedures
> from a production
> error "Could not find
> the distribution
> Wizard" in the
> subscription from the very
> showed.
|||Later editions of BOL may have these details, but if not this link has more
details: http://support.microsoft.com/default...b;EN-US;299903
Regards,
Paul Ibison
|||Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uOnbmgthEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Later editions of BOL may have these details, but if not this link has
more
> details: http://support.microsoft.com/default...b;EN-US;299903
> Regards,
> Paul Ibison
>
|||Hi
do let me know if you've had any difficulties running
"sp_scriptpublicationcustomprocs".
After creating the replication as described in the KB 320499, if you see
that Inserts get replicated well but "updates" gives
us the Following error;
"37000 Cannot update identity column 'column1'. 8102 "
Do let me know.
SB.

Could not find stored procedure 'sp_MSins_tablename'.

I am using sql server 2000 workgroup edition.
when trying to replicate data between 2 servers I am getting that
error
"Could not find stored procedure 'sp_MSins_tablename'."
Here's some info on this, if you are going with a 'nosync' subscription:
http://vyaskn.tripod.com/repl_ans2.htm#nosync
If you are on SQL Server 2000, all you need to generate the scripts for
these procedures is, sp_scriptpublicationcustomprocs
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"marios" <amarios@.terravision.com-dot-lb.no-spam.invalid> wrote in message
news:ktadnVLDj9lI1WXfRVn_vQ@.giganews.com...
I am using sql server 2000 workgroup edition.
when trying to replicate data between 2 servers I am getting that
error
"Could not find stored procedure 'sp_MSins_tablename'."

Could not find stored procedure 'sp_MSins_<table_name>'.

Error message for a Distribution Agent:
"Could not find stored procedure 'sp_MSins_<table_name>'."
Elham,
looks like you have set up things manually. You can still create the stored
procedure scripts and apply them at the subscriber, or alternatively allow
the snapshot to create everything (inc data files) and reinitialize. To
manually create the scripts, use sp_scriptpublicationcustomprocs. There are
details in this article:
http://support.microsoft.com/default...;EN-US;299903.
HTH,
Paul Ibison

Could not find stored procedure 'sp_MSin_<TableName>'

Hi,
Just completed the transactional replication and when tried to test the
changes made in the publisher data it (Distribution Agent) failed with the
following error:
Could not find stored procedure 'sp_MSupd_ACCOUNT'.
(Source: PARISDB2 (Data source); Error number: 2812)
Checked the sysobjects and all these procedures (sp_MSins, sp_MSupd etc) are
present in the database.
Current Configuration is: 1 Publisher, 1 Subscriber, Distributor database is
on the Publisher server, SQLServer 2000 (SP4), Windows 2003)
Please help me out....need to know the reason and the solution
Thanks & Regards
Sangra
Hi Sangra
This problem will happen when the snapshot schema is not applied on the
subscriber.
You can generate the scripts manually using the following procedure
exec sp_scriptinsproc 'articleid'
exec sp_scriptdelproc 'articleid'
exec sp_scriptmappedupdproc 'articleid'
Apply this script on the subscriber.
For getting the articleid check sysarticles table.
P. Srinivasan MCDBA
Consultant
C-13/1,GF,Tulip Garden, Ardee City,
Sector-52,
Gurgaon-122003
India
Mobile:+91-9810321551
"Sangra" <Sangra@.discussions.microsoft.com> wrote in message
news:1A700079-F991-4D00-82A6-756AF23CC16E@.microsoft.com...
> Hi,
> Just completed the transactional replication and when tried to test the
> changes made in the publisher data it (Distribution Agent) failed with the
> following error:
> Could not find stored procedure 'sp_MSupd_ACCOUNT'.
> (Source: PARISDB2 (Data source); Error number: 2812)
> Checked the sysobjects and all these procedures (sp_MSins, sp_MSupd etc)
> are
> present in the database.
> Current Configuration is: 1 Publisher, 1 Subscriber, Distributor database
> is
> on the Publisher server, SQLServer 2000 (SP4), Windows 2003)
> Please help me out....need to know the reason and the solution
> Thanks & Regards
> Sangra

Could not find stored procedure 'SP_DBOPTION'.

Hi All,
Command:
SP_DBOPTION 'ORDERDB', 'SELECT INTO', 'TRUE'
Error Message:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'SP_DBOPTION'.
I am getting the above message when I run the said
command. I tried to locate the resolution at several
places and no help
Thanks,
Mohammed Sarwar
Ocp Dba Oracle 9i, 8i, 8.0If you have a case-sensitive installation, you need to specify the
stored procedure name in lower case:
EXE sp_dboption 'ORDERDB', 'SELECT INTO', 'TRUE'
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Mohammed Sarwar" <MSarwar@.uBid.com> wrote in message
news:29fe001c391dd$1012bfd0$a601280a@.phx.gbl...
> Hi All,
> Command:
> SP_DBOPTION 'ORDERDB', 'SELECT INTO', 'TRUE'
> Error Message:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'SP_DBOPTION'.
> I am getting the above message when I run the said
> command. I tried to locate the resolution at several
> places and no help
> Thanks,
> Mohammed Sarwar
> Ocp Dba Oracle 9i, 8i, 8.0
>|||Dan,
Super! That worked.
Thanks,
Mohammed Sarwar
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!