Phil Factor reflects on how the people who made the industry great, in the past, were often eccentric, rebellious, odd, truculent, but all blessed with the gift of creating wonderful software. Today, such people would struggle to get pass the first interview.
We are getting more and more types of data that we have to manage and store in our databases. Steve Jones notes that SQL Server can handle almost all your needs.
Many of my clients need to make data that lives on one server available on another server. There are many reasons for such a requirement. You might want to speed up cross-server queries by providing a local copy of the data. Or you might want to make the data available to resource intensive reporting queries without impacting the OLTP load, maybe even with an intentional delay so you're always reporting against complete days only. Finally, you might be looking to implement high availability. In all these situations, SQL Server Replication is a viable option to look at when planning for the implementation of such a requirement.
Richard Morris interviewed Michael Stoop, a database developer at Calvi, Europe's leading provider of Telecom Invoice Management software. The discussion focused on how Calvi transformed their database delivery process to accommodate massive database growth, statutory regulations, and developments in their application. Here's their story.
SQL in the City is coming to Pasadena on October 9. Register for a full day of free SQL Server training the Red Gate way. Top tips and best practices for SQL Server database development and administration will be presented by SQL Server MVP experts, including Steve Jones and Grant Fritchey. You’ll also see Red Gate tools in action and have the chance to network with other data professionals.
Allen Kinsel is running for the board of directors of PASS. He took a little time to answer some questions from Steve Jones
Looking for a new job? Want to pick the best one? Your employer probably feels the same way. Andy Warren talks about how your interview is more like dating than you think.
Part one of a four part series intent on demystifying and making more accessible SQL Server extended properties
From time to time, I see a requirement to generate random identifiers for things like users or orders. People want to use random numbers so that the "next" identifier is not guessable, or to prevent insight into how many new users or orders are being generated in a given time frame, but they don't want to run into any duplicates. We can trade a bit of disk space and relatively predictable (but not optimal) performance for the guarantee of no collisions, no matter how many random numbers we've already used.
SQL Server Live! is coming to Orlando November 18-22. SQL Server Live! provides comprehensive education and knowledge share on SQL Server database management, data warehouse/BI model design, performance tuning, troubleshooting and more.
When I put together the invitation for T-SQL Tuesday #202, I wasn't sure what...
By Steve Jones
My life has some crazy travel stretches for sure. Between speaking, office visits, customer...
In Part 1, we saw how ‘Vamana’ represents vectors as nodes, connects them with...
Comments posted to this topic are about the item Server-Level Table sizes
Comments posted to this topic are about the item Optional Parameter Plan Optimization in...
There is a table tmp_tab:
CREATE TABLE tmp_tab ( id int, val int );
INSERT INTO tmp_tab VALUES (1, 1), (2, NULL), (3, 3), (4, 4), (5, 5);You want to order the rows ids by the following expression:
ISNULL(val, id) + 1Which of the following queries produces the expected ordering and why? (Select all correct) See possible answers