Can we have a folder as input path for SSIS package, and process all files within it?

Can we have a folder as input path for SSIS package, and process all files within it?

My client wish to run a batch process where in a folder he will put number of files, which needs to be processed by ssis package. Is that possible directly in ssis?

Alternate solution that I have thought of is...
1. user will copy all files in c:\folder1
2. a .NET component will
2.1 pick up files from folder1 one by one (process all files in the folder)
2.2 will copy that file in c:\INPUT folder by the name in.xls
2.3 will call SSIS package
2.4 SSIS package will process the file in.xls
2.5 end loop..go back to step 2.1

Do we have any othre way of achieving this task? Any suggestions are welcome. Thanks in advanc.

Regards,
MS Guy

MS Guy wrote:

Can we have a folder as input path for SSIS package, and process all files within it?

My client wish to run a batch process where in a folder he will put number of files, which needs to be processed by ssis package. Is that possible directly in ssis?

Alternate solution that I have thought of is...
1. user will copy all files in c:\folder1
2. a .NET component will
2.1 pick up files from folder1 one by one (process all files in the folder)
2.2 will copy that file in c:\INPUT folder by the name in.xls
2.3 will call SSIS package
2.4 SSIS package will process the file in.xls
2.5 end loop..go back to step 2.1

Do we have any othre way of achieving this task? Any suggestions are welcome. Thanks in advanc.

Regards,
MS Guy

There's a few things that make the answer "It depends" but there's a few things you should look at:
1) MULTIFLATFILE connection manager. This connection manager points to a colelction of files (usually all files in a folder) and you can then apply a single operation (such as loading the contents of all those files into a table) in one step. Usually the metadata of the files needs to be the same - it depends on what operation you're applying.

2) Use a Foreach loop container to loop over the files and process them individually. There's a bit more guidance on this here: http://blogs.conchango.com/jamiethomson/archive/2005/05/30/1489.aspx plus Darren and Allan have some good stuff on this at www.sqlis.com.

-Jamie

Can we add tooltip to the Reports available in Report Manager?

Hi,
In my Report Manager window, I have created the Folder "Test" and under this folder I have uploaded 2 .rdl file. When I am placing the cursor over the Report Items, it shows 'Items in Test' instead I want to show Some Other Message.

Is it possible?

ThanksI'm sorry, this is not possible.

-Daniel

Can we add tooltip to the Reports available in Report Manager?

Hi,
In my Report Manager window, I have created the Folder "Test" and under this folder I have uploaded 2 .rdl file. When I am placing the cursor over the Report Items, it shows 'Items in Test' instead I want to show Some Other Message.

Is it possible?

ThanksI'm sorry, this is not possible.

-Daniel

Can SQL Server 7.0 handle a SQL Server 2000 mdf?

I've got MSDE, SQL Server 7.0, installed. I want to handle an .mdf
developed by someone else so I loaded the .mdf into my /DATA folder.
But, MSDE/ODBC can't see the database. I subsequently discovered that
it was created using SQL Server 2000. Is this the reason that my MSDE
7.0 doesn't see the .mdf? If so, how can I use this database with my
7.0? Backup from 2000, restore to 7.0?

Thanks for any help.Mike Watson (mike@.connectingsoftware.it) writes:
> I've got MSDE, SQL Server 7.0, installed. I want to handle an .mdf
> developed by someone else so I loaded the .mdf into my /DATA folder.
> But, MSDE/ODBC can't see the database. I subsequently discovered that
> it was created using SQL Server 2000. Is this the reason that my MSDE
> 7.0 doesn't see the .mdf? If so, how can I use this database with my
> 7.0? Backup from 2000, restore to 7.0?

Well, there's actually two problems here.

The fact that MSDE/ODBC can't see the database has nothing to do with
the versions of SQL Server. Putting a file into your data directory has
no effect. You would have to do sp_attach_db to make the database available.
And for sp_attach_db the .mdf is not sufficient; you would need the log
file too. There is sp_attach_single_file_db for this situation, but the
database must have been shut down cleanly for this. (Well, this applies
to sp_attach_db as well as I recall.)

But for all this to work, the target server must be the same version or
later than the source server, so you can never do anything with that file
without access to SQL 2000. To restore that database on SQL 7, you would
have to script it and bulk out all data. And if the database makes use
of features not in SQL 7, not even this method would work.

