SQL Server has great client side tools, Query Analyzer, Enterprise Manager, for working with your server and managing it. But how many times have you wished for a web interface because you didn't have VPN or didn't want to give rights to a developer. Or maybe you host clients' databases on your server and don't want one person to see another's databases. Read this review by someone who actually uses this product.
This short article shows you how to use SQL-DMO to enable or disable all the triggers in a database.
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.
SQL Server Alerts provide a great way for the server to notify a DBA that some event has occurred, usually something bad that they need to fix. However alerts can also be used to drive business logic processes and enable some types of actions to be safely performed without requiring extraordinary rights by a user. Author Leo Peysakhovich brings us some ideas on how we can use alerts to implement business logic processing.
Brian Knight has started a new series base on his impressions of SQL Server 2005, Beta 2, aka "Yukon". Read about his first impressions of the product as he starts down the path of learning about the next version of SQL Server.
Are you familiar with using the Command object in ADO? If so, migrating to ADO.NET should be a snap.
The 2004 premier SQL Server event, the PASS Summit is coming to Orlando in September. Once again we'er working with PASS to sponsor and promote this event. Read Steve Jones' take on this event and why it's worth your time and your company's money.
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.
Developing applications for SQL Server usually results in a variety of access methods that the programmers use. A data access layer class, given to the developers, is usually seen as the best practice, but one that isn't usually implemented. In fact, in most software I've built, each developer uses his own method, or may cut and paste from another, but rarely is there a central access class. New Author Patryk Nowakowski brings us his solution using ADO.NET.
Automating SQL Server tasks is the sign of an experienced DBA. One who doesn't waste time on repetitive tasks that can be easily setup in a job, task, or some other scheduling process to run when they need to run. Haidong Ji has written a number of articles on how to perform automation and brings us yet another technique. This time he looks at managing your backup files, something that we all need to do, but all too often forget to do.
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