2005-03-11
1,610 reads
2005-03-11
1,610 reads
Performing routine database maintenance such as reindexing is important for keeping your databases running at peak performance. When you use INSERT, UPDATE, and DELETE statements to modify table data, indexes can become fragmented. Index fragmentation can happen when the logical sequence of pages is disrupted or when an index page contains less than its maximum amount of data, creating a gap in the data page or index. As indexes become fragmented, you get inefficient data reads when accessing tables and slower database performance.
2005-03-10
3,919 reads
We introduced our previous article, Prepare the Execution Log for Reporting, with a discussion about a valuable source of information for performance and auditing analysis, identifying the Report Server Execution Log as a great place to start for this sort of reporting. We noted that the Execution Log captures data specific to individual reports, including when a given report was run, identification of the user who ran it, delivery destination of the report, and which rendering format was used, among other information.
2005-03-02
2,384 reads
Do you need the ability to manage your SQL Server data wherever you are? Microsoft released a Web interface that can help you manage your SQL Server databases. With this tool, called the SQL Server Web Data Administrator, you can:
* Perform ad-hoc queries against databases and save them to your file system.
* Create/edit databases in SQL Server 2000 or MSDE 2000.
* View, create, and edit stored procedures.
* Export and import database schema and data.
* Manage users and roles.
2005-03-01
2,523 reads
Ken Henderson explains the effects that SQL Server fiber mode coupled with the User Mode Scheduler component can have on your system, and what to consider carefully before enabling fiber mode.
2005-02-28
1,542 reads
In this chapter, we discuss various installation setups you can use to install and configure Reporting Services. For the most part, this process is managed by the Setup.exe installation wizard, so expect to be prompted for a number of configuration options that determine how, where, and whether each segment of the Reporting Services package will be installed. We know that there are a variety of ways to install Reporting Services, so we've tried not only to address the common case, but also provide hints and techniques to be used for some of the more sophisticated installation scenarios. To make this process as painless as possible, we've broken this chapter down into several sections:
2005-02-18
3,426 reads
SQL Server 2000 does not have the best or most secure password mechanism. In fact it does a pretty poor job of managing passwords and forcing changes. From the very knowledgable web team over at Orcsweb, a short article on how you change passwords in code.
2005-02-17
11,469 reads
2005-02-15
1,764 reads
In this two-part series, Serdar Yegulalp explains how to remotely administer SQL Server without compromising network security. In part one below, he describes two methods for providing secure administrative access to remote employees. In part two, he'll examine practical problems you may encounter when remotely administering SQL Server and how to work around them.
2005-02-15
1,665 reads
SQL Server 2000 Reporting Services uses cryptography to protect account data. Learn how SQL Server 2000 Reporting Services generates and stores the keys required to encrypt data.
2005-02-11
2,173 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers