Search this blog
VS Live San Diego

-

-

Jones Book Club Tags
- administration
- AI
- AIExperiments
- auditing
- Azure
- backup
- Backup/Recovery
- blogging
- business
- career
- career2
- car update
- Cloud Computing
- conferences
- containers
- continuous integration
- coping
- data
- data analysis
- database design
- databases
- Database Weekly
- data privacy
- dbatools
- DevOps
- disaster recovery
- encryption
- Flyway
- Friday Poll
- FWTips
- GDPR
- Git
- goals
- hardware
- high availability
- Humor
- life
- Linux
- Microsoft
- misc
- monitoring
- networking
- PASS
- Performance
- powershell
- presentations
- Redgate
- Redgate Monitor
- republish
- sabbatical
- security
- software development
- software development
- speaking
- SQL Compare
- SQL in the City
- SQLNewBlogger
- SQL Prompt
- SQL Saturday
- sql server
- SSMS
- syndicated
- T-SQL
- T-SQL Tuesday
- Tesla
- testing
- tools
- travel
- tsqlt
- vacation
- version control
- webinar
- windows
- words
- work
Search this blog
Steve’s Tweets
Tweets by way0utwestOlder Posts
Meta
Tag Archives: sql server
The End of Support
With the accelerating pace of development and more frequent releases, we are seeing a bunching up of SQL Server support milestones. From 2008 through 2016, we had a new version every two years. Last year we saw another version, which … Continue reading
String or binary data would be truncated
Microsoft, please fix this. This issue is still out there, and once again, it’s the top voted on item for SQL Server. Everytime I see this: Msg 8152, Level 16, State 13, Line 1 String or binary data would be truncated. I’m … Continue reading
How Far Back?
At the Redgate SQL Privacy Summit recently, there was panel I hosted that I thought was really interesting. At one point someone asked a question and there was a bit of a discussion about the right to forget in the … Continue reading
Update Oddness for SQL Server
I’ve been meaning to patch some of my development instances. With a little spare time while doing other work, I started the process the other day. My first step was to patch SQL Server 2016 with SP2. This went as … Continue reading