Sometimes Gauging Performance Can Kill It
But not with the right tools to dig into your systems. It’s amazing if you consider that a common database server will have 4,000 unique application SQL statements that can run 10+ million times during the business day. With Sql Power Tools, you can find out what’s running, what’s running slower than it has historically, and dig in to see what’s up. Check out SQL Power Tools – they have some solid ways to see how your system is performing, all using their non-intrusive, zero-impact approach. Get more information here.
Filestream – a Clarification and Information
Yesterday I wrote about the Filestream capabilities in SQL Server – and I did receive some clarification from Microsoft on a few of the elements. First, part of what I said was:
Now, with the FileStream approach, you can store these objects within SQL Server. The catch is that they’re still stored separately on disk, outside the database.
And Microsoft (thanks Rajendra!) provided the following additional information:
"While it is indeed true that filestream data is stored as files outside the database, SQL-server continues t control these files. Specifically,
– Filestream data gets backed up as part of SQL-server backup and gets recovered along with the rest of SQL server without users having to do anything special
– All transactional guarantees are applicable to filestream data as well.
– In-band (T-SQL based) access to filestream files is subject to SQL server access controls.
– A user may access filestream data OOB (API – based access) only if he meets the access controls of both SQL server as well as the OS."
It actually answers some of the bigger questions there were asked today when people wrote in – backups, access controls, etc. I’ll keep you posted as others write in with their experiences with the Filestream capabilities. (Email your thoughts here about using it, considering it, etc.)
Microsoft Officially Talks About SQL Server v.Next
…it’s all about BI. Interesting – because that was a huge push for 2008 as well. Still learning about what this means for future releases of SQL Server, but the overall direction of the upcoming release in this area is a fuller integration of tools that you can use to get to BI features, and easier – much easier – access to information in general so you can make better, faster decisions. The big emphasis on this update, especially as compared to the 2008 release, is a focus on "self service" BI. 2008 is foundational (my take and description, not theirs) and Kilimanjaro, the next release of SQL Server, is more about the continuing very tight integration with tools (Excel, SharePoint, etc.).
It really looks very interesting, but is very early on – I’ll keep poking around for additional information and demos and I’ll make sure you’re up on it.
Featured White Paper(s)
BitLocker: Is It Really Secure?
What is BitLocker? How does it work? Is it a truly safe way to protect your data and applications, hard drive, and operation … (read more)
Bust a Move With Your SSIS – Passing Package Variables
Explore the creation of sample development data using one of the most basic features in this new interface. Integration Serv… (read more)