Chandra Sekhar Pathivada

Chandra Sekhar

Chandra Sekhar Pathivada is an independent consultant based in San Francisco. An MCST in SQL Server 2005 and SQL Server 2000, he specializes in developing and administering SQL Server database servers. He hosts the website to help fellow DBAs and the SQL Server user community.

white cubes of assorted size on blue and yellow data grid background
Revisiting How to Avoid Referential Integrity Errors
In this updated version of "Avoid Referential Integrity Errors When Deleting Records from Databases," Chandra Sekhar Pathivada goes more in-depth into the concepts behind his PR_HIERARCHIAL_DATA stored procedure.
white cubes of assorted size on blue and yellow data grid background
Avoid Referential Integrity Errors When Deleting Records from Databases 8
Deleting all the records in a database can be tricky when it includes tables with foreign keys. Here's a script you can use if you have ALTER TABLE permission and a stored procedure you can use if you don't.

Digital Magazine Archives

Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.


From the Blogs
Nov 3, 2015

Climb the Steps Toward Data Quality Success

Melissa Data's Data Quality Analyst Joseph Vertido explains how Gartner defines the critical data quality steps to prevent bad data from entering your systems in the first place, and then keep it clean over time....More
Sep 29, 2015

Data Breaches and Insider Threats

I’ll sound a bit like Captain Obvious for bringing this up, but it’s important to remember that security encompasses a lot more than protecting sensitive data from the specter of outsider threats like hackers. Properly implemented security policies also account for threat-models that include insiders – or people within your organization....More
Sep 15, 2015

Setting Up Additional Checks to Ensure Regular Transaction Log Backups 1

There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×