SQL Server 2005 - Interface Overview
In this article, we will be giving you an overview of what the new interface looks like in SQL Server 2005.
2005-02-07
2,762 reads
In this article, we will be giving you an overview of what the new interface looks like in SQL Server 2005.
2005-02-07
2,762 reads
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.
2005-02-02
15,997 reads
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
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
This paper explains how batches are cached and reused in SQL Server 2005, and suggests best practices on maximizing reuse of cached plans. It also explains scenarios in which batches are recompiled, and gives best practices for reducing or eliminating unnecessary recompilations.
2005-01-31
1,234 reads
When a DBA is managing many different SQL Server boxes, it can be a tedious job to find the port numbers used by all of the SQL Servers. In this article, I would like to discuss several methods for finding the Port numbers used by SQL Server.
2005-01-28
1,942 reads
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.
2005-01-26
9,740 reads
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
Table partitioning is a powerful new feature in SQL Server 2005. It is primarily a manageability feature, but my interest here is in the performance and scalability of table and index partitioning for use with very large tables.
2005-01-24
1,462 reads
2005-01-17
1,181 reads
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
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 REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers