Your question has three parts to it that you can lookup:

1) Fetching a flat file. This is one of the import types supported in SSIS.

2) Accessing a website or web server to retrieve a file. This depends on
your configuration of SSIS. Is the database on the same server as IIS? Are
you trying to access a file on some other website?

SSIS is going to need appropriate permissions to get at the file. If you
don't have control of the file and permissions, SSIS isn't going to be able
to work with it.

3) Automation of executing the package. Is this supposed to execute from the
website, or are you automating an action to retrieve files and process them?

If you're doing an automated search, parse and action type of process you
could build a dotnet service that could be automated to do this. I would have
the process bring the file into a local structure where you control
permissions, run SSIS to parse, then kill the file or archive it. This
service could be automated via the scheduler to run when you want it. No
hands on needed. You would also want to write some sort of logging of
activity and success/failure.

"matt" wrote:

Your question has three parts to it that you can lookup:

1) Fetching a flat file. This is one of the import types supported in SSIS.

2) Accessing a website or web server to retrieve a file. This depends on
your configuration of SSIS. Is the database on the same server as IIS? Are
you trying to access a file on some other website?

SSIS is going to need appropriate permissions to get at the file. If you
don't have control of the file and permissions, SSIS isn't going to be able
to work with it.

3) Automation of executing the package. Is this supposed to execute from the
website, or are you automating an action to retrieve files and process them?

If you're doing an automated search, parse and action type of process you
could build a dotnet service that could be automated to do this. I would have
the process bring the file into a local structure where you control
permissions, run SSIS to parse, then kill the file or archive it. This
service could be automated via the scheduler to run when you want it. No
hands on needed. You would also want to write some sort of logging of
activity and success/failure.

"matt" wrote:

Your question has three parts to it that you can lookup:

1) Fetching a flat file. This is one of the import types supported in SSIS.

2) Accessing a website or web server to retrieve a file. This depends on
your configuration of SSIS. Is the database on the same server as IIS? Are
you trying to access a file on some other website?

SSIS is going to need appropriate permissions to get at the file. If you
don't have control of the file and permissions, SSIS isn't going to be able
to work with it.

3) Automation of executing the package. Is this supposed to execute from the
website, or are you automating an action to retrieve files and process them?

If you're doing an automated search, parse and action type of process you
could build a dotnet service that could be automated to do this. I would have
the process bring the file into a local structure where you control
permissions, run SSIS to parse, then kill the file or archive it. This
service could be automated via the scheduler to run when you want it. No
hands on needed. You would also want to write some sort of logging of
activity and success/failure.

"matt" wrote:

Your question has three parts to it that you can lookup:

1) Fetching a flat file. This is one of the import types supported in SSIS.

2) Accessing a website or web server to retrieve a file. This depends on
your configuration of SSIS. Is the database on the same server as IIS? Are
you trying to access a file on some other website?

SSIS is going to need appropriate permissions to get at the file. If you
don't have control of the file and permissions, SSIS isn't going to be able
to work with it.

3) Automation of executing the package. Is this supposed to execute from the
website, or are you automating an action to retrieve files and process them?

If you're doing an automated search, parse and action type of process you
could build a dotnet service that could be automated to do this. I would have
the process bring the file into a local structure where you control
permissions, run SSIS to parse, then kill the file or archive it. This
service could be automated via the scheduler to run when you want it. No
hands on needed. You would also want to write some sort of logging of
activity and success/failure.

"matt" wrote:

Your question has three parts to it that you can lookup:

1) Fetching a flat file. This is one of the import types supported in SSIS.

2) Accessing a website or web server to retrieve a file. This depends on
your configuration of SSIS. Is the database on the same server as IIS? Are
you trying to access a file on some other website?

SSIS is going to need appropriate permissions to get at the file. If you
don't have control of the file and permissions, SSIS isn't going to be able
to work with it.

3) Automation of executing the package. Is this supposed to execute from the
website, or are you automating an action to retrieve files and process them?

If you're doing an automated search, parse and action type of process you
could build a dotnet service that could be automated to do this. I would have
the process bring the file into a local structure where you control
permissions, run SSIS to parse, then kill the file or archive it. This
service could be automated via the scheduler to run when you want it. No
hands on needed. You would also want to write some sort of logging of
activity and success/failure.

"matt" wrote:

Your question has three parts to it that you can lookup:

1) Fetching a flat file. This is one of the import types supported in SSIS.

2) Accessing a website or web server to retrieve a file. This depends on
your configuration of SSIS. Is the database on the same server as IIS? Are
you trying to access a file on some other website?

SSIS is going to need appropriate permissions to get at the file. If you
don't have control of the file and permissions, SSIS isn't going to be able
to work with it.

3) Automation of executing the package. Is this supposed to execute from the
website, or are you automating an action to retrieve files and process them?

If you're doing an automated search, parse and action type of process you
could build a dotnet service that could be automated to do this. I would have
the process bring the file into a local structure where you control
permissions, run SSIS to parse, then kill the file or archive it. This
service could be automated via the scheduler to run when you want it. No
hands on needed. You would also want to write some sort of logging of
activity and success/failure.

"matt" wrote:

Your question has three parts to it that you can lookup:

1) Fetching a flat file. This is one of the import types supported in SSIS.

2) Accessing a website or web server to retrieve a file. This depends on
your configuration of SSIS. Is the database on the same server as IIS? Are
you trying to access a file on some other website?

SSIS is going to need appropriate permissions to get at the file. If you
don't have control of the file and permissions, SSIS isn't going to be able
to work with it.

3) Automation of executing the package. Is this supposed to execute from the
website, or are you automating an action to retrieve files and process them?

If you're doing an automated search, parse and action type of process you
could build a dotnet service that could be automated to do this. I would have
the process bring the file into a local structure where you control
permissions, run SSIS to parse, then kill the file or archive it. This
service could be automated via the scheduler to run when you want it. No
hands on needed. You would also want to write some sort of logging of
activity and success/failure.

"matt" wrote: