Hi,
I am presently using Client Access ODBC driver (32-bit) to connect to the AS400. I have set up a linked server that enables me to run queries against the AS400 using the driver. However I seek to have a driver that could give better performance. Right now I can extract 6 million rows from the AS400 table in like 2 hrs. Now is there an ODBC driver that can do better than that? Also I seek an evaluation edition of the driver if possible. Moreover I am the only developer and so a single user license is what I can have my supervisor budget.
Thanks,
VivekLook at www.hitsw.com. I've never used their drivers, but a friend of mine did and he praised their performance to the sky.
Regards,
hmscott
Hi,
I am presently using Client Access ODBC driver (32-bit) to connect to the AS400. I have set up a linked server that enables me to run queries against the AS400 using the driver. However I seek to have a driver that could give better performance. Right now I can extract 6 million rows from the AS400 table in like 2 hrs. Now is there an ODBC driver that can do better than that? Also I seek an evaluation edition of the driver if possible. Moreover I am the only developer and so a single user license is what I can have my supervisor budget.
Thanks,
Viveksql
Showing posts with label run. Show all posts
Showing posts with label run. Show all posts
Wednesday, March 28, 2012
Monday, March 19, 2012
ODBC communication link failure to SQL server
Okay-- if anyone can solve this they are truly the SQL genius! We are getting this error when we run a VB program that we use to access an SQL database on a server across our network on a workstation. In fact we get this same error when we even run the program on the server where the SQL database is running or on any of our workstations. Here is the error message:
08501:[Micorsoft][odbc sql server driver] communications link failure
Now the odd thing is that many other functions in the workstation application work fine and retrieve data from SQL but certain data requests by the workstation application fail with the above error message and we get this message consistently. Even though it appears that different workstations running the identical Vb application will get this error consistently but in different locations when running the application. We were running SQL 6.5 on an old server, with the workstation application for literally years without any problems. We also decided to upgrade to a new server, installed server 2000 operating system and the latest version of SQl -- moved all the databases pointed the workstations odbc at this new server and get exactly the same error in the same location in the workstation applications. The programmer that wrote the application and designed the database in SQL can't find the problem and a number of other computer "experts" also could not find the error. We did add a new linksys DSL router/firewall but everything kept working after this installation for several weeks so I don't know if this is the problem on the network. THe programmer also noted that he had problems using terminal services on our network to connect to his office computer and decided that there must be some network issues that are causing the ODBC communicaitions to fail and also terminal services to fail-- or of course they may be unrelated. Has anyone ever seen this ODBC communication error in their travels through SQL implementations? Any help will be greatly appreciated. If we can't fix this we will have to abandon a software application that has been used for over five years and just too complex to rewrite.
Jeff KilpatrickWell, this challenge is not really for a "true DBA", simply because it's related to ODBC driver for SQL Server. Link failure may be caused by several things, including improper closing of resultsets without notifying the server that no more records are needed. The definition ofthe error is:
The communication link between the driver and the data source to which the driver was connected failed before the function completed processing.
And that's what you need to investigate. The reason why it worked with 6.5 may be as simple as the version of the driver. So all the seeming mysteries are probably lying right in there.|||Not playing around with Windows XP SP2, are you?
Anyway, It sounds as though there is an ODBC DSN set up on each of these machines. Go through the configuration of this DSN on one of the affected machines, and see if the test connection button comes back successfully. If it is successful, then you may be looking at a client (i.e. VB Application) problem.
If the test is successful, have the programmer assemble all of his connection strings. If any of them specify PROVIDER as one of the attributes, then you may have your suspect. An ODBC DSN specifies PROVIDER and DATA SOURCE for most connection strings it is used in. Most often, it also specifies DATABASE. I have not experimented with it so much that I know if a connection string can override the DSN, or not, but it is worth a check. For this line of questioning, it would help if you could identify what functions seem to be erroring out. If it is random on each machine, and each attempt, then this will be a pain to figure out.
Another place to check is to make sure you have at least MDAC 2.7 on all of the machines. If you have applied SQL SP3 to the SQL box, then that box at least should have MDAC 2.7 sp1, I think. Microsoft has an MDAC version checker available on their website.
Hope this helps.|||We recently moved from an older (SQL 7 I think) server to SQL2000. Our VB application was using a DNS pointer to point to the SQL server.
This no longer worked once we moved the data to the SQL2000 server. As the poster above mentioned, I ran across a suggestion to run the MDAC patch. There is actually a newer version out now MDAC 2.8. I first ran this on my desktop and then we had to push it out and install it on all the clients which needed to connect to the new server.
Once we did that, we were able to connect to the SQL 2000 server without any problems using the DNS pointer.
A note, with ODBC, the pointer will not show up on your server list, you have to just type it in manually.
08501:[Micorsoft][odbc sql server driver] communications link failure
Now the odd thing is that many other functions in the workstation application work fine and retrieve data from SQL but certain data requests by the workstation application fail with the above error message and we get this message consistently. Even though it appears that different workstations running the identical Vb application will get this error consistently but in different locations when running the application. We were running SQL 6.5 on an old server, with the workstation application for literally years without any problems. We also decided to upgrade to a new server, installed server 2000 operating system and the latest version of SQl -- moved all the databases pointed the workstations odbc at this new server and get exactly the same error in the same location in the workstation applications. The programmer that wrote the application and designed the database in SQL can't find the problem and a number of other computer "experts" also could not find the error. We did add a new linksys DSL router/firewall but everything kept working after this installation for several weeks so I don't know if this is the problem on the network. THe programmer also noted that he had problems using terminal services on our network to connect to his office computer and decided that there must be some network issues that are causing the ODBC communicaitions to fail and also terminal services to fail-- or of course they may be unrelated. Has anyone ever seen this ODBC communication error in their travels through SQL implementations? Any help will be greatly appreciated. If we can't fix this we will have to abandon a software application that has been used for over five years and just too complex to rewrite.
Jeff KilpatrickWell, this challenge is not really for a "true DBA", simply because it's related to ODBC driver for SQL Server. Link failure may be caused by several things, including improper closing of resultsets without notifying the server that no more records are needed. The definition ofthe error is:
The communication link between the driver and the data source to which the driver was connected failed before the function completed processing.
And that's what you need to investigate. The reason why it worked with 6.5 may be as simple as the version of the driver. So all the seeming mysteries are probably lying right in there.|||Not playing around with Windows XP SP2, are you?
Anyway, It sounds as though there is an ODBC DSN set up on each of these machines. Go through the configuration of this DSN on one of the affected machines, and see if the test connection button comes back successfully. If it is successful, then you may be looking at a client (i.e. VB Application) problem.
If the test is successful, have the programmer assemble all of his connection strings. If any of them specify PROVIDER as one of the attributes, then you may have your suspect. An ODBC DSN specifies PROVIDER and DATA SOURCE for most connection strings it is used in. Most often, it also specifies DATABASE. I have not experimented with it so much that I know if a connection string can override the DSN, or not, but it is worth a check. For this line of questioning, it would help if you could identify what functions seem to be erroring out. If it is random on each machine, and each attempt, then this will be a pain to figure out.
Another place to check is to make sure you have at least MDAC 2.7 on all of the machines. If you have applied SQL SP3 to the SQL box, then that box at least should have MDAC 2.7 sp1, I think. Microsoft has an MDAC version checker available on their website.
Hope this helps.|||We recently moved from an older (SQL 7 I think) server to SQL2000. Our VB application was using a DNS pointer to point to the SQL server.
This no longer worked once we moved the data to the SQL2000 server. As the poster above mentioned, I ran across a suggestion to run the MDAC patch. There is actually a newer version out now MDAC 2.8. I first ran this on my desktop and then we had to push it out and install it on all the clients which needed to connect to the new server.
Once we did that, we were able to connect to the SQL 2000 server without any problems using the DNS pointer.
A note, with ODBC, the pointer will not show up on your server list, you have to just type it in manually.
Monday, March 12, 2012
ODBC 3146
Hi
Have you run the query through Query Analyser to check that it will work?
http://msdn.microsoft.com/library/d...s
ql.asp
describes the error 37000 as being possibly due to returning multiple
resultsets or a statement not supported by server side cursors.
Without seeing your SQL Statement it is not possible to know this!
Also
http://msdn.microsoft.com/library/d...s_violation.asp
describes an error occurring on SQL Server SP2, you may want to check it out
even though you may be on a higher version
John
"Sql_NeedHelp" wrote:
> Excuse me for my poor english
> I have MS access Database linked with SQL SERVER 7.
> Only 2 pc not execute a big Query.This query is composed of lot subquery.
> i have ODBC ERROR 37000. and this message "Alias and column (MS3) is
> incorrect"
> With SQL.LOG i read the syntax SQL is not identique with the sql synatx of
> good query.
> What do you Think of this? the ODBC drivers et Jet DB are the last version
.
> Thanks for your help
>
>Excuse me for my poor english
I have MS access Database linked with SQL SERVER 7.
Only 2 pc not execute a big Query.This query is composed of lot subquery.
i have ODBC ERROR 37000. and this message "Alias and column (MS3) is
incorrect"
With SQL.LOG i read the syntax SQL is not identique with the sql synatx of
good query.
What do you Think of this? the ODBC drivers et Jet DB are the last version.
Thanks for your help|||Hi
Have you run the query through Query Analyser to check that it will work?
http://msdn.microsoft.com/library/d...s
ql.asp
describes the error 37000 as being possibly due to returning multiple
resultsets or a statement not supported by server side cursors.
Without seeing your SQL Statement it is not possible to know this!
Also
http://msdn.microsoft.com/library/d...s_violation.asp
describes an error occurring on SQL Server SP2, you may want to check it out
even though you may be on a higher version
John
"Sql_NeedHelp" wrote:
> Excuse me for my poor english
> I have MS access Database linked with SQL SERVER 7.
> Only 2 pc not execute a big Query.This query is composed of lot subquery.
> i have ODBC ERROR 37000. and this message "Alias and column (MS3) is
> incorrect"
> With SQL.LOG i read the syntax SQL is not identique with the sql synatx of
> good query.
> What do you Think of this? the ODBC drivers et Jet DB are the last version
.
> Thanks for your help
>
>
Have you run the query through Query Analyser to check that it will work?
http://msdn.microsoft.com/library/d...s
ql.asp
describes the error 37000 as being possibly due to returning multiple
resultsets or a statement not supported by server side cursors.
Without seeing your SQL Statement it is not possible to know this!
Also
http://msdn.microsoft.com/library/d...s_violation.asp
describes an error occurring on SQL Server SP2, you may want to check it out
even though you may be on a higher version
John
"Sql_NeedHelp" wrote:
> Excuse me for my poor english
> I have MS access Database linked with SQL SERVER 7.
> Only 2 pc not execute a big Query.This query is composed of lot subquery.
> i have ODBC ERROR 37000. and this message "Alias and column (MS3) is
> incorrect"
> With SQL.LOG i read the syntax SQL is not identique with the sql synatx of
> good query.
> What do you Think of this? the ODBC drivers et Jet DB are the last version
.
> Thanks for your help
>
>Excuse me for my poor english
I have MS access Database linked with SQL SERVER 7.
Only 2 pc not execute a big Query.This query is composed of lot subquery.
i have ODBC ERROR 37000. and this message "Alias and column (MS3) is
incorrect"
With SQL.LOG i read the syntax SQL is not identique with the sql synatx of
good query.
What do you Think of this? the ODBC drivers et Jet DB are the last version.
Thanks for your help|||Hi
Have you run the query through Query Analyser to check that it will work?
http://msdn.microsoft.com/library/d...s
ql.asp
describes the error 37000 as being possibly due to returning multiple
resultsets or a statement not supported by server side cursors.
Without seeing your SQL Statement it is not possible to know this!
Also
http://msdn.microsoft.com/library/d...s_violation.asp
describes an error occurring on SQL Server SP2, you may want to check it out
even though you may be on a higher version
John
"Sql_NeedHelp" wrote:
> Excuse me for my poor english
> I have MS access Database linked with SQL SERVER 7.
> Only 2 pc not execute a big Query.This query is composed of lot subquery.
> i have ODBC ERROR 37000. and this message "Alias and column (MS3) is
> incorrect"
> With SQL.LOG i read the syntax SQL is not identique with the sql synatx of
> good query.
> What do you Think of this? the ODBC drivers et Jet DB are the last version
.
> Thanks for your help
>
>
ODBC - System DSN window is blank
We've run into a few XP machines in our organization that have some interesting quirk going on. We have several ODBC connections configured on the machines. However, when you go to ODBC connections, then click on the System DSN tab, it's empty. If we try to manually create a "missing" odbc, it says it already exists, do you want to overwrite, etc. We say yes, but it still doesn't appear. The main program being used has a dropdown box at the login screen that shows the various ODBC names to choose from. The ones from the System DSN tab (which is blank anyway) are not listed. However, if you manually type in the name of the ODBC that is supposedly configured but doesn't show up, it works. So, it sees the ODBC, but it won't display it to the human eye in the settings or drop down lists. What's up with that? We've tried reinstalling MDAC, java, windows updates, etc, etc. Only some machines are affected. I am unable to tell you what's been done to all these machines. The users are all set as admins on their machines. They all run similar software, etc. The only thing that happened around the time we started noticing this is that we added a couple new ODBCs and changed the settings in an existing one. We sent an exe to all users in the organization that auto configures these ODBC's so we don't have to do it manually. It works awesome, but I don't see how that exe could have caused this problem especially when the problem seems to have only shown up on about 1% of the PCs it was applied to.Found this at: http://www.dbforums.com/t1055278.html
01-01-05, 01:37
wconner50
Registered User
Join Date: Jan 2005
Posts: 2
System DSN not in ODBC Manager
You should export the registry entries for the ODBC.INI Data source and DataSet Names. Then edit the .reg exported file and see if there are any odd lines of text. I found a corrupt entry in the ODBC Data Source registry entry, all the missing system DSN's were right after the corrupt line. Delete corrupt line and deleted ODBC Data Source registry entry, then imported .reg file.
Problem was resolved.
01-01-05, 01:37
wconner50
Registered User
Join Date: Jan 2005
Posts: 2
System DSN not in ODBC Manager
You should export the registry entries for the ODBC.INI Data source and DataSet Names. Then edit the .reg exported file and see if there are any odd lines of text. I found a corrupt entry in the ODBC Data Source registry entry, all the missing system DSN's were right after the corrupt line. Delete corrupt line and deleted ODBC Data Source registry entry, then imported .reg file.
Problem was resolved.
Wednesday, March 7, 2012
obtaining the license key
Hello:
Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
of ours as this client's soon-to-be old server has run out of disk space.
I hope to obtain the SQL license key in a timely manner from their IT
department. In case I cannot get this key as quickly as I'd like, though, is
there a way to somehow get this key by reviewing files in the SQL folder on
the old server's hard drive?
Thanks, for your time!
childofthe1980s
http://www.nirsoft.net/utils/product_cd_key_viewer.html
Regards,
Trevor Benedict
MCSD
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B9D5700B-6E99-44B3-BEED-16E2B7C3F200@.microsoft.com...
> Hello:
> Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
> of ours as this client's soon-to-be old server has run out of disk space.
> I hope to obtain the SQL license key in a timely manner from their IT
> department. In case I cannot get this key as quickly as I'd like, though,
> is
> there a way to somehow get this key by reviewing files in the SQL folder
> on
> the old server's hard drive?
> Thanks, for your time!
> childofthe1980s
Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
of ours as this client's soon-to-be old server has run out of disk space.
I hope to obtain the SQL license key in a timely manner from their IT
department. In case I cannot get this key as quickly as I'd like, though, is
there a way to somehow get this key by reviewing files in the SQL folder on
the old server's hard drive?
Thanks, for your time!
childofthe1980s
http://www.nirsoft.net/utils/product_cd_key_viewer.html
Regards,
Trevor Benedict
MCSD
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B9D5700B-6E99-44B3-BEED-16E2B7C3F200@.microsoft.com...
> Hello:
> Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
> of ours as this client's soon-to-be old server has run out of disk space.
> I hope to obtain the SQL license key in a timely manner from their IT
> department. In case I cannot get this key as quickly as I'd like, though,
> is
> there a way to somehow get this key by reviewing files in the SQL folder
> on
> the old server's hard drive?
> Thanks, for your time!
> childofthe1980s
obtaining the license key
Hello:
Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
of ours as this client's soon-to-be old server has run out of disk space.
I hope to obtain the SQL license key in a timely manner from their IT
department. In case I cannot get this key as quickly as I'd like, though, is
there a way to somehow get this key by reviewing files in the SQL folder on
the old server's hard drive?
Thanks, for your time!
childofthe1980shttp://www.nirsoft.net/utils/product_cd_key_viewer.html
Regards,
Trevor Benedict
MCSD
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B9D5700B-6E99-44B3-BEED-16E2B7C3F200@.microsoft.com...
> Hello:
> Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
> of ours as this client's soon-to-be old server has run out of disk space.
> I hope to obtain the SQL license key in a timely manner from their IT
> department. In case I cannot get this key as quickly as I'd like, though,
> is
> there a way to somehow get this key by reviewing files in the SQL folder
> on
> the old server's hard drive?
> Thanks, for your time!
> childofthe1980s
Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
of ours as this client's soon-to-be old server has run out of disk space.
I hope to obtain the SQL license key in a timely manner from their IT
department. In case I cannot get this key as quickly as I'd like, though, is
there a way to somehow get this key by reviewing files in the SQL folder on
the old server's hard drive?
Thanks, for your time!
childofthe1980shttp://www.nirsoft.net/utils/product_cd_key_viewer.html
Regards,
Trevor Benedict
MCSD
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B9D5700B-6E99-44B3-BEED-16E2B7C3F200@.microsoft.com...
> Hello:
> Tomorrow AM, I am going to reinstall SQL 2000 on a new server for a client
> of ours as this client's soon-to-be old server has run out of disk space.
> I hope to obtain the SQL license key in a timely manner from their IT
> department. In case I cannot get this key as quickly as I'd like, though,
> is
> there a way to somehow get this key by reviewing files in the SQL folder
> on
> the old server's hard drive?
> Thanks, for your time!
> childofthe1980s
Friday, February 24, 2012
ObsoletedSprocException is being thrown
I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David
ObsoletedSprocException is being thrown
I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David
ObsoletedSprocException is being thrown
I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,
"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegr oups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,
"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegr oups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David
Subscribe to:
Posts (Atom)