Scripting out your SQL Server 2000 objects is useful in any number of ways. You can save off the scripts for version control, generate the scripts needed to migrate to new hardware or a new environment, or just package up your application for deployment. Jon Reade brings us a look at the SCPTXFR utility, which can prove very valuable in managing your scripts.
2006-10-13 (first published: 2005-04-14)
38,831 reads
ADVERTISEMENT
So you've decided to secure your SQL Server infrastructure and you don't know where to start. This first guide in a two-part series on SQL Server patch deployment will help you track down those pesky servers before getting them properly patched.
SQL Servers represent a significant security challenge for a number of reasons. Primarily, they are ubiquitous. Hundreds of software packages use SQL Server as a data store as do a large number of commercial websites.
2005-04-11
2,667 reads
In working with many reporting tools over my career, particularly within enterprise business intelligence suites and high-end production reporting systems, I have become acquainted with various control features in each that allow administrators to govern the actions of end users. Reporting Services is no different in this aspect of need for control, and the application provides numerous avenues for restraining our users from kicking off resource crippling queries that, unchecked, could disrupt even the most robust systems, as well as to prevent other harmful activities. At various junctures within this series, we will examine ways to effect such controls on an intermittent basis.
2005-03-31
2,850 reads
SQL Server 2000 does an amazing job of running itself to a large extent, much more so in my experience, than the other major platforms. That being said, it isn't designed to run without some sort of DBA, at least not at an efficient level. But what value does a production level DBA bring to your organization? Your manager might wonder, but with many years of experience as a production DBA and manager, Steve Jones brings you a look at the value that a DBA provides.
2005-03-30
17,402 reads
2005-03-25
1,802 reads
SQL Server includes autonumber of identity columns despite the fact that they are not SQL-92 compliant. There is quite a bit of debate over the use of them in your database, but if you do decide to use them, you should be aware of potential problems. New author Troy Ketsdever brings us a story about his identity crisis and how it was solved.
2005-03-23
10,243 reads
2005-03-17
1,592 reads
SQL Server's master database stores tables with important and constantly updated information about the state of the SQL server. One of these tables, sysprocesses, can be used to track (in SQL Server itself) which SQL Server users are currently logged in and which database(s) they are accessing.
The quick way to find out if a particular user is accessing a particular table is with a query.
2005-03-17
2,982 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
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,...
By Steve Jones
It’s a day off for Redgate today. This is our annual wellbeing day, where...
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...
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