SQLServerCentral Article

CLR Integration

One of the more controversial new features in SQL Server 2005 is the inclusion of the Common Language Runtime (CLR) inside the server. Whether you agree this is a good idea or not, the very knowledgable Chris Hedgate brings us the first article in a series looking at how the CLR fits into your database server.

Technical Article

A First Look at Express Manager

Microsoft describes its new, free SQL Server 2005 Express Manager (XM) as a "lightweight" database management tool built on top of the .NET Framework 2.0. Better yet, not only can you use XM to manage SQL Server 2005 Developer and Express Edition databases on local and remote computers, you can also use it with SQL Server 2000 and SQL Server 2000 Desktop Engine (MSDE 2000) databases. In this article, Rick Dobson shows you what XM offers DBAs.

SQLServerCentral Article

Scripted Server Snapshot

Users call and complain and by the time you get to the server, everything looks fine. Even running Profiler sometimes doesn't capture the information. Author Roy Carlson found a solution, a script that you can give to users to dump whatever information you need to an Excel file.

External Article

SQL backup encryption

Judging by mainstream news coverage over the past few weeks, the issue of data theft, particularly loss of backup tapes, has reached the tipping point. It might mean that your relatively anonymous existence within your company could come to a screeching halt.
A look at how encrpytion might be if importance to your company.

External Article

.NET 2.0 transaction model

The Microsoft .NET 2.0 platform introduces a new namespace called System.Transactions that brings in a lightweight, simplified transaction model. This article discusses the shortcomings of current transaction models and introduces System.Transactions for .NET Framework 2.0 beta 2.

Currently there are two transaction models available in the .NET world, both of which are suited for certain situations. The first is part of the rich ADO.NET data providers. The second is the enterprise services transaction. Before we examine System.Transactions, let’s have a look at the current models.

Technical Article

Meta-Data Trends & Technologies

The term “Enterprise Metadata Management” has been in use since the late 1980’s when many of us worked in classic “mainframe environments” using “corporate data dictionaries” to manage our COBOL programs, Job Control Language (JCL), screens, reports, copybooks, and database schema definitions. Fast-forward to 2005 ~ has anything changed? What does “enterprise metadata management” mean today ? I recently surveyed a number of leading metadata management vendors, Global 5000 companies, and industry thought-leaders seeking their input.

SQLServerCentral Article

Another DBA Whoops

Two in a month? Steve Jones brings us another mistake made by a DBA in SQL Server. Everyone makes them and we may not like to admit to them, everyone that we print hopefully helps a few other SQL Server DBAs avoid that particular mistake. This one looks at the dangers of sorting by aliases.

Blogs

Azure SQL offerings

By

There are three Azure SQL products with so many different deployment options, service tiers,...

T-SQL Tuesday #183 Roundup

By

I hosted this month’s T-SQL Tuesday party with my invitation asking about tracking permissions....

A Little Brainstorming with an AI

By

I was asked to do some a little thinking and brainstorming recently. Rather than...

Read the latest Blogs

Forums

MEMORYBROKER_FOR_RESERVE experience

By tony28

Hi, Does anyone have experience with MEMORYBROKER_FOR_RESERVE ? when suddenly there is somehow constantly...

Moving Database Files

By Ahr Aitch

I just learned that my database was created on my C:\ drive in the...

Migrate MSSQL to MYSQL - Different Servers

By cajun_sql

I am needing to migrate a MSSQL db to MySQL, on a different server...

Visit the forum

Question of the Day

Mixed Backups

I have a complex database with a few filegroups and files. Can I run a backup command like this? (assume file/filegroup names are valid).

BACKUP DATABASE [complex]
    FILE = N'thirdone'
 ,  FILE = N'thirdtwo'
 ,  FILEGROUP = N'second' 
 TO  DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL16.SQL2022\MSSQL\Backup\complex.bak' 
 WITH NOFORMAT, NOINIT,  NAME = N'complex-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,  STATS = 10
GO

See possible answers