Before you ask, you cannot hide a table from the PowerPivot window in V1. Sorry.
We had to save something for V2.

1. First, and I know this sounds dumb, but I have to point it out – you have to be using Excel 2010. PowerPivot does not run under earlier version of Excel.
2. Next ensure that you have the additional “Shared Features” option checked in your Office install options. We need this for VSTO support.
3. Next ensure that you have the COM add-ins to see whether it’s checked, if not check and try it again. You might see something like:

   

4. Check to see whether or not the PowerPivot for Excel add-in is disabled. If disabled, enable it and try again. Sometimes Excel won’t enable it by default, or you don’t accept the signing when the add-in first comes up after registration. Check whether the add-in is in disabled items list. You might be wondering “Why does Excel disable PowerPivot?” The answer is that if Excel believes that an add-in is interfering with the usage of Excel, it disables the add-in. This could be something as simple as a delay in some startup code, i.e. you hit a network ‘hiccup’ at just the wrong time, or something like that.
5. If you still cannot get a valid error message, please try this
   • Open My Computer Properties
   • Click on Advanced Tab
   • Click on the Environmental Variable
   • Click on New User Variable
   • Add VSTO_SUPPRESSDISPLAYALERTS with value 0 press OK
   • Repair PowerPivot For Excel from add/remove program
   • Open Excel again, it will prompt an error message – that might lead you to a better understanding of the problem.

Enjoy!

Answer: Yup — that is a technical term.  You can use a schema.ini file in the same directory as the imported text file to specify all kinds of things that aren’t available through the PowerPivot UI, including fixed column rather than delimited text file format.  Here’s a web page with the info:

http://msdn.microsoft.com/en-us/library/ms709353(VS.85).aspx

(Thanks to Ron Pihlgren for this solution. Ron is the PowerPivot client test lead – and his blog is included in my blogroll.)

Enjoy.

1. The result set must have a name associated with each column. If you are not returning the column name, then you must assign an SQL alias to the column. Some query tools allow you to work with ordinal numbers for the columns; some query tools assign a name based on the ordinal (e.g. COLUMN_42); some query tools use a combination of the two. The add-in (and the SSAS engine) does not not – it directly binds to the column name.
2. You cannot have duplicate column names. Each column name must be unique.
3. You cannot return multiple rowsets. The client add-in only deals with a single rowset. Some tools allow you to return multiple rowsets but only deal with first one; or the last one. In the client add-in, you must have only a single return rowset. If you are entering queries via SQL then this is typically not a problem – but it has serious complications if you are using stored procedures. If you don’t use “SET NOCOUNT ON” at the beginning of your stored procedure, then a rowset is returned for each SELECT expression, even if that expression is just setting a variable. Thus you must have a “SET NOCOUNT NO” at the start of your stored procedure or the stored procedures are likely to fail with the client add-in.

I am just sharing the love here . . . the end result is that you might not be able to use all of your existing queries and stored procedures with the PowerPivot Excel client add-in. Being for-warned is for-armed.

And “Oh…” another possibility issue that you might run into is support for variant datatype. The rowset previewer can handle variant data — but the Engine cannot.

Enjoy.

See: http://blogs.msdn.com/powerpivot/archive/2010/04/07/fix-for-powerpivot-expiration-released.aspx

So where to begin . . . Being a geek, let’s start off with a technical topic. When you are running in a 64-bit process, then you can only use dlls and other executables that are build as native 64-bit applications. Therefore whatever our choice, 32-bit or 64-bit, the ‘bit-ness’ of our approach has to hold for the entire process. For example, if we pick 64-bit, then we need the 64-bit version of Excel 2010, we need the 64-bit versions of any add-ins, such as PowerPivot for Excel, and we need 64-bit versions of any OLE DB providers or ODBC drivers (using the 64-bit version of the OLE DB Provider for ODBC here). So let’s keep that in mind.

Ok, here we go:

Pro for 32-bit:

• It does not require an upgrade to a new OS. While yes, Windows 64-bit is still Windows, there are subtle differences between them.
• Likewise, it does not require new PCs. Depending on what your PCs are, they might not be capable of running 64-bit or may not have the capacity to make use of the 64-bit address space, e.g. they might only have 2GB of memory.
• There is better availability of add-ins and other components on 32-bit. Your existing add-ins will continue to work. For example, if we want to run the Microsoft Communicator add-in to Outlook 2010, then there is only a 32-bit version available. The installation of 32-bit verses 64-bit is at the Office “level” – you cannot have a 32-bit version of Outlook and a 64-bit version of Excel.

An excellent example of this limitation is that the Data Mining add-in for Excel is only available as a 32-bit version. Therefore if you need to run the data mining add-in then you must install Excel 32-bit. The larger dataset and performance improvements of 64-bit are not available to you.

• Likewise there is better availability of data providers on 32-bit. This can be important, particularly if you are using the PowerPivot mashup capability, then being able to use older legacy ODBC drivers is important. Some of those ODBC drivers are available in 64-bit versions (for example, there is a 64-bit version of the SQL Server OLE DB provider), but not all of them. Remember that you cannot mix ‘bit-ness’. If you install the 64-bit version of Excel, then you must use the 64-bit versions of any data providers. But this can be a double edged sword. Data refresh on the server is a 64-bit only environment. Therefore you could easily back yourself back into a corner by selecting a data provider that is available in 32-bit on the PowerPivot for Excel client – but is not available for the 64-bit server and thus you cannot use the data refresh facility on the server. The workaround for a situation like this can be problematic – it is to install a 32-bit version of SSRS and use the data feeds feature to get access to the data. The 32-bit server running Reporting Services is the ‘link’ via to the 32-bit provider. Or you could use a linked server in a similar 64-bit server connecting through a 32-bit server. Kind of a hack if you ask me.
• Lastly, an advantage of 32-bit is that you can run Office 2007 and Office 2010 side-by-side on the same 32-bit desktop. This is not possible with 64-bit because there is no 64-bit version of Office 2007 (we need a common registry hive to have the side-by-side work).

Pros for 64-bit:

• Let’s start with the biggest advantage first – you can handler larger datasets with 64-bit. You can save an Excel workbook with embedded PowerPivot data in it up to 2GB of embedded data. This represents 4GB of in-memory data. In the 32-bit world, you will find that the largest Excel workbook with embedded PowerPivot data is about 300-400MB. This is because in the 32-bit world, the 2GB virtual address space has to handle Excel, plus any add-ins including the PowerPivot for Excel add-in, plus the PowerPivot vertipaq in-memory engine, plus its data structures, dlls, etc . . . thus you will find the largest in-memory data is about 600-800MB – and that translates to a workbook of 300-400MB. Now, it may be that this is large enough for all of your user data, and you may even have a set a lower limit for the SharePoint maximum file size upload. Out-of-the-box PowerPivot for SharePoint in a “New Server” configuration sets the maximum file upload to 200MB. But if you want to go larger, you may quickly find that 32-bit just isn’t large enough for the datasets that end-users need.
• There are some performance gains at the OS level as applications grow beyond 2GB. While this might not be an issue with most desktop applications such as Office, it is quite apparent in larger applications that push the computing power of the desktop – and those benefit from not having to page virtual address space to disk as its memory usage increases. No knowing if your desktop users might be using one of these ‘power’ applications on their desktop it is hard to establish if they will see a performance gain in going to 64-bit, but there are some apps that do.

Thus you have some interesting choices ahead of yourself as we all walk the path of the Brave New World of 64-bit on the desktop. Let’s just hope that we can have some fun while we struggle with it.

Enjoy.