Good afternoon Everyone! Thank you for coming to the event, and I apologize for the mix up in directions, I was on Dunvale Rd. at 6:30 am. :-) Here are the questions I took down at the event. Please comment if you have any further questions or if I missed any.
Q: How do you migrate an Oracle database to SQL 2005?A: This is a great question and there are tons of great resources here, to help with the migration from Oracle but also other database environments. With that said, and focusing on the question, it is a complex answer and fortunately there is a Solution Guide for Migrating Oracle on UNIX to SQL Server on Windows. There are a ton of tools to help you with this migration, from a lot of our partners. What makes this a challenge, is not so much the data but the applications that ride on top of the database. There is a fantastic white-paper comparing both SQL 2005 (beta 2) and Oracle titled: Features, strengths, and weaknesses comparison between Microsoft SQL Server 2005 (Yukon) and Oracle 10g databases. Even though the author has some preconceived notions about both products not a badly written document.
Q: What are the different ways to make Schema Owner Calls?A: One of the huge benefits of SQL 2005 is schema separation, this provides several benefits. This separation of database users from schemas provides several benefits to administrators and developers.
So the question becomes is what happens when you delete the owner, well hopeful nothing but it all depends on how you called the procedure. SQL 2005 now allows several ways to execute code:
Q: What happens when you run Microsoft Baseline Security Analyzer (MBSA) after you rename the SA account?A: So I downloaded the Microsoft Baseline Security Analyzer (MBSA) and got out my handy dandy Virtual PC and loaded the SQL 2005 beta 2. So I renamed the SA account (something new in SQL 2005), and ran the MBSA against my server and who-la, I got the ever informative Unhandled Exception Error. :-) This is what I expected the MBSA is configured to look for the information that it is programmed to look for.
Q: How does SQL 2005 handle dirty reads?A: There is an excellent white-paper about how concurrency and data consistency works, it is located here. It provides a great table that outlines the isolation levels, in addition the only way to get a dirty read, just like past products, is with read uncomitted. Check out here as well for more information on this topic as well.
Q: With the optimistic concurrency control turned on, does it copy the indexes into the tempdb?A: Unfortunately no, from the books online there are several limitations with concurrency row level versioning:
Any snapshot transaction that is active when the ALTER INDEX statement is executed receives an error if it attempts to reference the HumanResources.Employee table after the ALTER INDEX statement is executed. Read-committed transactions using row versioning are not affected.