If you are using SVN to deploy stuff then sure, why not? I can't count the amount of times being able to svn switch to the previous version of the app has saved our tails. It also opened up angles of letting people setup the push to production without access -- they commit, ops runs svn update.
Security-wise, it doesn't run anything that should be remotely exploitable and if you've got local exploit issues on the server then you probably need to rethink your security policy. The biggest issue if these are web apps is that the .svn folders on windows could potentially be read depending on server setup. Default IIS is fine -- it doesn't pass unknown extensions. But if you are, say, running tomcat as a web server, it will let people HTTP GET your svn-revprops and potentially bits of your source code, without some tuning. This is fixed by svn 1.7 as there are no longer .svn folders in every folder as 1.7 uses a central sqllite DB. So if you make the root folder higher than the webroot you are golden.
Or, if it helps you enough to be worth deploying to production than go for it understanding some caveats around file structures.