Automating the installation of SQL Server was made simple in SQL Server 2005. SQL Server 2005 can be installed using a GUI, an ini file or just run setup.exe with a bunch of parameters.
2006-06-19
2,304 reads
This article, the last in the Stored Procedure series, will focus on RETURN parameters.
2006-06-16
4,328 reads
s running .NET Framework code within SQL Server 2005 exciting or a threat? Which is it? This article explores the security issues of SQLCLR code so that both developers and DBAs can make informed decisions about its use.
2006-06-15
2,774 reads
SQL Server 2005 comes with a built-in answer to this problem: the Database Engine Tuning Advisor. Combining a simple user interface with a deep knowledge of SQL Server, this utility can help you tune your databases for peak performance.
2006-06-14
3,523 reads
The Database Tuning Advisor (DTA) is an improvement over the old Index Tuning Wizard. Learn how to access the advanced features of DTA from the command line with a custom configuration.
2006-06-13
1,777 reads
Lightweight and adaptable, but with proper emphasis on the design phase, the ICONIX methodology can help you avoid Constant Refactoring After Programming...
2006-06-09
1,977 reads
A seemingly never-ending battle in online database forums involves the question of whether or not database application development should involve the use of stored procedures.
2006-06-08
2,270 reads
There is a lot of talk these days about “business intelligence” (BI for short). Pick up any magazine aimed at business or technology professionals, and you’re sure to read about things like data warehouses, dashboards, cubes, ETL, SCD, and a seemingly endless list of other specialized terms and acronyms. One might be left wondering, is this something to which I should be paying attention?
2006-06-06
2,524 reads
This (new) design bothered me. It violated one of the fundamentals that I'd learned and read about for years; namely keeping the primary key small and narrow. It also looked like it would be difficult to maintain. Finally, after arguing back and forth about the merits and drawbacks of each of the designs, we decided that testing them was the only way to be sure
2006-06-02
4,359 reads
The latest article in our series discusses improvements in the transactional support implemented in SQL Server 2005 Integration Services. The more granular scope of transactions, which now can be assigned to arbitrarily designated Control Flow tasks and containers, makes it is possible to limit their impact or execute several of them in parallel. However, even with this improved functionality, you need to keep the blocking issues they might potentially introduce in mind.
2006-06-01
2,138 reads
By Vinay Thakur
it has been a year since i have not written much on the blog...
By Steve Jones
on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...
By DataOnWheels
I have been active in the data community throughout my career. I have met...
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