Backup

Technical Article

SQL Server Backup, Integrity Check, Index and Statistics Maintenance

  • Script

Solution for Backup, Integrity Check, Index and Statistics Maintenance in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

4.87 (97)

You rated this post out of 5. Change rating

2018-06-04 (first published: )

48,038 reads

SQLServerCentral Article

Restoring to a Point In Time

  • Article

One of the lesser used features of SQL Server 2000, but the capability to restore your databases to a particular point in time can be a valuable skill. Kathi Kellenberger takes a moment to explain how this feature works and how you can use it in your environment.

5 (2)

You rated this post out of 5. Change rating

2005-06-14

17,787 reads

Blogs

Securing Kubernetes With External Secrets Operator on AWS

By

Here’s a way to centralize management, rotate secrets conveniently without downtime, automate synchronization and...

Save Azure PostgreSQL Backup to Storage

By

This may or may not be helpful in the long term, but since I’m...

The Book of Redgate: What’s Great about Redgate?

By

“I’m sick of hearing about Red Gate.” The first article in the book has...

Read the latest Blogs

Forums

Dynamic T-SQL Script Parameterization Using Python

By omu

Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...

Collation related issues

By LearningDBA

I have read that the collation at the instance level cannot be changed. I...

getting started paas SSAS

By stan

hi our on prem STD implementation of SSAS currently occupies about 3.6 gig of...

Visit the forum

Question of the Day

Multiple Sequences

In SQL Server 2022, I run this code:

CREATE SEQUENCE myseqtest START WITH 1 INCREMENT BY 1;
GO
CREATE TABLE NewMonthSales
  (SaleID    INT
  , SecondID int
 , saleyear  INT
 , salemonth TINYINT
 , currSales NUMERIC(10, 2));
GO
INSERT dbo.NewMonthSales
  (SaleID, SecondID, saleyear, salemonth, currSales)
SELECT
  NEXT VALUE FOR myseqtest
, NEXT VALUE FOR myseqtest
, ms.saleyear
, ms.salemonth
, ms.currMonthSales
FROM dbo.MonthSales AS ms;
GO
SELECT * FROM dbo.NewMonthSales AS nms

Assume the dbo.MonthSales table exists. If I run this, what happens?

See possible answers