Rick Dobson


Rick Dobson is an author, trainer, and Webmaster who specializes in Microsoft databases, Visual Basic.NET, and data-based Web development. He is the author of Beginning SQL Server 2005 Express Database Applications with Visual Basic Express and Visual Web Developer Express (Apress, 2005).

Making the Most of Login Controls with ASP.NET
ASP.NET 2.0 lets you use Visual Studio login controls with a SQL Server membership provider to dramatically simplify Web-site membership management.
Create Your Own Code Library 1
ADO.NET developers often use T-SQL strings to retrieve data for applications, but poorly written strings can lead to errors. By learning a few techniques, you can provide developers with a code library to use for many common data-access tasks.
Reporting Services 101
Although much excitement surrounded last year's release of SQL Server 2000 Reporting Services, some SQL Server professionals have put off adopting it. If you're ready to give Reporting Services a try, here's a tutorial that will get you started.
Web Services Made Easy
Let the SQL Sever 2000 Web Services Toolkit turn you into a Web services wizard as you build this sample telephone-directory application.
SQL Server and .NET: A Dynamic Duo 10
SQL Server and the .NET framework make a powerful pair for developing enterprise applications. If you're not familiar with .NET's languages and capabilities, this article's sample Web application can quickly bring you up to speed.
Special MOD XP SQL Server Features
If you're planning to use Access 2002 to build SQL Server 2000 solutions, Microsoft Office XP Developer makes a lot of sense.
Exporting a Table as an XML Document to a Web site 1
Here's an example that shows how to export a table as an XML document to a Web site.
What's New in Access 2002 1
Use this backstage tour of Access 2002's SQL Server-related features to help determine whether the new Access release is what your organization needs.
Views and Stored Procedures
This column looks at the SQL-DMO syntax required to examine and manipulate SQL Server views and stored procedures.
Creating Tables with SQL-DMO
Develop your basic SQL-DMO programming skills by creating tables in Access projects.
SQL-DMO: Learning the Basics 1
SQL-DMO lets you program custom solutions containing administrative functions for SQL Server by exposing objects, methods, properties, and events through a COM interface.
Programming SQL Server Security
You can use SQL-DMO to program a custom security interface.
Homegrown Security Solutions
Using object permissions and user-defined roles, you can fine-tune secure access to database objects.
Securing SQL Server Tables 1
In this second article in a security series, Rick Dobson shows you how to set up SQL Server account security through Access projects.
Access Granted
You can successfully log in to SQL Server from an Access project when you understand login process aspects such as authentication modes and login accounts.

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
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
Sep 1, 2015

Stop Using INFORMATION_SCHEMA and SysObjects for Exists Checks 3

Code like this isn’t optimal: IF EXISTS(SELECT * FROM sys.objects WHERE name = N'TableToDrop' AND type = 'U')         DROP TABLE TableToDrop; GO Neither is this: IF EXISTS(SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'TableToDrop')         DROP TABLE TableToDrop; GO Yet, I see both of those used all of the time – over and over again. Even though it’s 2015.  ...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) ×