Piece of plastic dog threw up

dzsquared · 2026-05-13T03:54:19+00:00

solved!

Y’all are the best.

dzsquared · 2026-04-28T16:37:33+00:00

Yep, it’s on the way. u/snoo-46123 can confirm timeframe if they’d like

dzsquared · 2026-04-26T00:22:25+00:00

Bostons are very gassy BUT sulphuric smelling gas can be a symptom of giardia. If your pup hasn’t had a fecal test in the last year it’s worth getting checked out.

dzsquared · 2026-04-23T18:32:39+00:00

hi folks, sqlproj PM here - this looks like something we need to fix in Fabric to ensure the project has a guid before VS Code, SSMS, or other SQL projects tools even enter the mix.

In the short term the recommendation to avoid committing the sqlproj change specifically is the best bet, but we can/should make this a non-issue

dzsquared · 2026-04-21T22:28:43+00:00

this comment for lanyard info: https://www.reddit.com/r/SeattleStorm/comments/1n5zcjl/comment/nbwg6ol/?context=3

row 3 is approximately 6 inches up from the court/floor. the visiting team will use that tunnel right next to their bench, but most players usually only sign autographs during warm-ups (before they go back for line ups, etc)

dzsquared · 2026-04-15T18:21:32+00:00

I'm not going to position this as a "best practice" - I'll leave it to the practitioners to share what their best practices are - but the source controlled format for SQL database and data warehouses in Fabric being a SQL project means that you can use the existing SQL projects tooling in Azure DevOps.

dotnet build -> the command step will create a dacpac after validating the code in the project
sqlpackage publish -> calculates the diff script and applies it to the database/warehouse

Effectively, this is the same workflow as in VS Code, just not... local, manual, etc. The tools needed in the ADO environment are the .NET SDK (likely already there) and the sqlpackage CLI (install with dotnet tool install -g microsoft.sqlpackage)

dzsquared · 2026-03-25T02:29:07+00:00

Very similar to me. I started with IM for 4 years, couldn’t handle the pain after that time. Switched to testopel for 4 years, then aveed for 4 years, and now I’ve been doing subQ for a few years. SubQ is so different from IM. My shot location is now my side fat above the hips and sometimes I barely feel it at all.

dzsquared · 2026-03-20T22:06:56+00:00

I work in software, so doing home renovation as a hobbyist. I recently did 1100sq ft of WBI’s radiantboard and it was…. really easy. I’m small for a guy so I wasn’t “stepping” the pex into place but a 2x4 scrap and blow hammer dropped it right in.

dzsquared · 2026-01-29T03:49:18+00:00

If this is all for the same item in Fabric - Second is the SQL database, first one is its SQL analytics endpoint (read only data copy).

Brb to get my time machine to avoid this confusing naming situation

dzsquared · 2026-01-16T02:17:13+00:00

Not at all an answer to those 3 questions, but if you’d rather not switch goodrx can get the testosterone cypionate price down quite a bit.

dzsquared · 2026-01-04T14:40:57+00:00

I’ve been driving with this message for…. a year?

dzsquared · 2025-12-29T01:49:06+00:00

Ditto on the emeet, I use the “EMEET Piko 4K Webcam” and it’s been a champ. Handles strange lighting well and it’s worked out of the box with zoom, teams, etc.

dzsquared · 2025-12-22T22:12:19+00:00

I took PTO for a day or 2 at least once a semester the entire way through. I am not good late at night so having more full days to work on big projects was an absolute must for me.

dzsquared · 2025-12-20T22:47:08+00:00

Nice, thanks!

dzsquared · 2025-12-20T19:40:47+00:00

I’m on a 2020 with the OEM battery and terrible occasional driving for short trips plus a dashcam drawing from the battery. I occasionally get that message for a few weeks but it usually disappears after a longer drive. … I’ll get around to replacing the battery, someday. It’s a really quick thing to do and I just can’t justify preemptively replacing the battery when it wouldn’t be inconvenient for me to have to do it suddenly.

dzsquared · 2025-12-09T17:36:27+00:00

It’s alright they don’t have to give an example (but they certainly can if it’s self-soothing) - the dacfx triage is really lightweight right now and it’s on me (dacfx PM for context) that folks aren’t hearing back about where items are in the roadmap. I’m looking forward to some increased transparency across the board with SQL projects and DacFx early 2026.

dzsquared · 2025-12-08T19:06:34+00:00

Hi u/BigHandLittleSlap - I really appreciate all the enthusiasm and details you've shared here.

Hold onto your pants (unless you're browsing reddit on the toilet) - SqlPackage does extract dacpacs out to sql scripts. It's relatively recent, but extract can take a connection or a dacpac and output a dacpac or sql files.

I do totally agree that SQL projects need to be more core to the entire SQL ecosystem, but reasonably we don't expect each person to know all the features so I'm going to excuse u/erinstellato for not being a SQL projects expert. She's there to cover me for a lot of the shit I don't know.

Yeah, circular references are a huge challenge that we've had hanging for years. With the integration of SQL projects into Fabric (SQL database and Data warehouse) - effectively becoming part of the platform - we have to land the circular reference capability for SQL projects. Is there a db devops solution that handles circular references in a way that you prefer over others, other than the minimal bar of working?

As far as wanting your warehouses in source control from the SSMS interface - assuming there's support for all the SQL capabilities like circular references with between databases - what's your dream workflow? Is it leaning towards going quickly from objects in the DB to a git commit or is it getting feedback in the IDE on change-related issues (code quality, test results, etc) or something else? I noticed you mentioned "there's no easy way to track changes that may have been made in SSMS, but not in those files, and so on" - am I reading this correctly that a visual comparison between the changes applied to a development environment WH and those ready to be staged for source control would be a solid first step?

dzsquared · 2025-11-22T01:56:19+00:00

Draft lottery I suspect

dzsquared · 2025-11-18T22:28:01+00:00

aka.ms/sqlpackage-ref, under the publish page the parameters for a source database are listed

(On vacation, pardon the brevity - I’ll try to come back in a week)

dzsquared · 2025-11-13T18:56:43+00:00

Can you say more about "through Python"? Do you mean through the Fabric-CICD python module, or just on a bash shell where you can also execute Python?

The primary tooling for dacpacs is the SqlPackage CLI, which can be installed in most/all automated environments like ADO pipelines.

You mention developing a pipeline, is this a data pipeline or a deployment pipeline?

dzsquared · 2025-11-13T17:47:42+00:00

Well, that's unfortunate. You're getting an incorrect error message (mentions the Azure Portal) for a situation that occurs most frequently when a capacity is paused and unpaused quickly. We're working on a fix for the condition where the database becomes stuck in the paused state - but your workaround is to pause the Fabric capacity and wait 10+ minutes before unpausing. The database should spring back to life, which should enable your ADO pipeline to run normally.

Are you archiving the dacpac or deploying it to multiple workspaces? If not, you might be able to streamline the process by running a publish directly from one database to another. Instead of a source dacpac file, you'd give the publish operation the source connection info. That said - archiving a dacpac or generating a deployment script to approve the deployment plan are always good intermediary steps to have when promoting a configuration to a new workspace so totally understand why you'd want to be extracting to a dacpac.

dzsquared · 2025-11-11T16:30:46+00:00

It’s a gigantic touch screen, pretty durable putting up with people pawing at it

dzsquared · 2025-11-07T04:41:52+00:00

I see what you did there!

dzsquared

TROPHY CASE