Andreas Wolter (www.andreas-wolter.com) has worked for over a decade as trainer (MCT), consultant and architect for SQL Server systems. He is one of less than a dozen experts worldwide, who have been certified as Microsoft Certified Master (MCM) on SQL Server 2008 and additionally Microsoft Certified Solutions Master Data Platform (MCSM) on SQL Server 2012.



Being an active member of the PASS he is also a speaker at various international conferences since several years.



With his Germany-based company, Sarpedon Quality Lab (www.SarpedonQualityLab.com), he provides development and optimization of database systems, with a focus on scalable, performing and secure deployments across Europe and worldwide. You can also follow him at Twitter at twitter.com/AndreasWolter.

  • Interests: Business Intelligence & Datawarehousing Performance Tuning Security

Blogs

Privacy Policy

By

We value your privacy. This policy explains what personal data we collect and why. What...

Why use XACT_ABORT?

By

This came up one day at my work when a developer was using it....

Using AI for Data Conversion

By

I’m sure I’ve never mentioned that I’m an amateur radio operator. Like Vegans and...

Read the latest Blogs

Forums

Find all records in a table whose values when summed up will equal another value

By kirkdevilliers

I have a list of transactions in a table. Each transaction has a unique...

sp_lock memory leak

By TheRedneckDBA

I spotted this in the release notes for CU17 in SQL Server 2022: KB3616559...

Migration related issue

By LearningDBA

I migrated DB server from 2017 enterprise to 2019 enterprise. After the migration, every...

Visit the forum

Question of the Day

Browsing for Instances

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