From localhost to going online, limitations I could get if I'm using a hardware that has a data from MS SSMS

This will be the first time that I'm going to up a website. The domain(?)/site we will be using would be provided by our school.

I'm a little worried since our system might get messy when we go online versus using localhost.

Our system works like this:

It is a time keeping logs for students using a facial recognition device.

So every time a student enters the campus, they have to scan their face on the hardware. We already have a working real-time database to database system (MS SSMS to MySQL. However, the biometrics hardware is only compatible in SQL Server Management Studios 2017, it has a extension of .mdf

Weirdly too, as I mentioned, it's only compatibility is MS SSMS, so when I inserted the codes into three other laptops without the SQL Server, the logs kept on the website are not accessible and gets error that points out it needs SSMS.

Now, my system is working perfectly on our localhost, but I want to know if there would be limitations to this as I used MS SSMS, and if other errors could occur since I am getting data from MS SQL to MySQL using a query like (IF TABLE NOT FOUND CREATE THIS . . .)

To narrow it down:

• Can I only use the computer that will be used to up or online my website?

• Or can I use other computers AS LONG AS it has MS SSMS compatible to the hardware that gets MS SSMS?

• Or, it wouldn't limit it, as long as I have my device connected to a computer and every scanned face will be going inside the site as well?

If something is unclear, please do point it out, I've been sleepless for a month and I'm actually only using one eye right now as I am getting really sleepy. Guess being a programmer would always go on like this.