PowerShell 101 for the DBA: Querying Your Servers with PowerShell
In my last blog post, I discussed how to get PowerShell and SQLPS up and running on your machine(s). And...
2009-09-22
1,919 reads
In my last blog post, I discussed how to get PowerShell and SQLPS up and running on your machine(s). And...
2009-09-22
1,919 reads
Many DBAs have heard about the new scripting technology from Microsoft, but have yet to really dive right in. You...
2009-09-15
2,514 reads
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...
By Steve Jones
When in doubt, overtip – from Excellent Advice for Living This is close to...
Comments posted to this topic are about the item How Much AI Code Would...
Comments posted to this topic are about the item Browsing for Instances
Comments posted to this topic are about the item Creating a Date Dimension (Calendar...
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