A customer sent us data in an SQB file format. Does anyone know how to bring this data into FileMaker?
This comment assumes you already have Microsoft SQL Server installed (the Express version is a free stripped down version available to download from Microsoft, as of summer 2016 anyway).
This morning I was able to download the trial as others have mentioned above, create a backup of a test database that has the SQB extension, then restore the backup in a Windows 10 VM running SQL Server Express 2014.
Download the 14 day trial of SQL Toolbelt from All Redgate's Products For SQL Server, .NET, And Oracle
Once downloaded, look for a file named SQLToolbelt.exe in your browser's downloads folder. Double click to install it. Here's the installer screen:
In test run, I selected only SQL Backup 9.2, and deselected all others.
Open the newly installed application (SQL Backup 9) from Start menu:
You'll get a popup the first time you open it, with an option to Install Server components. Click that... then...
Click next. If you haven't set up a a service account in SQL Server, hop into SSMS and do that first. I used the built in sa account, but couldn't remember the password, so hopped into SSMS and changed the pw first. Then back to SQL Toolbelt, then click next....
Use SQL Server authentication and the account credentials you've set up prior in SQL Server Management Studio (SSMS).
You'll get the above indicating the installation was successful. Now you should see your local SQL Server instance in the left pane of the SQL Backup application. Click the "Restore" button...
It will give you a series of 4 steps. I just left all the defaults in place, other than the point where i needed to browse the directory structure to tell it where the SQB backup is at....
Now hop back into SSMS and see if the restored database is there, in the above the database is named "TEST" in the Object Explorer. Right click it and select "Properties" to verify the backup is usable and browse the various attributes of the db.
If all that works, you'll then be able to look at all of the tables. Right click each table and script table as, SELECT TO, new query editor window... and this will build the SQL for you to do a simple SELECT of all rows... then click the Execute button and the results will display in the bottom panel...
Right click in the bottom panel and click "Save Results As"....
Save each query as its own using the syntax "table_name.csv" CSV file. Then, you can import each CSV into FileMaker. By naming the CSV the same name as the underlying table that the query's table was based on, you'll by default get the same table names in FileMaker since it will use the filename as the table name, unless you specify otherwise, when you import the CSVs into an fmp12 file.
Once you're done there, you'll just then need to analyze the tables by eyeballing the data to see if you can figure out what the relationship structure is by looking at the column names and/or data to determine what join predicates were used. This could be really simple or next to impossible depending upon how many tables are in the backup and how they are all related. Doubt there is any way to copy referentially intact relationships between SQL Server and FileMaker.
Or..... would be happy to try to restore the SQB file, and if successful export your tables into CSV's, then send back via Dropbox, if you'd like to place the SQB in Dropbox and shoot me a PM with your email and the Dropbox link location.
This looks to be proprietary to RedGate. In my search I found converters, but do have no experience with this format or the converters.
Do you have SQL Server and RedGate?
Unfortunately I don't have experience with either so I'm not sure where to begin.
ask the customer to resend in a different format? CSV, XLSX, DBF, even XML anything that is more standard.
Unfortunately the customer no longer has access to that system and their previous provider is belligerent.
How about using trial? (I don't know it is full feature or not)
Licensing - SQL Backup 9 - Product Documentation
I also have no experience. But its usage (CLI converter) looks not so hard.
I found this stackoverflow question.
How to restore database using sqb files in SQL SERVER - Stack Overflow
And perhaps some of the suggestions there can help (listed methods and utilites links)?
It would be helpful if someone with SQL Server could assist you!
Yeah, it looks like the backup software itself is $995. Maybe there's a trial version, too.
Redgate Software - Select Product
Thanks, that worked! I fumbled my way through setting up a SQL server and was able to recover... 262 tables. Field mapping this is going to be a nightmare.
On a related note, is it possible to automate querying all 262 SQL tables and saving the results as csv, or am I stuck doing this manually?
So you "imported" into SQL server? You can the try to ESS into SQL from FileMaker and you just see the tables. You should be able to also write SQL queries and the Import script step to create tables and bring in the data.
That sounds lovely and... complicated. Stackoverflow also mentions using Powershell or SQL Procedure, none of which I'm familiar with. I might have to do this export process again occasionally. Would anyone be able to consult on building this pipeline, PM me?
Awesome, glad your data was able to be retrieved from the oddball backup file to a SQL Server instance....
Your next step kind of depends on what you're wanting to do, long term, with the data... now that you've successfully rescued it from the proprietary backup file.
If your goal is to get the data out of SQL Server, and into FileMaker.... and then be done with SQL Server, I'd probably just bite the bullet and go through he process of creating the 262 CSV files, and then make a few backups of them for safe keeping, then start building your FileMaker application by importing the CSV's.
If you have a long term goal of keeping SQL Server for some reason, then it would worth your time to set up ODBC/ESS between the two databases... it all kind of depends on what you've wanting to do with the data. Kudos for rescuing it!
Retrieving data ...