I actually have to keep asking developers "Why do you want to put that in SQL Server? What value does SQL Server and a relational model add to that data? What are you going to join it to? What does it relate to? Did you consider the licensing costs?"

SQL, as a mostly-relational database, is good for some things. It is, however, a huge amount of overhead for other things (write only logs that don't relate to anything, for instance). It's even very bad at some things (properly constrained temporal databases), though sometimes there isn't a better alternative available. Sometimes there is.