Colin,

Thanks for the feedback. If you would, I'd appreciate some detail on your concerns.

Why would the utility not be able to be used in a controlled environment? Because xp_regwrite would not be accessable? If the system tables are to be moved, some utility (such as Microsoft SQL Server Configuration Manager) will need to write this same value to the registry, yes?

In order to automate the process, either xp_regwrite can be used, or some other way to update the registry can be. Whether that is REG.EXE, a REGEDIT input file, or direct API calls (perhaps through Perl or VB), a way to write to the registry gets exposed. I take it that your concern is that a SQL-familiar audience that may have been intimidated by API calls or unaware of registry-writing techniques has now found a way to write to the registry using a language they are familiar with.

My opinion is that most SQL programmers are familiar with either xp_regwrite or other techniques for updating the registry. The warnings about causing damage with direct registry writes abound and should be heeded, but that should not stop legitimate uses such as the utility I presented.

Again, though, thanks for your feedback. It gives me something to think about for the future.

Vince