Uncategorized

SQLServerCentral Article

The CLR in SQL Server 2005

  • Article

Updated: Jan 2008. One of the big changes in SQL Server 2005 is the integration of the CLR into the relational engine itself. This is probably the biggest reason for the delays in completing the product and it is a controversial decision. Steve Jones spends a few minutes looking at the pros and cons of having the CLR integrated and possible implications for DBAs.

(10)

You rated this post out of 5. Change rating

2008-01-25 (first published: )

143,103 reads

SQLServerCentral Article

Inside SQL Server Development

  • Article

After the announcement last week by Microsoft that there would be no Beta 3 for SQL Server 2005 and that the CTP process would take over, Steve Jones had the opportunity to interview Thomas Rizzo and Allan Ros from the SQL Server development team about the CTP process and testing the SQL Server builds.

You rated this post out of 5. Change rating

2005-04-26

5,711 reads

SQLServerCentral Article

Learning SQL Server 2005

  • Article

Everyone wants to get ahead of the curve with SQL Server 2005, but many people don't have the time or desire to dig through a Google search. Steve Jones has gotten quite a few requests for resources, so here is a compiled list of some places that might help you get started.

You rated this post out of 5. Change rating

2006-09-08 (first published: )

45,312 reads

SQLServerCentral Article

The April CTP is Here and No Beta 3

  • Article

SQL Server 2005 is on everyone's mind, especially with SQL Server 2000 almost 5 years old. On Monday, April 18, Microsoft made an announcement that the April CTP was available, but there would be no Beta 3. Read Steve Jones take on this announcement as well as a few more details.

You rated this post out of 5. Change rating

2005-04-19

5,966 reads

Technical Article

SQL Server 2005 Editions and Integration Services

  • Article

The SQL Server 2005 product family has now been announced, so with four editions available, what does this mean for SQL Server Integration Services? Starting from the bottom we have the free edition known as Express, and the entry level Workgroup edition, and neither include the full IS product. They have the Import/Export capabilities, but nothing more, so for simple loading and extraction of data this should suffice, but you will not be able to build packages.

2005-04-07

4,009 reads

SQLServerCentral Article

Comparison of SQL Server 2005 Editions

  • Article

On February 24th, 2005, Microsoft announced the new editions and pricing of SQL Server 2005. There have been quite a few changes and MVP Brian Knight has put down a comparison as well as details about which features are included with each. Read about the 4 new additions and see which one might be right for your next project.

(2)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

65,375 reads

Blogs

SQL Server 2025 GAs Today

By

If you aren’t watching the Ignite keynotes today, then you might have missed the...

Run SQL Server 2025 and SQL Server Management Studio on macOS Tahoe

By

Short version You want to get this running as fast as possible. Do these...

The Roundup for T-SQL Tuesday #192

By

Last week I asked you to write about SQL Server 2025 and what things...

Read the latest Blogs

Forums

Best way to log Data Flow errors in SSIS 2005?

By jakestopher

Hi everyone, I’m working with some old SSIS 2005 packages, and I’m trying to...

Advanced Excel Mastery for Finance, Accounting & Payroll – 2025 Edition

By jackraines1717

Unlock the full potential of spreadsheets with our “Advanced Excel Mastery” course tailored for...

2025 Form 1099 Reporting Requirements: Essential 1099 NEC Updates

By jackraines1717

Prepare your team for the upcoming compliance shift with our “2025 Form 1099 Reporting...

Visit the forum

Question of the Day

Specifying the Collation

I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:

DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'

SELECT  p.PersonType,
        p.Title,
        p.LastName,
        c.CustomerID,
        c.AccountNumber
 FROM Person.Person AS p
 INNER JOIN Sales.Customer AS c
 ON c.PersonID = p.BusinessEntityID
 COLLATE @c
Will this solve my problem?

See possible answers