Since MSDE for SQL 2000 is freely available, it appears to be a good idea
to download and install it.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <esquel@.sommarskog.se> wrote in message news:<Xns9619844A49F0FYazorman@.127.0.0.1>...
> Mike Watson (mike@.connectingsoftware.it) writes:
> > I've got MSDE, SQL Server 7.0, installed. I want to handle an .mdf
> > developed by someone else so I loaded the .mdf into my /DATA folder.
> > But, MSDE/ODBC can't see the database. I subsequently discovered that
> > it was created using SQL Server 2000. Is this the reason that my MSDE
> > 7.0 doesn't see the .mdf? If so, how can I use this database with my
> > 7.0? Backup from 2000, restore to 7.0?
> Well, there's actually two problems here.
> The fact that MSDE/ODBC can't see the database has nothing to do with
> the versions of SQL Server. Putting a file into your data directory has
> no effect. You would have to do sp_attach_db to make the database available.
> And for sp_attach_db the .mdf is not sufficient; you would need the log
> file too. There is sp_attach_single_file_db for this situation, but the
> database must have been shut down cleanly for this. (Well, this applies
> to sp_attach_db as well as I recall.)
> But for all this to work, the target server must be the same version or
> later than the source server, so you can never do anything with that file
> without access to SQL 2000. To restore that database on SQL 7, you would
> have to script it and bulk out all data. And if the database makes use
> of features not in SQL 7, not even this method would work.
> Since MSDE for SQL 2000 is freely available, it appears to be a good idea
> to download and install it.

Thank you Erland, for your answer. We've got the log file. So,
following your advice I will look for and install MSDE 2000. After
that I presume I have to run the 'sp_attach_db' procedure to make the
db available to MSDE 2000 so that I can create an ODBC to see it from
Access 2000. Could you please confirm if that is correct?

Mike Watson|||Mike Watson (mike@.connectingsoftware.it) writes:
> Thank you Erland, for your answer. We've got the log file. So,
> following your advice I will look for and install MSDE 2000. After
> that I presume I have to run the 'sp_attach_db' procedure to make the
> db available to MSDE 2000 so that I can create an ODBC to see it from
> Access 2000. Could you please confirm if that is correct?

That should work just fine.

Once you have MSDE 2000 up, do a SELECT @.@.version, and make sure that
you have at least 8.00.760, so you have SP3 and the fix for the Slammer
worm.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <esquel@.sommarskog.se> wrote in message news:<Xns961AE57BC3805Yazorman@.127.0.0.1>...
> Mike Watson (mike@.connectingsoftware.it) writes:
> > Thank you Erland, for your answer. We've got the log file. So,
> > following your advice I will look for and install MSDE 2000. After
> > that I presume I have to run the 'sp_attach_db' procedure to make the
> > db available to MSDE 2000 so that I can create an ODBC to see it from
> > Access 2000. Could you please confirm if that is correct?
> That should work just fine.
> Once you have MSDE 2000 up, do a SELECT @.@.version, and make sure that
> you have at least 8.00.760, so you have SP3 and the fix for the Slammer
> worm.

Erland,

I've downloaded MSDE 2000 (Italian version), expanded the zip, read
the readme.txt, checked the things they tell me to check. I started
the setup with:

setup SAPWD="password" SECURITYMODE=SQL

The install fails with roughly 3 - 5 seconds remaining with following
message:

"Impossible to configure the Server. For further information examine
the error logs..."

The last 2 messages in the log are:

Warning: override, autoexec procedures skipped.

and

Closing down SQL Server because of a interruption request from the
Service control handler (my translation)

I can't see what's going wrong. Can you help me?

Mike Watson|||Mike Watson (mike@.connectingsoftware.it) writes:
> I've downloaded MSDE 2000 (Italian version), expanded the zip, read
> the readme.txt, checked the things they tell me to check. I started
> the setup with:
> setup SAPWD="password" SECURITYMODE=SQL
> The install fails with roughly 3 - 5 seconds remaining with following
> message:
> "Impossible to configure the Server. For further information examine
> the error logs..."
> The last 2 messages in the log are:
> Warning: override, autoexec procedures skipped.
> and
> Closing down SQL Server because of a interruption request from the
> Service control handler (my translation)
> I can't see what's going wrong. Can you help me?

Unfortunately, I have no experience of running the MSDE setup, so
there is not much I can assist with.

Do you run the setup on the machine where you already have MSDE 7, or
do you run it on some other machine?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <esquel@.sommarskog.se> wrote in message news:<Xns961BF3EFC447BYazorman@.127.0.0.1>...
> Mike Watson (mike@.connectingsoftware.it) writes:
> > I've downloaded MSDE 2000 (Italian version), expanded the zip, read
> > the readme.txt, checked the things they tell me to check. I started
> > the setup with:
> > setup SAPWD="password" SECURITYMODE=SQL
> > The install fails with roughly 3 - 5 seconds remaining with following
> > message:
> > "Impossible to configure the Server. For further information examine
> > the error logs..."
> > The last 2 messages in the log are:
> > Warning: override, autoexec procedures skipped.
> > and
> > Closing down SQL Server because of a interruption request from the
> > Service control handler (my translation)
> > I can't see what's going wrong. Can you help me?
> Unfortunately, I have no experience of running the MSDE setup, so
> there is not much I can assist with.
> Do you run the setup on the machine where you already have MSDE 7, or
> do you run it on some other machine?

Erland,

I'm doing the install on another machine where there is no previous
copy of SQL or MSDE. It's Windows XP.

Mike Watson|||Mike Watson (mike@.connectingsoftware.it) writes:
> I'm doing the install on another machine where there is no previous
> copy of SQL or MSDE. It's Windows XP.

Darn! Then I can't even suggest that as a remedy. I believe that there
is a newsgroup microsoft.public.sqlserver.msde.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp