One of the few things that SQL Server does not automatically help you with is the design of your tales, views, and other database objects. Having standards and design techniques can greatly ease the maintenance of your schema as well as ease the transition to having others work with the database. New author J.D. Gonzalez brings us some of his naming techniques to keep things organized.
Calling all developers! Does the idea of going from a concept to a prototype in a 54 hour marathon weekend of design and coding sound fun to you? If so, join us!
By using cascading referential integrity constraints, you can define the actions that SQL Server 2005 takes when a user tries to delete or update a key to which existing foreign keys point.
This white paper provides an introduction to various features of XQuery implemented in SQL Server 2005 such as the FLWOR statement, operators in XQuery, if-then-else construct, XML constructors, built-in XQuery functions, type casting operators, and examples of how to use each of these features.
Are you in the Zone at work? Can you find those times when you are amazingly productive? Tim Mitchell asks a question in this guest editorial.
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
I am excited to host T-SQL Tuesday for the first time. I want to...
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Comments posted to this topic are about the item Measuring Productivity
Comments posted to this topic are about the item Importing Excel files into SQL...
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers