Administration

Technical Article

SQL Server 2005 - Managed execution

  • Article

The next version of SQL Server named SQL Server 2005 is completely hyped with the integration of CLR into SQL Server. The introduction of CLR into SQL Server allows developers to write stored procedures, triggers, user defined functions, user defined aggregates and user defined types using .NET languages like VB.NET and C#. This introduction has opened up multiple avenues for developers and we need to be careful in maximizing the feature provided.

2005-01-14

3,007 reads

SQLServerCentral Article

Recovery Planning For SQL Reporting Services

  • Article

SQL Server 2000 Reporting Services is becoming a more and more popular reporting option everyday. However, the disaster recovery plan for this add on is not a simple backup and restore since there are multiple pieces and servers usually involved. However the DBA may be responsible for the entire system. Mike Pearson brings us a look at some of the scenarios that you need to consider and what you might need to prepare for disaster recovery of SQL Server 2000 Reporting Services.

(4)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

29,313 reads

SQLServerCentral Article

SQL Server 2005 DBCC Command Quick Reference

  • Article

The next version of SQL Server due in 2005 will bring about many changes in how it works, with .NET, the CLR integration, Integration Services, and much more. Many of us are looking to get a jump on the product and see where these changes might affect our scripts and environments. Jon Reade has started the work in decoding the new DBCC commands, which ones work and which don't. Since there's a limited amount of documentation for the Beta product, read about his detective work and send him off an

(11)

You rated this post out of 5. Change rating

2004-12-16

34,294 reads

SQLServerCentral Article

Finding Objects Owned by non-DBO Users

  • Article

SQL Server has this concept of an owner of an object. Similar to the concept of schema, but not quite the same. Best practice dictates that all objects in SQL Server be owned by dbo, but that does not always happen. Tracking those objects down might be a pain, but Santveer Singh brings us an easy way of doing this.

You rated this post out of 5. Change rating

2004-12-15

6,093 reads

SQLServerCentral Article

Scheduled MS Cluster Failovers using Automation Server Objects

  • Article

SQL Server clusters are great tools to ensure that your servers are highly available. However there are some times when you'll want to manually perform a failover for testing, maintenance, etc. New author Anthony Bressi brings you a technique and code to allow you to use VB 6.0 to build a small program to automatically do this.

(1)

You rated this post out of 5. Change rating

2004-12-06

4,901 reads

Blogs

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments

By Massimo Preitano

Comments posted to this topic are about the item Concurrency and Baseline Control: Level...

Spending Time in the Office

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spending Time in the Office

Visit the forum

Question of the Day

Multiple Values Inserted

I have this code on SQL Server 2022. What happens when it runs all at once?

DROP TABLE IF EXISTS dbo.Commission
GO
CREATE TABLE dbo.Commission
(id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY
, salesperson VARCHAR(20)
, commission VARCHAR(20)
)
GO
INSERT dbo.Commission
( salesperson, commission)
VALUES
( 'Brian', 12 ),
( 'Brian', 'None' )
GO
 

See possible answers