Solved

Parameterized OpenDataSource call

Posted on 2004-08-18
6
715 Views
Last Modified: 2012-05-05
Hello,

I need to pass as a parameter the "Data Source" portion of the OpenDataSource call:

SELECT @foo = col1 FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0', 'Data Source="c:\foo.xsl";User ID=Admin;Password=;Extended properties=Excel 8')...sheet1

the "c:\foo.xsl" portion above needs to be in a variable.

I've tried the following:

set @FileName = 'c:\foo.xls'
SELECT @foo = col1 FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0', 'Data Source=' + @FileName + ';User ID=Admin;Password=;Extended properties=Excel 8')...sheet1

but I get the error:

Server: Msg 170, Level 15, State 1, Line 7
Line 7: Incorrect syntax near '+'.

I'm new to SQL Server so any help would be greatly appreciated!

Thanks.




0
Comment
Question by:pennypiper
  • 3
  • 2
6 Comments
 
LVL 12

Expert Comment

by:patrikt
ID: 11838498
Procedures and functiopns don't like expressions.

Build string first and then pass it to OpenDataSource.

set @FileName = 'c:\foo.xls'
set @dsn='Data Source=' + @FileName+';User ID=Admin;Password=;Extended properties=Excel 8'
SELECT @foo = col1 FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0', @dsn)...sheet1
0
 

Author Comment

by:pennypiper
ID: 11838613
Hello,

When I run the above, I get the following error:

Server: Msg 170, Level 15, State 1, Line 15
Line 15: Incorrect syntax near '@dsn'.

with line 15 being this line:
SELECT @foo = col1 FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0', @dsn)...sheet1
                 
I've declared @dsn as:  declare @dsn varchar(400)

Is it something obvious I'm missing?

Thanks.


0
 
LVL 142

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 11838650
Actually, OpenDataSource (as well the other functions related) do not accept ANY variables, only fixed string.
Solution is to put all into dynamic SQL:

declare @sql varchar(1000)
set @sql = '
declare @foo ...
SELECT @foo = col1 FROM OpenDataSource( ''Microsoft.Jet.OLEDB.4.0'', ''Data Source="' + @yourfile + '";User ID=Admin;Password=;Extended properties=Excel 8'')...sheet1
'
exec (@sql)

Now, note that @foo is declared inside the dynamic sql, so you won't be able to access it from outside. To solve THAT, you will need to use xp_executesql:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_ea-ez_2h7w.asp

Cheers
0
Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

 

Author Comment

by:pennypiper
ID: 11839335
Hello,

Thanks for the information about xp_executesql.  I changed the code to use xp_executesql and it works in the following case:

declare @result varchar(200)

set @SQLString = N'SELECT @foo = col1
FROM      OpenDataSource( ' + '''' + 'Microsoft.Jet.OLEDB.4.0' + '''' + ',' + '''' + 'Data Source="' + 'c:\excel\foo.xls' + '";User ID=Admin;Password=;Extended properties=Excel 8.0'+'''' + ')...sheet1'

SET @ParmDefinition = N'@foo varchar(30) OUTPUT'

EXECUTE sp_executesql
@SQLString,
@ParmDefinition,
@foo=@result OUTPUT
SELECT @result

@result does indeed contain the correct information.  However, getting back to my original question, what I'd *really* like to do is replace the 'c:\excel\foo.xsl' with a variable.  If I add an input variable called 'myfile':

declare @result varchar(200)
declare @FileName varchar(200)
set @FileName = 'c:\foo.xls'

set @SQLString = N'SELECT @foo = col1
FROM      OpenDataSource( ' + '''' + 'Microsoft.Jet.OLEDB.4.0' + '''' + ',' + '''' + 'Data Source="' + @myfile + '";User ID=Admin;Password=;Extended properties=Excel 8.0'+'''' + ')...sheet1'

SET @ParmDefinition = N'@foo varchar(30) OUTPUT,
                                     @myfile varchar(200)'

EXECUTE sp_executesql
@SQLString,
@ParmDefinition,
@myfile=@FileName,
@foo=@result OUTPUT
SELECT @result

it fails:
Server: Msg 137, Level 15, State 2, Line 46
Must declare the variable '@myfile'.

which makes sense because the scope of @myfile is wrong.  So, I guess my new question is: how do I quote the variable @myfile to get SQL Server to expand it at within 'SQLString'?

Thanks for your help!



0
 
LVL 142

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 500 total points
ID: 11839402
The way you wanted to do is would put back the orignial problem inside the sql.
the thing is that you need to build the complete connecting string (using @FileName) and NOT passing that information inside the dynamic SQL:

declare @result varchar(200)
declare @FileName varchar(200)
set @FileName = 'c:\foo.xls'

set @SQLString = N'SELECT @foo = col1
FROM     OpenDataSource( ' + '''' + 'Microsoft.Jet.OLEDB.4.0' + '''' + ',' + '''' + 'Data Source="' + @FileName + '";User ID=Admin;Password=;Extended properties=Excel 8.0'+'''' + ')...sheet1'

SET @ParmDefinition = N'@foo varchar(30) OUTPUT'

EXECUTE sp_executesql
@SQLString,
@ParmDefinition,
@foo=@result OUTPUT
SELECT @result

CHeers
0
 

Author Comment

by:pennypiper
ID: 11839611
Success!  

I discovered I had a type-o in my code: the "hard-coded" directory was "c:\excel\foo.xsl" but  my variable @FileName was set to "c:\foo.xsl".  Changing that fixed my problem.  Thanks for your help!  
0

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
migration MS SQL database to Oracle 30 62
Find results from sql within a time span 11 33
Rename a column in the output 3 14
Proper Case SQL Command 2 13
When you hear the word proxy, you may become apprehensive. This article will help you to understand Proxy and when it is useful. Let's talk Proxy for SQL Server. (Not in terms of Internet access.) Typically, you'll run into this type of problem w…
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

832 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question