Using no_sms_on_drive.sms when installing on SQL cluster
SCCM setup has a habit of placing components on the drive it finds that has the most space. if you're using a clustered SQL instance then this can often mean that components intended for non-shared disks end up on shared disks.
To prevent this from happening, place an empty file named NO_SMS_ON_DRIVE.SMS at the root of each drive where you DO NOT want it to install the components and it will avoid using those drives i.e. place it on all drives except where you want it to install the SCCM components.
Note we're talking about the SCCM components here, not the actual database itself. SCCM installs some components on each physical node to assist with things like backup.