While you can indeed restore one server’s master database over to another, it’s just not a good idea. In the event of a disaster, we don’t usually restore master. Starting Windows with a full C drive is not a lot of fun.
I’d rather not create tables that might grow when I’m not looking, and then possibly run my server’s limited boot drive out of space. The default installation parameters for SQL Server throw master, model, and msdb all on the C drive. System databases are often located on space-limited drives. But what’s the real deal? Why is this such a bad idea? Growing up as a young boy, my elementary teachers always warned me about the perils of putting stuff in master.
0 kommentar(er)
