Phil Factor

  • Interests: Motorbikes, Beer, gardening, conservation, Local history.

SQLServerCentral Editorial

Guest Editorial: That ain't a Database, it's a Spreadsheet

Phil recently had to draw up a list of 'top ten' pieces of advice for programmers who were starting out as database developers. It is a difficult thing to do when one is immersed in the study of the intricacies and detail of the plumbing of SQL Server.

(4)

You rated this post out of 5. Change rating

2008-12-18

440 reads

SQLServerCentral Editorial

Updating Aging Databases

Somehow, one is expected to be pleased that SQL Server 2005 is going to have another Service Pack. Why? For many DBAs, SQL Server 2005 is still a dangerous and radical upgrade. Phil Factor considers Microsoft's responsibilities...

2008-10-28

197 reads

Blogs

How to Parameterize Fabric Linked Services in Azure Data Factory for Azure Devops Deployment

By

Quite the title, so let me set the stage first. You have an Azure...

Deployment Pipelines in Fabric – What Are They?

By

In the realm of software development and content creation, the deployment pipeline serves as...

Ad Hoc SQL Server Help

By

I just need a few hours of your time… We get a variation of...

Read the latest Blogs

Forums

A Quick Restore

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Restore

Guarding Against SQL Injection at the Database Layer (SQL Server)

By Terry Jago

Comments posted to this topic are about the item Guarding Against SQL Injection at...

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

Visit the forum

Question of the Day

A Quick Restore

While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:

USE DNRTest

BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
/*
Bunch of stuff tested here
*/RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance.

See possible answers