Administration

SQLServerCentral Article

Using the SQLCMD in SQL Server 2005

  • Article

SQL Server 2005 has changed quite a bit about the way DBAs will work with SQL Server. One of the new tools is the SQLCMD utility that will replace isql and osql as the command line utility. Author Andre Vigneau brings us a first look at this new tool and how you can do a few neat tricks with it.

(1)

You rated this post out of 5. Change rating

2005-02-02

15,997 reads

External Article

SQL Server 2005 Part 5 - High Availability and Scalability Enhancement

  • Article

In this article, we continue our discussion on high availability and scalability enhancements in SQL Server 2005 Beta 2 release. Features such as clustering, database mirroring, online indexing, fast recovery, database snapshots, and snapshot isolation transaction level have already been covered earlier in this series - now we will concentrate on the remaining features, such as a new method of table and index partitioning, backup and restore improvements, and new hardware support options.

2005-02-02

1,738 reads

External Article

MSSQL Server 2000 Reporting Services: Black Belt Administration: Prepa

  • Article

General optimization of RS' performance is, beyond argument, one of the more important functions of the Administrator. In evaluating performance from various perspectives at the Administrative level, one readily useful source of information is the data we can obtain from the logs created by the system itself. Reporting Services generates a number of log files to capture information about server operations, status, and so forth. Within this group of logs, which we will explore individually within prospective articles within our series, the Report Server Execution Log is a great place to start in setting up a basic performance and auditing analysis capability.

2005-02-01

2,827 reads

SQLServerCentral Article

HOWTO: Create an Asynchronous Schedule For a Report Server Report

  • Article

SQL Server 2000 Reporting Services is one of the most exciting new enhancements to SQL Server in quite some time. The addition of a robust and flexible reporting environment is something that most DBAs and developers are pleased to see. New author Andy Leonard brings us a technique for scheduling the execution of a report asynchronously, so your application or system can get back to work while the report is being generated.

(2)

You rated this post out of 5. Change rating

2005-01-26

9,740 reads

Technical Article

Microsoft SQL Reporting Services – Running a Report from the Command L

  • Article

I recently ran into a need to run a report in SQL reporting services from the command line. The Report took four (4) input parameters and I had to export it to Microsoft® Excel and save it to disk. I had to rummage through the product documentation and the Microsoft® SQL Reporting newsgroup to get this right. For running reports from the command line, SQL Reporting services provide a utility called “rs utility”.

2005-01-26

2,602 reads

Blogs

Ad Hoc SQL Server Help

By

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

TempDB Internals – What’s New (SQL Server 2016 to 2022)

By

I wrote about TempDB Internals and understand that Tempdb plays very important role on...

AI: Blog a Day – Day 2: Generative AI, Multimodal Systems, and Agent AI

By

continuing from Day 1 where we covered the history of AI and GPT family,...

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