Showing posts with label drop. Show all posts
Showing posts with label drop. Show all posts

Saturday, February 25, 2012

ODBC no Stored Procedure

I create an ODBC connection to my datasource. Then in my data set i
only have a "Text" and no "Stored Procedure" in the drop down list.
How do i go around this and why is only "Text" available when using an
ODBC connection?
Thanks!I use ODBC extensively. For my stored procedures I use the generic query
designer. I have the command type of text and then put something like this
in:
pr_rpt_by_date_shift ?,?, 3
I usually first get it working by hardcoding the parameters and then I put
in the query parameters. Note that you have to use unnamed parameters. Then
you map those to the Report Parameters.
I am going against Sybase but it should act the same for other databases.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"muris" <rmuris@.hotmail.com> wrote in message
news:1114027214.114796.4340@.z14g2000cwz.googlegroups.com...
> I create an ODBC connection to my datasource. Then in my data set i
> only have a "Text" and no "Stored Procedure" in the drop down list.
> How do i go around this and why is only "Text" available when using an
> ODBC connection?
> Thanks!
>|||Ok, in generic query designer i have:
sp_qtrsumrpt ?, ?, ?, ?, ?
since my stored procedure takes in 5 parameters.
I'm able to get the list of the fields, but when i hit execute and in
the "Define Query Parameters" enter my parameter values, i get an error
message:
ERROR [42000][Microsoft][ODBC SQL Server Driver][SQL Server] Line 1:
Incorrect syntax near 'sp_qtrsumrpt'
How do you hard code your parameters and how do you map the unamed to
the report parameters? I'm not able to acomplish it! :(
Thanks!|||I answered this earlier today but I don't see my response here. When I get
into to work I'll see if it wasn't sent for some reason.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"muris" <rmuris@.hotmail.com> wrote in message
news:1114032042.597762.157350@.o13g2000cwo.googlegroups.com...
> Ok, in generic query designer i have:
> sp_qtrsumrpt ?, ?, ?, ?, ?
> since my stored procedure takes in 5 parameters.
> I'm able to get the list of the fields, but when i hit execute and in
> the "Define Query Parameters" enter my parameter values, i get an error
> message:
> ERROR [42000][Microsoft][ODBC SQL Server Driver][SQL Server] Line 1:
> Incorrect syntax near 'sp_qtrsumrpt'
> How do you hard code your parameters and how do you map the unamed to
> the report parameters? I'm not able to acomplish it! :(
> Thanks!
>|||By hardcoding I mean do this (obviously I don't know what values you should
be having).
sp_qtrsumrpt '1/1/2005','3/1/2005',25, 2.0, 10
Once it is working put in the ? marks. Then click on the ... and go to the
parameters tab. Sometimes (not always, not sure why it does sometimes and
not others), you should see the 5 parameters. RS then creates (if it did) 5
report parameters. I don't like the name that they create so I go to Report
Layout and the menu Report, Parameters and I change the name of the report
parameters. Then go back to the dataset, click on the ... and remap the
query parameters to the report parameters.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"muris" <rmuris@.hotmail.com> wrote in message
news:1114032042.597762.157350@.o13g2000cwo.googlegroups.com...
> Ok, in generic query designer i have:
> sp_qtrsumrpt ?, ?, ?, ?, ?
> since my stored procedure takes in 5 parameters.
> I'm able to get the list of the fields, but when i hit execute and in
> the "Define Query Parameters" enter my parameter values, i get an error
> message:
> ERROR [42000][Microsoft][ODBC SQL Server Driver][SQL Server] Line 1:
> Incorrect syntax near 'sp_qtrsumrpt'
> How do you hard code your parameters and how do you map the unamed to
> the report parameters? I'm not able to acomplish it! :(
> Thanks!
>

Monday, February 20, 2012

ODBC issue!!!

Im trying to run a very simple script on an index that doesnt exist.

Drop Index BLAH;

Create Index BLAH;

When I run this through an ODBC Connection it fails on the drop since it doesnt exist and STOPS running the script. Im hoping this is a simple setting on my part where if it errors on something as simple as a index to be dropped does not exist then it will continue to the next line in the script

Thanks

Scott

What about first checking in your script if the index you want to drop already exists ?

IF Object_ID('SomeIndexName') IS NOT NULL
DROP INDEX BLAH

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||I can do that butthe amount of modifications that would require would be huge. I was hoping there was an easier way.