Greetings Everybody! I currently have data that has to be pivoted in order to have the user report on it in the way they want. I'm doing this from VB.NET by creating a dataset and pivoting the data there, exporting to an XML file and using Reporting Services XML datasource. All works beautifully! Now for my "opportunity"... My users are starting to use Report Builder to run their own reports which is great, except I cannot build a Report Model based on an XML file. Therefore, I've written a stored procedure that will use SQL2005's new PIVOT to perform my cross table functionallity. Problem is, to make the data available to build a report model, I need to have a static table defined, and the table definition can change based on user selection. Therefore, within the stored procedure, I'm dropping the table, and creating the table based on the latest layout from the user, which gives me a static table. My concerns are with the constant daily dropping and recreating of tables. Obviously, I'm gonna take a little performance hit, but I'm more concerned about any other negative consequences down the road. Any thoughts out there from someone much wiser than I?