For me, this year was an awesome year. I have done many new things. I found, that after all the Corana stuff I had to change a bit of the things I am doing. Just before Corona I tried getting into the world of the speaking. It is difficult to get involved. I have reached out to some people and together we made a first attempt to get into it. Few good fellows have helped me with this.

For a specific home project at my fathers place I needed to add data to a database which was in the cloud. The only thing was that that project could only do restfull requests. Because I played with data API Builder (DAB) quite intensive I thought about pulling up a dab server on a raspberry Pi. Of course my first attempts failed. I first wanted to run the package from the cloud straight by downloading binaries and see if that would work.

In a recent post on Linked In I announced that I have a bit a busy week. In this post I will sum up what I have done and how it worked out. DataWeekender 6.5 DataWeekender has a special place. I am volunteering there for a quite a few times. It is always a pleasure to work with the team. Somehow this year was more special for me. I was helping other speakers, but also have a session.

Now that we have DataAPIBuilder, a SQLServer in the Cloud and a web application that should be able to use Restfull API’s it is time to setup some authentication. I am not a fan of SQL Logins. Never bin and will never be. I want Azure Authentication uhh.. Entra Authentication as it is called nowadays. Making an app usefull for EntraID there are some requirements: You need to have a tenant.

In the last post we have created some more settings we need, like a Free Azure SQL Database, configured our Static Web Application to use DAB and configured User Managed Identities for as well the Database as well the Static web app. In this post we will continue. First step should be to enable the SWA to connect to the database, but it might come in handy if we also can talk from our development server to the database.

I am happy to announce that I have been selected to speak at Data Weekender 6.5. Saturday, November 4 2023 at 11:30 in track 1 I will be presenting the session named Opening up your database by API. I hope to pack in a few new items I learned recentlty about this exiting product. Next to presenting, I will be present in Track 1 the whole day to assist the other speakers.

Just a few days ago I read in an that he announced that there was a free azure database available. I am a Dutch guy. I like free. And it does fit perfectly in my dataAPI Builder stuff I am doing. Next ot the fact that I am writing this article using Github and Hugo running on Azure Static Webapp. I think this all fits in/together some how. In fact, that LinkedIn post referers now to https://learn.

ok. I have to admit. I was not in the understanding that my preview session of last week should mean that I would not have a good presentation. As you might have read in my previous post on my sort of bad hairday, I have survived and taken action. Yesterday evening the Final of my investigation on #DataAPIBuilder was going to finalize. Or not? At least, when Brian Bonk Ruelokke contacted me to do a presentation for Microsoft Fabric – DK: Overview | LinkedIn on something new, I accepted that challenge.

In my previous posts about #DataAPIbuilder I showed you how I created an environment for it. I used the Bikestores sample code which you can download from SQLServerTutorials. The source and explanation is here. I have installed that database in a VM on my desktop. That is running SQL2019 and the full stuff is downloaded from the Microsoft site. After that I configured my Visual Studio and tried to install the Nuget Package for DataApiBuilder.

API’s are usefull if you can read documentation over them, or if you can explore them. All decent API solutions deliver you something like a Swagger interface. Such an interface is helpfull if you want to find out which API is delivering you the data you want. Swagger is included in DataAPI Builder. You will find it under: HTTP http://localhost:5000/swagger/index.html HTTPS https://localhost:5001/swagger/index.html OPENAPI https://localhost:5001/api/openapi SWAGGER https://localhost:5001/swagger I encourage you NOT to use the HTTP one.

Camel C(h)asing? Last Friday I was finding out how to get the API builder installed. That was for a non programmer not that easy, but there is plenty of documentation on Microsoft Learn which is usefull. Today, I will try to build the connection to my SQL Instance which is running on premise in a VM. My NUC can do this.. It is awesome to get this done. Since I do not know what or where it should run, I just opened VSCode and start to write a Powershell like thing because I know I have to repeat some of this stuff sooner or later.

After my install yesterday, I could easily read what to do. But, Microsoft Learn is telling you something else. Where MS Learn tells you to do > dab --version I found that returned an error message: dab : The term 'dab' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

One of my friends invited me to do something on his Data Fabric usergroup Denmark in August. He wanted me to do a thing else than the Defender stuff. So I opted in for something new. I have read and seen some nice videos about a Open Source tool from Microsoft called Data API Builder. But, since it is new for me and I am eager to learn it. It is fun to do.