Forum Documentation Showcase Pricing Learn more

SQL Server queries limited to 200 returns

I am trying to return a list of counties from an sql server instance is there a way to increase the number of returns?

image

1 Like

+1

Would love to see a limit increase or a workaround to this problem that doesn’t involve writing custom plugins.

Would be helpful. I had asked many months ago, but the answer was no. After lots of searching and playing around, I ended up finding a service (SlashDB) that would allow me to create APIs to access my SQL Stored Procedures (both to read and write). Cost me about $80 a month ($40 for the API Service and another $30-$40 for a VM on Azure). Would have saved me $80/month (close to $1,000/year) if they just increased the limit.

Ouch! A lot for a small system. What did you try for paging data in 200-row chunks? Was it too clunky to fit with your app?

Yes, but made the UI to cumbersome. Not money I was looking to spend, but saw no other way around it, and this was the least expensive API building solution I could find p. Btw, it works really well.

1 Like

Hi, that plugin funcion fast? in the search, editing and inserting ?

thanks

Slashdb is not a plugin. But, yes it is fast. You use it with the Bubble API plug-in.

Thank you ! do you think it’s easy to give a try? I’m not so pro programming.
But I would like to avoid that extra secs that with sql connector bubble takes.

Thanks again

It not really hard. If you know how to write simple stores procedures in SQL then it’s not really hard. You also have the option to use the API calls Slashdb can create automatically for you. There is a cost for the Azure VM they have it running in and the Slashdb product monthly. Together, I pay about $60/month for this. That’s in addition to Bubbles cost. Another idea is you could add resources to Bubble. They charge for that. I have two units (I forget what they call it off hand)!to help speed up the processing. While it helps, I still didn’t think it was responsive enough.

Hi, I created the virtual machine in Azure and followed all the steps but after that, in the slashdb website, when I try to connect my database, I get this error:

Cannot activate next database due to the license limitations.

Initially I thought that was because there was a demo db installed in the slash db databases section, but I deleted it and the error persists.

For the license payment I think that it is charged in the Azure configuration (It shows an azure per hour fee and and the slashdb per hour fee).

In the slash db license section, it shows that I have a production license through azure:

Current License Details

License Type:

Production License

Expiry Date:

Product Key:

b34e845b31…

Maximum Users:

100

Maximum Databases:

1

Licensed To:

Azure Subscriber

You should contact slashdb. There is a free version License for sql development. Only when you are ready to deploy your app would you need to pay for licensing, although you may have Azure vm charges. But victor (the owner), at slashdb is very helpful to help get you the right licensing. I don’t recall, but I had some similar issues when starting up. He cleared that up at the time.

1 Like

Thanks ! I can make it works in Slash DB,

but now I don’t know where to configure the api calls, where to write the api keys, how to call them (with a url and the parameters inside it with [] ? ).

Sorry for asking too much, but with only one that works I can go for my own :smiley:

Thanks !!!

You set up Bubble API Connector:

You add API calls to the connector:

You define the SQL Database and write your SQL Query calls in Slashdb:

Sample Query Statement inside the Query Statement box underQueries in Slashdb:
exec BudgetQuery :ProjID, :CustNmbr, :bubble

You would have a SQL Stored Proc with them BudgetQuery with those parameters. It would then return or write the data to/from SQL tables. Important: I always pass a Current Date/Time:Extract UNIX parameter. This forces a refresh to the SQL call. Otherwise Bubble uses it’s cached values.

Hope you can follow all this. It takes some patience and trial and error, but you will figure it out in time.

Thanks !!! I really appreciate the time you take to do this tutorial.

I talked with Victor but he didn’t know how to configure here in Bubble. (The only thing that he said me was to select in

“Authentication”: “Private key in URL”,

then in Keyname: “apikey” and in Key value: (the api key in slash db settings).

I finally can make it works.

I found some tip that may be can be useful.

I noticed that always the first query is slower than the nexts (may be while Bubble connects to the api).

So I force a fictitious api call in a workflow on when page is loaded. I display data in one group that I don’t use, with only field (I use “1”), or one parameter maybe the Bubble refresh you use for example).

So the first query after that is faster than without this trick. (it also works for the Bubble’s sql plugin)

PD: have you tried the slash db offset? it works with bubble? or I might use another way.

Again thanks for all.