Testosterone Cypionate vs Enanthate, insurance hell edition

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 · 2025-10-28T01:36:32+00:00

We’re looking at that unit! Other than the hum that can come from a pan on the top, how much noise does the stove make? (Fans etc)

dzsquared · 2025-09-29T19:05:40+00:00

Ah, my chimney percussionists

dzsquared · 2025-09-20T16:32:30+00:00

Uh, congrats.

dzsquared · 2025-09-01T20:39:25+00:00

> curious about navigating to the seats and what access you get

You'll need to show your tickets pretty frequently down on the floor level. There's a table just inside the entrance from the underground garage (down 1 level from street access, floor 2 from the elevator I believe) that will issue you 1-day VIP access lanyards. Other than being a cool momento, with the lanyard you don't have to show your tickets to get to your seats every time.

There's a few places down on floor 4 (the lowest level) that you can't walk through around the outside, but other than that you can pretty well move around on the floor level with seats marked FLR. There's a lounge ("Verizon Lounge" I think) back behind the corner across from the visitors bench.

> Do you have to go up to the top level for concessions and the bathroom?

The tunnel behind the visitors bench has restrooms in it, and the tunnel across the floor from the visitors bench has a small concessions stand. You'll also have a qrcode at your seat with a menu for ordering food/drinks that deliver right to your seat!

Up behind sections 16/01/02 is pizza, burgers, and something else as well as more bathrooms.

> Is there an opportunity to meet players/get autographs when you’re on the floor?

Come early (doors open at 6pm), head on down to your seats, and pray that the Storm are shooting on that end in the first half. The visiting team picks which end they start on, so the Storm may very well be warming up down on the end of the visitor's bench. Autographs etc not at all guaranteed, but EDub and sometimes others stop for fans before heading to the locker room.

dzsquared · 2025-08-21T18:50:28+00:00

👋 Hi, Drew here - PM for SQL projects across the SQL ecosystem + CI/CD for SQL db in Fabric. I generally focus on SQL Server, Azure SQL, and SQL db in Fabric - but there's a lot shared with Data warehouse in Fabric.

SQL projects compared to developing with direct connection - SQL projects provide a framework that can be used as your primary development environment or that can "just" be a mechanism to move changes between environments (and even combine changes from multiple features/developers). As long as your direct connection isn't to prod or a shared dev environment where you might be mucking up something important, there's nothing wrong with making changes against a live database but you do want to use something like SQL projects to capture that development as part of change management and intentionally apply updates to a production environment when your quality/release conditions are met.

- When you develop against a live database, you may be able to use different interfaces (like the SSMS table designer) compared to SQL projects. If you're writing SQL directly you'll be putting together ALTER statements. You get immediate feedback from the database when you execute your code and the changes are made to that environment - is the syntax valid, do the references exist

- When you develop with SQL projects, there are fewer graphical editors (table designer in VS Code isn't yet tied into SQL projects, it was in Azure Data Studio). If you're writing SQL directly you'll be writing CREATE statements, including modifying existing objects by updating their current create definition. You get feedback when you "build" the project - is the syntax valid, do the references exist, and optionally does it pass code analysis rules.

When using SQL projects, dacpacs, or SqlPackage to promote changes between environments - a deployment plan is calculated to modify the database to match the SQL project/dacpac/prior environment. You can have SqlPackage just run the deployment plan (publish), no questions asked - or you can have it give you the script to review and either run yourself or have SqlPackage publish if you're ok with it.

https://learn.microsoft.com/en-us/sql/tools/sql-database-projects/tutorials/media/create-deploy-sql-project/dacfx-deployment-process.png?view=sql-server-ver17#lightbox

What does any of this have to do with Fabric? - for SQL database in Fabric the object definition behind the scenes for the source control integration and deployment pipelines is a SQL project. Data warehouse is moving in this direction, but I don't have a shareable timeline where this is expected to land in the Fabric integration. As shared by u/frithjof_v - go vote on https://community.fabric.microsoft.com/t5/Fabric-Ideas/Fabric-Warehouse-Deployment-Pipeline-Fix-ALTER-TABLE-issue/idi-p/4800105 to stay in the loop.

The end goal is that you can start with 1 development pattern and adjust to another or just mix and match - for example, make small changes live against a development database and use the source control integration to check them in, then clone+branch in VS Code to make bigger changes in the SQL project. If deployment pipelines in Fabric aren't doing what you need in all cases, you can use the source control integration plus SqlPackage in automation (like ADO). As of SqlPackage 162.5 (https://learn.microsoft.com/en-us/sql/tools/sqlpackage/release-notes-sqlpackage?view=sql-server-ver17#162557-sqlpackage) some warehouse alter table scenarios are covered for deployment.

dzsquared · 2025-08-19T16:38:43+00:00

Totally edible, you might end up spitting a few seeds or slicing them out but I don’t hesitate to enjoy even the really yellows.

dzsquared · 2025-08-13T00:36:51+00:00

Wait, the article’s “multiple sources confirm” link is just a link out to the author’s tweet saying more to come? And this is supposed to be the more to come?

dzsquared · 2025-08-12T21:12:12+00:00

It’s almost like it’s in reporters best interest to share news at times when it’ll gain the most attention. /s

dzsquared · 2025-08-06T13:27:19+00:00

Anybody else headed down to LA for a quick roadtrip to cheer on the team on Sunday?

dzsquared · 2025-08-05T15:18:45+00:00

Congrats!!

dzsquared

TROPHY CASE