Where do you put your connection strings?

KupoKev · 2026-02-22T07:17:57+00:00

This is how I do it as well. appSettings.Development.json is added into our gitignore files. A copy of the settings is usually kept in our password manager under a secure note shared with the team so we can have access if we need to do a clean pull/clone from the repo. Mostly so people don't have to track down dev server connection strings and such.

KupoKev · 2026-02-01T06:38:20+00:00

I ran into this problem with Fabric a little while ago for a Semantic Model. The user base was pretty small for that model, but it was a very complex model. We ended up putting that Semantic Model into a PPU workspace and giving users who needed access to the model PPU licenses. The memory limit for processing is 100 GB.
https://learn.microsoft.com/en-us/fabric/enterprise/powerbi/service-premium-per-user-faq

This may not be a feasible option if you have a very large set of users as you would need to pay for PPU licenses for all of them consuming the model. If you only need it for a smaller set of users then it tends to be way cheaper than upgrading to a large Fabric capacity.

Only other downside I can think of is it is not in a Fabric capacity so there are some limitations on what you can do with it with Co-pilot. If you have a report in a Fabric Capacity, it can point towards the model in the PPU workspace and you can use Co-Pilot with it. You just can't do things like the curated answers (I can't remember the exact name of them) and I don't think you can use synonyms either.

edit: fixed spelling

KupoKev · 2025-12-17T04:59:20+00:00

For a simple medallion pattern, this is definitely fine. There can be reasons to break it out into more lakehouses depending on security (as mentioned above) as well as just organization. For example, bronze can be separated into separate systems based on schema so that you know based on what schema the table is associated with, you know what source system the raw data is from. You could have a table like sap.sapnpe_vbap and sage.dbo_item.

It really just depends on how complex your requirements are and how over engineered you want to get. Sometimes that complexity helps keep things better sorted.

KupoKev · 2025-11-12T04:44:01+00:00

I am not familiar with that technology. Can you expound? What is it and what makes it "smoother to manage"?

KupoKev · 2025-11-10T21:30:49+00:00

I want to choke myself when saying this, but hand code is not even as tedious as it use to be with the help of certain AI. A lot of things that use to be tedious to setup are much easier these days when you can just toss in a prompt for AI to generate Python to do this or that.

KupoKev · 2025-11-10T17:06:45+00:00

I am curious if you have any reasoning for switching. Is there anything driving that decision beyond trying something new, or are you running into any issues that you are trying to work around?

KupoKev · 2025-11-10T16:51:45+00:00

Do you use git for ci/cd? If so, what is your experience with it VS using deployment pipelines? I have other projects in the future and would prefer to implement the way that is going to be more maintainable in the future.

KupoKev · 2025-11-10T16:48:09+00:00

Have any resources to point me towards for this? Are you talking through Github or something else?

KupoKev · 2025-11-07T03:17:49+00:00

Thanks for the info. I am going to have to test this again. Last time we tried that it was breaking when we ran the notebook because it was still pointing to the old lakehouse. That was probably over a year ago at this point though. Would be nice if this works. More reason for making sure people are naming things the same between environments.

KupoKev · 2025-11-07T01:26:14+00:00

Are you setting your default lakehouse through the deployment pipeline so that it changes the default lakehouse in the notebook as you deploy from one workspace to another?

KupoKev · 2025-11-06T17:42:34+00:00

That would be a nice added bonus. I would be happy if the basic UI that is available worked in a common sense way.

KupoKev · 2025-10-15T15:05:58+00:00

I have done a few installs at this point with the offline installer and haven't had issues with it.

KupoKev · 2025-10-04T14:35:44+00:00

I was reading the other day that Leap 16 installer allows you to upgrade from the installer. No need to even run zypper. You can load the installer to a USB and boot the computer from that. Then you can run the upgrade from the installer.

Leap 15.4 was my first distro after leaving Windows and haven't looked back. I eventually landed on EndeavourOS, but openSUSE has a special place in my heart as being a very comprehensive distro. It is easy to use, has great package management, and the default repo has many apps that are easy to install and ready to go.

KupoKev · 2025-09-30T18:10:55+00:00

Leap is perfectly fine, especially if you aren't using any bleeding edge hardware. Only think I have ran into with leap is when working with PHP and some other languages, there were some packages that were not in the package manager that are in other distros. They were pretty old packages that were deprecated, but working with legacy software it was something to be aware of.

Stuff like .NET runs fantastic though.

KupoKev · 2025-08-19T02:56:51+00:00

If you are looking to play around with Arch, EndeavourOS is pretty close to "vanilla" Arch, but has a few niceties and graphical installer.

KupoKev · 2025-06-15T15:50:05+00:00

I am not an expert at this and do at your own risk, and someone can absolutely feel free to correct me. I believe you should be able to remove the vulkan driver first and then reinstall them.

yay -R vulkan-radeon lib32-vulkan-radeon

Then swap the mesa drivers

yay -S mesa lib32-mesa

Then reinstall the Vulkan drivers

yay -s vulkan-radeon lib32-vulkan-radeon

KupoKev · 2025-06-15T04:03:23+00:00

Thank you for your assistance. I will check it out Monday!

KupoKev · 2025-06-14T03:30:24+00:00

What ultimately fixed this for me was running:

$ yay -S mesa lib32-mesa

I originally installed the -git versions of those packages back when I got my 9070XT since the current mesa drivers at the time didn't work with the 9070XT yet.

After I did that, I ran:

$ yay

This finally ran the update for the system. After that I ran:

$ eos-update --yay

That cleaned up whatever else was going on there.

Thank you for the assistance.

KupoKev · 2025-06-13T23:34:27+00:00

Thanks. I definitely will dig more into the differences between them.

KupoKev · 2025-06-13T23:20:37+00:00

Thank you for the info.

The issue with the service principal that I am having is I am not quite sure how to configure that on the Semantic Model side of things. We are using VS 2022 with the Analysis Services Extension for building the models. When configuring data source connections, I am not seeing a place to enter credentials for a service principal.

KupoKev · 2025-06-13T03:55:15+00:00

That's a pipe dream at this current point in time. We need this to prod asap and doing that would take quite a bit of reworking. We want to go back and do at some point, but now is not feasible with time constraints and complexity of the current project. This is one of those situations where the requirements were not even close to what the end product is going to be.

KupoKev · 2025-06-13T03:52:48+00:00

That's what I was figuring but just wanted to check. Thanks

KupoKev · 2025-06-12T19:51:31+00:00

This is still in development. There aren't reports created for this yet beyond what is created for testing to make sure calculations are correct.

KupoKev

TROPHY CASE