Even if you didn’t mind unreliability, performance was a major problem – network file shares just weren’t fast enough to handle database access. Database administrators are usually way too paranoid to let their databases get corrupted just because somebody tripped over a network cable or a $200 NAS box failed. This was a pretty bone-headed idea – heck, it was hard enough to get our local and SAN storage to be reliable enough – so few people used it.
If you could buy it off the shelf from a major vendor, you were fine.įor ambitious people who wanted to gamble with their data, trace flag 1807 let you store your database files on network shares or mapped drives.
#Yo soy betty la fea capitulos completos windows#
Over time, we stopped buying hardware from a Windows Hardware Compatibility List because, well, everything worked. Server vendors got the point, and everybody’s local storage and SAN storage followed the guidelines. The SQL Server 2000 I/O Basics whitepaper explains in stern terms why not just any storage will do – we have to be sure our data will hit the disk in a calm, orderly fashion. In the past, Microsoft SQL Server required its database files to be stored on local drives or SAN storage. A Brief History Lesson on Trace Flag 1807 Since I’ve started using SQL 2012 in my lab, not a week has gone by that I haven’t used this feature to do something faster and easier. I don’t want you to build a solution from scratch with it, but it’s a killer tool that deserves a prominent spot in your bag of tricks. I’m about to discuss a feature of SQL Server that’s probably going to horrify you at first, but take a step back and think of it as duct tape. We carry our money in duct tape wallets, wear duct tape shirts, practice ductigami, and hang our duct tape from custom metal brackets. Sure, we pride ourselves on building a rock-solid solution the right way, but when the brown stuff hits the moving metal stuff, we love to show off our ingenuity.
0 kommentar(er)
