New data set - sybase stor proc

I'm new to BIRT so this may be a simple issue. I created a data source that connects to a Sybase server, but when I use it to create a new data set, it's only showing a list of user ID's in the default DB for the user ID I'm logging in with.

Is there a way to specify which DB to use when creating the new data source? Here's the sytax for the JDBC Driver URL I used......

jdbc:sybase:Tds:{server name}:{port number}.

We're running Sybase 15.

thanks.

Find more posts tagged with

Comments

mwilliams

Hi gslane,

In researching this, I found this format for the Sybase driver URL:

jdbc:sybase:Tds:{Server_Name}:{Port_Number}?ServiceName={Database_Name}

Try adding the '?ServiceName=databaseName' and let me know if that gets you the database you're looking for.

mwilliams

gslane,

Actually, it looks like that was for Sybase IQ. The following format for the driver URL may work better for Sybase ASE 15:

jdbc:sybase:Tds:{Server_Name}:{Port_Number}/{Database_Name}

Let me know. Thanks.

gslane

That was the correct format.... I was able to specify the database. I'm still only seeing a list of users. Should the "Available Items" listing include stored procedure names?

Thanks,
Steve

mwilliams

Steve,

Stored Procedures should show up too. It's possible that you have so much stuff on the database that your current BIRT settings are just too low to show it. You could check that out. Go to Window->Preferences->Report Design->Data Set Editor->JDBC Data Set and change the settings for how many schemas to show. Let me know if this helps.

gslane

Getting closer, but I still don't see any procs listed. I set the preferences very high and I'm now seeing all the users. Each user has a link for stored procedures under them, but none (that I checked anyway) has any actual procs listed.

Maybe it's an issue with permissions. We have all the procs in the database set as executable by specific roles, and then the user ID's are assigned to the appropriate role. I tried selecting the roles, which also show up as an available item, but they don't list any procs either.

My work-around for now is to just create an SQL query and code the proc execute statment explicitly. Not sure if doing it this way will cause any issues or not.... it seems to work.