Unanswered

Is sharepoint usable as a database temporarily given the constraints

(0) Share

Report

Posted on by zajacjos

120

I need to move our database that uses SQL. The problem was that it ran on a laptop this obviously leads to problems. My boss wants to use sharepoint until we can move to the cloud, but online it says this is not a good idea. I think it may be possible as our database does not need to store much data( like the whole system stored is 10MB) does anyone know any complications or if this would work or not? I see there are Sharepoint connectors but obviously they could be utilized for simpler uses. Any resources would help also.

Background info:

Connectors MYSQL and teams:

Data cards used in MYSQL: Apps log, employees, parts, manufacturer, distributors and contacts.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

J0el 58 on at

Like (0)

Report

If you have multiple tables, that are related in some form. I would not recommend using SharePoint Lists.

What you could do, however, is use Dataverse for Teams, which is free, and allows creation of multiple tables that can be related. There is a 2GB limit, which sounds fine for your scenario. If in the future you need to go larger than this, then you can just move the solution to its own environment and purchase more storage. Licenced users of Dataverse and your app will increase the storage amount in Dataverse anyway, which may be sufficient, depending on how many users use the app.

If it is one table, then you can use SP Lists, however, you need to be aware of the 5000 record view limit. While Lists allows 30,000,000 records, you are restricted to the amount of records you can retrieve. So you must use filters where ever possible to keep below the 5000 limit.

Was this reply helpful? Yes No
zajacjos 120 on at

Like (0)

Report

Could I import my sql database to dataverse?

Was this reply helpful? Yes No
J0el 58 on at

Like (0)

Report

You can import using Dataflows (not Power Automate flows). However, you can use a Gateway to connect directly to your SQL server, instead, which will create Virtual Dataverse tables. That is, if you want to keep the SQL DB live. If not, import using Dataflows. Or there is an Import option in the Tables section of the Maker portal, which will allow you to connect to an SQL server as well, but probably does the same as Dataflows.

Guessing you could also export your table(s) in SQL to CSV, then use Dataflows to import those, which will avoid any connection issues to SQL server that you may have (firewalls, gateways etc.)

Was this reply helpful? Yes No
zajacjos 120 on at

Like (0)

Report

I just need to import the old database so the import option will work I think. Before I was thinking I would have to use Azure SQL if the sharepoint option didn't work. Is there any benefit to Azure sql other than more space? This sounds too good to be true lol.

Was this reply helpful? Yes No