Comments for Ben Sullins Tech http://bensullins.com Business Intelligence Ramblings and Opinions Fri, 05 Dec 2008 08:03:50 +0000 http://wordpress.org/?v=2.6.2 Comment on Adding Row Numbers Excel Sources in SSIS by sagar http://bensullins.com/adding-a-row-number-to-an-excel-source-in-ssis/#comment-35 sagar Wed, 29 Oct 2008 03:42:42 +0000 http://bensullins.com/?p=8#comment-35 I will not be able to use temp tables. I will not be able to use temp tables.

]]> Comment on Adding Row Numbers Excel Sources in SSIS by bsullins http://bensullins.com/adding-a-row-number-to-an-excel-source-in-ssis/#comment-34 bsullins Tue, 28 Oct 2008 16:00:36 +0000 http://bensullins.com/?p=8#comment-34 Hi Sagar, You are correct, the row_number() function is not supported in SQL Server 2000. In this case I would suggest inserting the data into a temp table with an identity field. Hope this helps! -Ben Hi Sagar,

You are correct, the row_number() function is not supported in SQL Server 2000. In this case I would suggest inserting the data into a temp table with an identity field. Hope this helps!

-Ben

]]> Comment on Adding Row Numbers Excel Sources in SSIS by sagar http://bensullins.com/adding-a-row-number-to-an-excel-source-in-ssis/#comment-33 sagar Tue, 28 Oct 2008 08:12:46 +0000 http://bensullins.com/?p=8#comment-33 Can you tell me if there is any solution for same problem using SQL Server 2000? I think row_number() wont work in 2000. Sagar Can you tell me if there is any solution for same problem using SQL Server 2000? I think row_number() wont work in 2000.

Sagar

]]> Comment on SQL Server Analysis Services (SSAS) Connection Properties by Reddy http://bensullins.com/sql-server-analysis-services-ssas-connection-properties/#comment-30 Reddy Thu, 02 Oct 2008 15:35:49 +0000 http://bensullins.com/?p=11#comment-30 Thanks buddy...that worked me Thanks buddy…that worked me

]]> Comment on SQL Server Analysis Services (SSAS) Connection Properties by bsullins http://bensullins.com/sql-server-analysis-services-ssas-connection-properties/#comment-20 bsullins Tue, 09 Sep 2008 18:57:17 +0000 http://bensullins.com/?p=11#comment-20 In SSIS I like the .Net provider for Execute SQL tasks because of the interface with the .Net data types and named parameters is much better, but in the data flows I generally use OLEDB because the .Net destination (SQL Server Destination) is only available when the SSIS code is on the same server as the destination database. In SSIS I like the .Net provider for Execute SQL tasks because of the interface with the .Net data types and named parameters is much better, but in the data flows I generally use OLEDB because the .Net destination (SQL Server Destination) is only available when the SSIS code is on the same server as the destination database.

]]> Comment on SQL Server Analysis Services (SSAS) Connection Properties by Daniel Upton http://bensullins.com/sql-server-analysis-services-ssas-connection-properties/#comment-19 Daniel Upton Tue, 09 Sep 2008 18:03:19 +0000 http://bensullins.com/?p=11#comment-19 Ben, Thanks for the insights. Question: When you connect BI Dev Studio to SQL Server (eg. for cube dev), do you prefer to use... * Native OLEDB\SQL Native Client (the default), or * .Net Providers\SQLClient Data Providers...? I've never had problems with the default, but I've been hearing that (at least for app-dev purposes), .Net may be superior. To see one such discussion thread, click on... http://www.vbforums.com/showthread.php?t=537137. Your thoughts, Ben? Ben,
Thanks for the insights. Question: When you connect BI Dev Studio to SQL Server (eg. for cube dev), do you prefer to use…

* Native OLEDB\SQL Native Client (the default), or
* .Net Providers\SQLClient Data Providers…?

I’ve never had problems with the default, but I’ve been hearing that (at least for app-dev purposes), .Net may be superior. To see one such discussion thread, click on…
http://www.vbforums.com/showthread.php?t=537137.

Your thoughts, Ben?

]]>