Administration

External Article

Managing Data Growth in SQL Server

  • Article

'Help, my database ate my disk drives!'. Many DBAs spend most of their time dealing with variations of the problem of database processes consuming too much disk space. This happens because of errors such as incorrect configurations for recovery models, data growth for large objects and queries that overtax TempDB resources. Rodney describes, with some feeling, the errors that can lead to this sort of crisis for the working DBA, and their solution.

2010-02-01

3,624 reads

External Article

Best Practice for renaming a SQL Server Database

  • Article

One of the Junior SQL Server Database Administrator in my company approached me yesterday with a dilemma. He was assigned a task to rename few of the databases in Beta and Production environments; the reason being the database name was based on some other project that is no longer relevant to the data which is presently stored within the database. At first I started to tell him, but figured it would be smarter to document the same and share the information.

2009-12-08

6,195 reads

Blogs

Performance tuning KubeVirt for SQL Server

By

Following on from my last post about Getting Started With KubeVirt & SQL Server,...

T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future

By

I haven’t posted in a while (well, not here at least since I’ve been...

Keeping MS Docs Up to Date

By

One of the things that I like about the SQL Server docs (MS Learn...

Read the latest Blogs

Forums

Change Tracking – Troubleshooting

By Phil Parkin

I have change tracking configured in several databases, in QA and production environments, and...

is there a no code way to limit an ssis extract from excel to the 1st 21 rows?

By stan

is there a no code way to limit an ssis extract from excel to...

Pivot but preserve all rows on Aggregate column

By getsaby

Hello Need help in pivoting this data set, the Pivot takes MIN/MAX on a...

Visit the forum

Question of the Day

What is the PRODUCT

In SQL Server 2025, what does this return?

CREATE TABLE Numbers
( n INT)
GO
INSERT dbo.Numbers
(
n
)
VALUES
(1), (2), (3)
GO
SELECT PRODUCT(n)
FROM dbo.Numbers

See possible answers