A backup/diff/tranlog of job of roughly 500 databases shows a failure (Event_ID 3041). Checking, one of the databases contains a comma in the database name. All the other databases backup without an issue. The name of the database is in an encyclopedia and cannot change. I'm not sure that the comma causes the issue but of the roughly 500, it is the only one with a comma and the only one that fails.
Is there a way to alter the batching of the transactional/differential/full backup (using SSIS to alter the maintenance wizard) to prevent the backup failure of a database name that contains a comma? I'm trying to keep in mind here that while I can alter the SSIS package to place brackets around the name to make it work, another person coming into my shoes would not know why the backup process was customized and would probably feel more comfortable using the wizard to create the backups and the problem will recur.
SQL Server 2008 (not R2, not 2012) Is this a bug in the 2012 version as well? Should this go to Connect.Microsoft.Com? I have no 08R2 or 2012 databases to test against.
R, J