FTP Task and Temporary Internet Files

I have created a package within SQL Server SSIS which includes an FTP Task, deployed it to our SQL Server (2005 SP1) msdb database and am running this job under SQL Agent on Windows Server 2003. Due to company security requirements this job has to be run under a service account within SQL Agent. The problem with this is that even though a directory is specified within the FTP Task to place any downloaded files into, the files are first written to the TIF (Temporary Internet Files) directory of "Default User" which is on the system drive. Based on corporate standards the system drive (C:) on our servers are only configured with enough space for the OS and other system files. All of the files being transferred are compressed, but some are still well over 1GB in size. The result is that many of our downloads are failing due to the system drive running out of space.

I have attempted to run IE by using "Run As" with the service account credentials, and have changed the location of the TIFs to a different drive, rebooted and verified the settings. When the SQL Agent job was run again, the files were still being written to the "Default User" directory on the system drive. I also created a new template account with the TIFs pointing to a non-system drive and used the User Profiles functionality of System Properties to copy the new template account to "Default User", but still the files are being written to the system drive.

My questions are:

is there a way to stop the FTP Task from using TIF (i.e. just directly write the file to the location specified) is there a best practice around how to setup a service account and have it create a proper user profile that can be managed separate from "Default User" short of specifying during the OS install, is there a way to move the "Default User" profile directory to a different drive

In case anyone else runs into this situation, I thought I would describe what ended up happening.

