AmosFiveSix.com

Here are some more issued we encountered when moving up to a 64-Bit SQL Server 2005. 

 64-Bit Product level is insufficient errors - This happened to us because we didn't have full SSIS installed on the server, just the development version.

• Why do I get "product level is insufficient..." error when I run my SSIS package?
• Where is my SQL Server Integration Services package running?
• SSIS - DTS_E_PRODUCTLEVELTOLOW Error
• MSDN: DTS_E_PRODUCTLEVELTOLOW

64-Bit Offline Mode is True error - This just required a regsvr on a DLL.

• MSKB: On a computer that has a 64-bit processor, you receive an error message in SQL Server Management Studio when you connect to SQL Server 2005 Integration Services or when you create or edit a maintenance plan
• DestinationConnectionExcel and OfflineMode
• Getting Error in 32bit DTEXEC on 64bit machine

64-Bit Linked Server Error - 64-bit SQL Server calls a stored procedure that doesn't exist on linked SQL 2000 servers. Creating a wrapper around a similar existing procedure fixed the problem for us.

• Issue with 64-bit SQL Server using SQL 2000 linked server
• Linking 64-bit SQL2k5 to 32-bit SQL2k ... or, How to Avoid Wasting 10 Days Waiting For Straight Answers

If you've just switched to the 64-bit version of SQL Server and have SSIS packages that access Excel or Access, you may find that you packages stop working. That's because the JET driver that is used to access Excel and Access is 32-bit only. SSIS normally uses the 64-bit DTExec to run SSIS packages, it has not access to the 32-bit drivers. Here are some articles with all the details and work arounds

Quick Reference: SSIS in 32- and 64-bits
http://toddmcdermid.blogspot.com/2009/10/quick-reference-ssis-in-32-and-64-bits.html

SSIS Snack: SSIS, Excel, and a 64-bit OS
http://sqlblog.com/blogs/andy_leonard/archive/2010/01/19/ssis-snack-ssis-excel-and-a-64-bit-os.aspx 

64-bit Excel Driver in Microsoft Office 14
http://dougbert.com/blogs/dougbert/archive/2009/08/28/64-bit-excel-driver-in-microsoft-office-14.aspx

Excel (and Access) Data Source in 64-bit environment
http://ssis.trigonblue.com/Excelin64bitenv/tabid/523/Default.aspx

This information is based on the United States Postal Service standard abbreviations for states and territories: http://www.usps.com/ncsc/lookups/usps_abbreviations.html

If your data needs to include addresses for the continental United States only, it's best to check if the address's state is included in the list of continental states, rather than checking if the state is not in the list of non-continental states.

For example, this incorrect SQL snipit allows addresses in Guam and other territories to pass through:

WHERE store.State NOT IN ('AK','HI','VI','PR')

This is the correct code to check for continental United States:

WHERE store.State IN ('AL', 'AZ', 'AR', 'CA', 'CO', 'CT', 'DE', 'DC', 'FL', 'GA', 'ID', 'IL', 'IN', 'IA', 'KS', 'KY', 'LA', 'ME', 'MD', 'MA', 'MI', 'MN', 'MS', 'MO', 'MT', 'NE', 'NV', 'NH', 'NJ', 'NM', 'NY', 'NC', 'ND', 'OH', 'OK', 'OR', 'PA', 'RI', 'SC', 'SD', 'TN', 'TX', 'UT', 'VT', 'VA', 'WA', 'WV', 'WI', 'WY') AND store.Country = 'United States'