SQL Server is an easy to use product in many ways, much better than the other major RDBMSs out there. However it's source control and ease of moving changes from development to production needs some work. Having a solid process is as important as good tools and new author Grant Fritchey brings us his proven method for moving changes through QA into production.
2005-03-22
9,479 reads
Most database developers dread including such navigation features as paginated reports, hierarchical navigation, filtering, and full-text search because the amount of time they take to develop is not proportional to the utility or interest they create. In addition, connecting individual pages and controls to the database is mind-numbing work. Since writing SQL is non-trivial in any circumstance, it typically requires a specialist DBA's involvement.
..... As Web-based applications proliferate to bring more functionality directly to end-users, writing every SQL statement for every web-based application in your shop is likely to become a never-ending Sisyphean task for your DBA.
2005-03-10
2,209 reads
Working with a QA server in SQL Server 2000 is something everyone should learn to do. Having some staging area between development and production will help ensure a more stable environment and smoother deployments. After a little hiatus, Steve Jones continues with this series looking at moving the latest backup over to QA.
2004-09-29
6,561 reads
From SQLTeam's Bill Granazio, a look at how he ensures his database scripts are always working.
2004-09-01
806 reads
The final installment in Darren Fuller's series on change management in SQL Server. If you haven't read the others, be sure to go through them before reading this one to learn how automating your version control in SQL Server is needed for any development shop.
2004-08-18
7,337 reads
Part 3 of Darren Fuller's series on automating change management for SQL Server. A must read if you perform development and need a system to ensure that all changes are tracked.
2004-08-11
9,739 reads
The second part of the series by Darren Fuller on SQL Server change management, version control, and ways that you can automate this approach. If you do any type of SQL Server development, having a version control system is key to ensuring stability and keeping to your deadlines. Whether you agree with this approach or not, it's good information to have.
2004-08-04
10,104 reads
SQL Server change management is tough. The tools don't integrate with version control systems, there isn't good administrative controls to enforce control, and often you need to buy a third party tool to make this work. New Author Darren Fuller takes a look at the various ways in which you can implement version control in SQL Server. This is part one of a four part series on version control in SQL Server.
2004-07-28
13,730 reads
SQL Server has no change management integrated with the native tools. This means that each person must develop their own method of handling changes, or live with the chaos that will inevitably ensue. There are a number of articles written about various ways to handle change management and Dinesh Asanka shares his here. Read on and see if this helps you get a handle on changes in your environment.
2004-05-27
7,232 reads
Do you have to refresh a test or QA server from the production system? Do you have a good process or is it a spur of the moment, let's get it done thing? Here's a look at Steve Jones' process, which was used weekly for well over a year.
2004-05-17
7,766 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