Continuing the conversation I began in Part 1 & Part 2, today I want to ruminate some more on networking. I've had a good discussions about networking since I wrote the first two parts, with a focus on the value of networking.
2009-01-23
1,698 reads
Had a bit of an oddity show up during some testing today when trying to disable log shipping on the primary server using SSMS. My test scenario was such that our secondary server was not available any longer (had been renamed) and when I tried to disable the log shipping...
2009-01-22
1,294 reads
I originally wrote this in French while working at LaCaisse.com "Why do you care, as a DBA (or a developer for that matter), about what is happening in the transaction...
2009-01-21
1,896 reads
We all have those things that happen at work that somehow turn into something other than expected, and sometimes in quite humorous fashion. I've got a few to share over the next couple months, but had to start with this one!
2009-01-19
160 reads
I didn't want to go on this trip, but I agreed to do it. Now I regret it. My flight to Chicago was fairly uneventful, but it was running late. At 4:30CST the pilot says we should be on the ground in 30 minutes, which is good since I have to get to...
2009-01-19
198 reads
We value your privacy. This policy explains what personal data we collect and why. What...
This came up one day at my work when a developer was using it....
I’m sure I’ve never mentioned that I’m an amateur radio operator. Like Vegans and...
I spotted this in the release notes for CU17 in SQL Server 2022: KB3616559...
I migrated DB server from 2017 enterprise to 2019 enterprise. After the migration, every...
Comments posted to this topic are about the item How Much AI Code Would...
I have a SQL Server instance that is not listening for connections on port 1433. By default, all ports are locked down on my server, except for the SQL Server port. What can I do to allow users to connect to the instance without knowing the port?
See possible answers