I have several DTS packages that import FoxPro data into SQL 2000. These
jobs create a temp file about the same size of the data that I am importing.
I call the DTS packages as a SQL job. If the job runs successfully then the
temp files are removed when it finishes, however if the job fails it leaves
the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
directory and I start to run low on disk space until I manually delete the
files.
Is there a way to direct where these files go? I would like to change this
to the D:\ where I have a lot more space.
Thanks
MikeNevermind. I found it. It is a windows configuration setting.
"Mike" <Mike@.Comcast.net> wrote in message
news:u7yCs%235MEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have several DTS packages that import FoxPro data into SQL 2000. These
> jobs create a temp file about the same size of the data that I am
importing.
> I call the DTS packages as a SQL job. If the job runs successfully then
the
> temp files are removed when it finishes, however if the job fails it
leaves
> the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
> directory and I start to run low on disk space until I manually delete the
> files.
> Is there a way to direct where these files go? I would like to change this
> to the D:\ where I have a lot more space.
> Thanks
> Mike
>
Showing posts with label foxpro. Show all posts
Showing posts with label foxpro. Show all posts
Friday, March 30, 2012
How to direct temp files for DTS packages
I have several DTS packages that import FoxPro data into SQL 2000. These
jobs create a temp file about the same size of the data that I am importing.
I call the DTS packages as a SQL job. If the job runs successfully then the
temp files are removed when it finishes, however if the job fails it leaves
the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
directory and I start to run low on disk space until I manually delete the
files.
Is there a way to direct where these files go? I would like to change this
to the D:\ where I have a lot more space.
Thanks
MikeNevermind. I found it. It is a windows configuration setting.
"Mike" <Mike@.Comcast.net> wrote in message
news:u7yCs%235MEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have several DTS packages that import FoxPro data into SQL 2000. These
> jobs create a temp file about the same size of the data that I am
importing.
> I call the DTS packages as a SQL job. If the job runs successfully then
the
> temp files are removed when it finishes, however if the job fails it
leaves
> the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
> directory and I start to run low on disk space until I manually delete the
> files.
> Is there a way to direct where these files go? I would like to change this
> to the D:\ where I have a lot more space.
> Thanks
> Mike
>sql
jobs create a temp file about the same size of the data that I am importing.
I call the DTS packages as a SQL job. If the job runs successfully then the
temp files are removed when it finishes, however if the job fails it leaves
the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
directory and I start to run low on disk space until I manually delete the
files.
Is there a way to direct where these files go? I would like to change this
to the D:\ where I have a lot more space.
Thanks
MikeNevermind. I found it. It is a windows configuration setting.
"Mike" <Mike@.Comcast.net> wrote in message
news:u7yCs%235MEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have several DTS packages that import FoxPro data into SQL 2000. These
> jobs create a temp file about the same size of the data that I am
importing.
> I call the DTS packages as a SQL job. If the job runs successfully then
the
> temp files are removed when it finishes, however if the job fails it
leaves
> the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
> directory and I start to run low on disk space until I manually delete the
> files.
> Is there a way to direct where these files go? I would like to change this
> to the D:\ where I have a lot more space.
> Thanks
> Mike
>sql
How to direct temp files for DTS packages
I have several DTS packages that import FoxPro data into SQL 2000. These
jobs create a temp file about the same size of the data that I am importing.
I call the DTS packages as a SQL job. If the job runs successfully then the
temp files are removed when it finishes, however if the job fails it leaves
the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
directory and I start to run low on disk space until I manually delete the
files.
Is there a way to direct where these files go? I would like to change this
to the D:\ where I have a lot more space.
Thanks
Mike
Nevermind. I found it. It is a windows configuration setting.
"Mike" <Mike@.Comcast.net> wrote in message
news:u7yCs%235MEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have several DTS packages that import FoxPro data into SQL 2000. These
> jobs create a temp file about the same size of the data that I am
importing.
> I call the DTS packages as a SQL job. If the job runs successfully then
the
> temp files are removed when it finishes, however if the job fails it
leaves
> the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
> directory and I start to run low on disk space until I manually delete the
> files.
> Is there a way to direct where these files go? I would like to change this
> to the D:\ where I have a lot more space.
> Thanks
> Mike
>
jobs create a temp file about the same size of the data that I am importing.
I call the DTS packages as a SQL job. If the job runs successfully then the
temp files are removed when it finishes, however if the job fails it leaves
the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
directory and I start to run low on disk space until I manually delete the
files.
Is there a way to direct where these files go? I would like to change this
to the D:\ where I have a lot more space.
Thanks
Mike
Nevermind. I found it. It is a windows configuration setting.
"Mike" <Mike@.Comcast.net> wrote in message
news:u7yCs%235MEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have several DTS packages that import FoxPro data into SQL 2000. These
> jobs create a temp file about the same size of the data that I am
importing.
> I call the DTS packages as a SQL job. If the job runs successfully then
the
> temp files are removed when it finishes, however if the job fails it
leaves
> the file in the C:\Documents and Settings\SQLUser\Local Settings\Temp
> directory and I start to run low on disk space until I manually delete the
> files.
> Is there a way to direct where these files go? I would like to change this
> to the D:\ where I have a lot more space.
> Thanks
> Mike
>
Friday, March 23, 2012
How to determine if application fetches the result set?
Hi
I have a FoxPro application here to deal with. How do I determine whether
the application fetches the result set to completion or not?
Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
look for?
Many thanks,
Oskar
Hi
You should get SQL_SUCCESS returned from your SQLExecute/SQLFetch statement
if it has completed or SQL_STILL_EXECUTING if it hasn't.
John
"Oskar" wrote:
> Hi
> I have a FoxPro application here to deal with. How do I determine whether
> the application fetches the result set to completion or not?
> Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
> look for?
> --
> Many thanks,
> Oskar
>
sql
I have a FoxPro application here to deal with. How do I determine whether
the application fetches the result set to completion or not?
Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
look for?
Many thanks,
Oskar
Hi
You should get SQL_SUCCESS returned from your SQLExecute/SQLFetch statement
if it has completed or SQL_STILL_EXECUTING if it hasn't.
John
"Oskar" wrote:
> Hi
> I have a FoxPro application here to deal with. How do I determine whether
> the application fetches the result set to completion or not?
> Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
> look for?
> --
> Many thanks,
> Oskar
>
sql
Labels:
application,
completion,
database,
determine,
fetches,
foxpro,
hii,
microsoft,
mysql,
notdo,
oracle,
server,
sql,
whetherthe
How to determine if application fetches the result set?
Hi
I have a FoxPro application here to deal with. How do I determine whether
the application fetches the result set to completion or not?
Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
look for?
Many thanks,
OskarHi
You should get SQL_SUCCESS returned from your SQLExecute/SQLFetch statement
if it has completed or SQL_STILL_EXECUTING if it hasn't.
John
"Oskar" wrote:
> Hi
> I have a FoxPro application here to deal with. How do I determine whether
> the application fetches the result set to completion or not?
> Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
> look for?
> --
> Many thanks,
> Oskar
>
I have a FoxPro application here to deal with. How do I determine whether
the application fetches the result set to completion or not?
Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
look for?
Many thanks,
OskarHi
You should get SQL_SUCCESS returned from your SQLExecute/SQLFetch statement
if it has completed or SQL_STILL_EXECUTING if it hasn't.
John
"Oskar" wrote:
> Hi
> I have a FoxPro application here to deal with. How do I determine whether
> the application fetches the result set to completion or not?
> Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
> look for?
> --
> Many thanks,
> Oskar
>
Labels:
application,
completion,
database,
determine,
fetches,
foxpro,
hii,
microsoft,
mysql,
notdo,
oracle,
server,
sql,
whetherthe
How to determine if application fetches the result set?
Hi
I have a FoxPro application here to deal with. How do I determine whether
the application fetches the result set to completion or not?
Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
look for?
--
Many thanks,
OskarHi
You should get SQL_SUCCESS returned from your SQLExecute/SQLFetch statement
if it has completed or SQL_STILL_EXECUTING if it hasn't.
John
"Oskar" wrote:
> Hi
> I have a FoxPro application here to deal with. How do I determine whether
> the application fetches the result set to completion or not?
> Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
> look for?
> --
> Many thanks,
> Oskar
>
I have a FoxPro application here to deal with. How do I determine whether
the application fetches the result set to completion or not?
Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
look for?
--
Many thanks,
OskarHi
You should get SQL_SUCCESS returned from your SQLExecute/SQLFetch statement
if it has completed or SQL_STILL_EXECUTING if it hasn't.
John
"Oskar" wrote:
> Hi
> I have a FoxPro application here to deal with. How do I determine whether
> the application fetches the result set to completion or not?
> Do I have to look for SQLCloseCursor in ODBC trace? What are the signs to
> look for?
> --
> Many thanks,
> Oskar
>
Subscribe to:
Posts (Atom)