The page file was moved off of the system drive; otherwise the server was locking up when the system drive ran out or space. Now that the page file is on a separate drive, once the system drive runs completely out of space during a download the FTP Task (or whatever is managing the FTP transfer in the background) just starts writing the file being downloaded to the specified location (apparently it's smart enough to stop caching without crashing once there is no space left). Once the file that filled up the system drive completes downloading then it is removed from the TIF; normally the files aren't removed from the TIF until the entire package finishes execution.

The only downside to this is that the time period between the system drive becoming full and the file download completing, there are difficulties with logging into the machine. The difficulty is that some error messages are displayed and not being able to use your user profile - the Default User profile is used instead.

|||I am experiencing a similar problem. Does anybody out there know how to address this issue please?

Chris Lund, Software Installation Limited, Manchester UKsql

FTP authentication information does not persist when deploying packages

I am trying to deploy a SSIS package which includes a FTP task. It works fine on the machine it was developed . When deploying the package on a production server, all other config changes work, but the FTP task is failing, with authentication error.

any help on how to persist the data would be appreciated

thanks

Maybe it's because the password was stored encrypted and couldn't be decrypted on the new machine... This is quite common and happens often when moving a package from machine to machine.

As far as I know you can get around this by using package passwords instead of the normal encryption. You can also save a package without encryption (what is not recommended...) or use a configuration to push the password back into the package i.e. using an XML file (but then the password is unencrypted in the XML)...

Freetexttable Not Finding Inflectional Forms

We're using SQL Server 2005 service pack 1. It was my understanding that
FreeTextTable automatically includes inflectional forms. We're not able to
get any inflectional forms of words during the search (even if we use
Contains with the special syntax). Are we missing something in the server
configuration? Or is there a bug somewhere?
Thanks,
Krip
Are you wrapping your freetext search in double quotes - this disables the
stemming (inflectional search)?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Krip" <amk@.kynetix.com> wrote in message
news:9E599183-45E3-4CA8-8628-540038B91EB6@.microsoft.com...
> We're using SQL Server 2005 service pack 1. It was my understanding that
> FreeTextTable automatically includes inflectional forms. We're not able
> to get any inflectional forms of words during the search (even if we use
> Contains with the special syntax). Are we missing something in the server
> configuration? Or is there a bug somewhere?
> Thanks,
> Krip
>
|||Hilary,
Nope, not wrapping with double quotes. Here's the clause:
INNER JOIN FreeTextTable(myTable, myField, 'tests') as FTT
I have 'test' in the data but 'tests' doesn't find it. That's just one
example (fox works but not foxes; landed works but not landing).
The following doesn't work either:
SELECT *
FROM myTable
WHERE CONTAINS(*, 'FORMSOF (INFLECTIONAL, foxes)')
Also, I've now installed SP2 and rebuilt the catalag - same issue.
Is there some place to enable inflectional forms? Or is there a dictionary
to populate?
Thanks,
Krip
|||Perhaps it is a language issue, what does this return? sp_configure 'default
full-text language'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Krip" <amk@.kynetix.com> wrote in message
news:3424FB65-92CF-40BA-B08E-436298FABB96@.microsoft.com...
> Hilary,
> Nope, not wrapping with double quotes. Here's the clause:
> INNER JOIN FreeTextTable(myTable, myField, 'tests') as FTT
> I have 'test' in the data but 'tests' doesn't find it. That's just one
> example (fox works but not foxes; landed works but not landing).
> The following doesn't work either:
> SELECT *
> FROM myTable
> WHERE CONTAINS(*, 'FORMSOF (INFLECTIONAL, foxes)')
> Also, I've now installed SP2 and rebuilt the catalag - same issue.
> Is there some place to enable inflectional forms? Or is there a
> dictionary to populate?
> Thanks,
> Krip
>
>
|||Hilary,
It returns the following:
name: default full-text language
minimum: 0
maximum: 2147483647
config_value: 1033
run_value: 1033
Thanks for your help,
Krip

FREE SOFTWARE!

DB Ghost - the scripter, scripts out all your database objects as individual scripts. This includes static data, so you can select your static data tables and "the scripter" will create a .SQL file containing all the insert statements for that table. Each
different object type will be created within it's own directory. DB Ghost - the scriptor can then add all these files into Visual SourceSafe mirroring the structure on your hard-drive as Directory to Project and source file to SourceSafe item.
So there you have it, a quick and painless way to script and save all your SQL Server database code into SourceSafe - just point and click.
Best of all though - it's free, just download the DB Ghost evaluation version (which is limited to thirty days) and DB Ghost - the scripter is included which never expires!
www.dbghost.com
Mark, spammers often use subjects such as yours within their posts. I =
almost did not open your post, but then I read your name and I figured =
that this message had a 95% chance of being legit so I took the chance =
and opened the post. You may want to submit another post that mentions =
your product in the subject line.
--=20
Keith
"mark baekdal" <anonymous@.discussions.microsoft.com> wrote in message =
news:B32097DF-10D3-4D4C-8C5C-965A46178E3D@.microsoft.com...
> DB Ghost - the scripter, scripts out all your database objects as =
individual scripts. This includes static data, so you can select your =
static data tables and "the scripter" will create a .SQL file containing =
all the insert statements for that table. Each different object type =
will be created within it's own directory. DB Ghost - the scriptor can =
then add all these files into Visual SourceSafe mirroring the structure =
on your hard-drive as Directory to Project and source file to SourceSafe =
item.
>=20
> So there you have it, a quick and painless way to script and save all =
your SQL Server database code into SourceSafe - just point and click.
>=20
> Best of all though - it's free, just download the DB Ghost evaluation =
version (which is limited to thirty days) and DB Ghost - the scripter is =
included which never expires!=20
>=20
> www.dbghost.com
>
|||thanks Keith, I'll follow your advice

Free database tool ~ DB Ghost - the scripter

DB Ghost - the scripter, scripts out all your database objects as individual scripts. This includes static data, so you can select your static data tables and "the scripter" will create a .SQL file containing all the insert statements for that table. Each
different object type will be created within it's own directory. DB Ghost - the scriptor can then add all these files into Visual SourceSafe mirroring the structure on your hard-drive as Directory to Project and source file to SourceSafe item.
So there you have it, a quick and painless way to script and save all your SQL Server database code into SourceSafe - just point and click.
Best of all though - it's free, just download the DB Ghost evaluation version (which is limited to thirty days) and DB Ghost - the scripter is included which never expires!
www.dbghost.com
But its not really free is it. Its a trial version of your software.
"mark baekdal" <anonymous@.discussions.microsoft.com> wrote in message
news:87390168-7861-4238-AB47-CDB3A281492F@.microsoft.com...
> DB Ghost - the scripter, scripts out all your database objects as
individual scripts. This includes static data, so you can select your static
data tables and "the scripter" will create a .SQL file containing all the
insert statements for that table. Each different object type will be created
within it's own directory. DB Ghost - the scriptor can then add all these
files into Visual SourceSafe mirroring the structure on your hard-drive as
Directory to Project and source file to SourceSafe item.
> So there you have it, a quick and painless way to script and save all your
SQL Server database code into SourceSafe - just point and click.
> Best of all though - it's free, just download the DB Ghost evaluation
version (which is limited to thirty days) and DB Ghost - the scripter is
included which never expires!
> www.dbghost.com
>
|||No Brian,
"DB Ghost - the scripter" really is free, no evaluation period, no cost - Free!
"DB Ghost" has an evaluation period and has a cost - "DB Ghost" is not free.
Two seperate exe's, doing different things, one which is free, one which is not.
Same MSI, two exe's. Download the DB Ghost evaluation and it'll come with the scripter which is free.
-- Bryan Oliver wrote: --
But its not really free is it. Its a trial version of your software.
"mark baekdal" <anonymous@.discussions.microsoft.com> wrote in message
news:87390168-7861-4238-AB47-CDB3A281492F@.microsoft.com...
> DB Ghost - the scripter, scripts out all your database objects as
individual scripts. This includes static data, so you can select your static
data tables and "the scripter" will create a .SQL file containing all the
insert statements for that table. Each different object type will be created
within it's own directory. DB Ghost - the scriptor can then add all these
files into Visual SourceSafe mirroring the structure on your hard-drive as
Directory to Project and source file to SourceSafe item.[vbcol=seagreen]
SQL Server database code into SourceSafe - just point and click.[vbcol=seagreen]
version (which is limited to thirty days) and DB Ghost - the scripter is
included which never expires![vbcol=seagreen]