We would like to offer a free copy of the May 2004 SQL Server Standard magazine to everyone who can take a couple minutes to update some demographics for us.
They have been very hard at work trying to get SQL Server 2005 ready for release, but many of them have been given a week's break after IDW15 to come down to TechEd. They've created an interesting diary that you can view.
Occasionally, SQL Server database administrators are requested to provide a list of development SQL Servers, production SQL Servers and so on. Many articles, such as "Monitor Disk Space on Multiple SQL Servers" and "Inventorying hardware and OS information on all SQL Servers" require a list of servers in a text file.
It's not a SQL Server event, but SQL Server is a large part of it. TechEd is a huge conference and one of the premier events put on by Microsoft each year. Read about the first day with Andy, Brian, and Steve.
When a SQL Server object is created, its properties are called metadata. The metadata is stored in special System Tables. For example, in SQL 2000, when a new column was created, the column name and data type could be found in an internal System Table called syscolumns. All SQL objects produce metadata. Every time SQL 2000 Enterprise Manager or SQL 2005 SQL Server Management Studio is browsed, the information displayed about database, tables, and all objects, comes from this metadata.
SQL Server 2000 does a lot of things for the DBA, tuning, updating statistics, scheduling tasks, wizards and more. But one thing that it does not help with is choosing the correct data type for your data. New author Amit Lohia brings us a technique and some code that will examine your existing data and suggest places where another data type might be a better choice.
This paper will explain and show how standard ANSI SQL processors can naturally model and automatically process complex multi-leg hierarchical data structures at a full conceptual hierarchical level. This also means the query user does not need to have structure knowledge of the hierarchical structures involved. The data modeling capability includes dynamically combining logical hierarchical relational and physical XML data structures at a full hierarchical level. This also includes the ability to link below the root of the lower level structure intuitively forming a valid unified hierarchical structure. As will be shown, ANSI SQL’s high level hierarchical data processing allows the flexible conceptual control of hierarchical node promotion, fragment processing, structure transformation, and variable structure creation.
In response to an article the Brian Knight write on the death of the production DBA, Sean McCown writes about the role that DBAs may play in shops that upgrade to Yukon (SQL Server 2005).
My interest in writing this article was started by an MSDN article titled SQL Server 2005: The CLR Enters the Relational Stage. The article shows how to write a function that returns the top three countries per category. That's always been something that was difficult to do in SQL so I was curious about the approach. The article started out well but I was very unhappy by the end. It's just soooo much easier to do this in SQL Server 2005 using the new CROSS APPLY clause in Transact-SQL. So I'm going to write a query to return the top 3 orders for each customer and I'm going to do it in about 10 lines of SQL. (UPDATE: An alert reader found an even better approach!)
By Steve Jones
immerensis – n. the maddening inability to understand the reasons why someone loves you...
In this post, I will guide you on how to deploy a dockerized simple...
You can now run powerful LLMs like Llama 3.1 directly on your laptop using...
Comments posted to this topic are about the item Understanding CROSS APPLY and OUTER...
Comments posted to this topic are about the item Database Files on Shares I
Comments posted to this topic are about the item Staying Employed
I want to store database files on a file share for a SQL Server 2017 instance. Can I use \\fileserver\D$ as a location?
See possible answers