Shrinking Databases
One piece of advice that is often given to new SQL Server administrators is not to shrink their databases. But they seem to do it often enough anyway. For this Friday's poll, Steve Jones asks if we should do away with shrink.
Facebook and E-Mail Security for a New Teenager
Cross-posted from a Goal Keeping DBA blog:
Just recently, my oldest son entered the ranks of the teenagers. I shouldn’t actually...
Giving Back, SQLMeetings.com Is Going Live Soon
I’ve been pretty quite since the PASS Summit and with good reason. Every year we have a chapter leader meeting....
Understanding and Controlling Parallel Query Processing in SQL Server
Data warehousing and general reporting applications tend to be CPU intensive because they need to read and process a large number of rows. To facilitate quick data processing for queries that touch a large amount of data, Microsoft SQL Server exploits the power of multiple logical processors to provide parallel query processing operations such as parallel scans. Through extensive testing, we have learned that, for most large queries that are executed in a parallel fashion, SQL Server can deliver linear or nearly linear response time speedup as the number of logical processors increases. However, some queries in high parallelism scenarios perform suboptimally. There are also some parallelism issues that can occur in a multi-user parallel query workload. This white paper describes parallel performance problems you might encounter when you run such queries and workloads, and it explains why these issues occur. In addition, it presents how data warehouse developers can detect these issues, and how they can work around them or mitigate them.
Certified Private Clouds
Microsoft is working to certify vendors to build private clouds, which Steve Jones thinks is a great idea.
What's Happening Here?
A look at what's happening with the SQLServerCentral servers based on the public information exposed by SQL Monitor.
Denormalization in SQL Server for Fun and Profit
Normalization is standard practice in database design, however, an over-normalized database can have issues. This article examines the case for denormalization.
SQLRally Call for Speakers Closes December 15, 2010
The call for speakers is open through December 15, 2010, and I hope many of you will take the chance...
Costing Cool Projects
Can you accurately determine the cost or benefit of a new, cool project up front? Steve Jones thinks not, but coming up with new projects can be a way to set yourself apart from others.
24HOP Needs Women!
“Next 24 Hours of PASS on March 15-16 2011, celebrating Women’s History Month with 24 female speakers!”
Thus goes the announcement on...
Blogs
Fabric Mirroring doesn’t start copying Rows
A short blog post about an issue with Fabric Mirroring (with Azure SQL DB...
JSON_OBJECTAGG is an Aggregate: #SQLNewBlogger
By Steve Jones
I wrote an article recently on the JSON_OBJECTAGG function, but neglected to include an...
Cultural Change: Fostering a Cost-Aware Culture in Your Organisation
By HeyMo0sh
After working deep in cloud operations, I’ve learned that FinOps isn’t really about dashboards...
Forums
Breaking SQL Server for disaster recovery practice
Hey all. I understand if this gets taken down due to the subject matter...
Creating a JSON Document I
Comments posted to this topic are about the item Creating a JSON Document I
Who is Irresponsible?
Comments posted to this topic are about the item Who is Irresponsible?
Question of the Day
Creating a JSON Document I
I want to create a JSON document that contains data from this table:
TeamID TeamName City YearEstablished 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933If I run this code, what is returned?
SELECT json_objectagg('Team' : TeamName)
FROM dbo.NFLTeams;
See possible answers