Hi all,
I have a problem when I import a text delimited data into SQL Server. This happens only with the date. My date format is dd/mm/yyyy in both the text file and regional settings in Windows. I have created a DTS package and schedule the job to run daily. The
imported data in SQL Server show mm/dd/yyyy.
The funny part is when I execute the package directly from DTS, the data were imported without the problem. But when I execute the job in SQL Server Agent, the problem arises. Also this happens only early of the month, from 1st - 12th.
I would appreciate it if anyone can help me in resolving this problem.
ps : My data type for the date column is datetime.
when you execute the job in SQL Server Agent, it runs with the settings on the server.
when you execute the package directly from DTS, it runs with your local settings.
It suggests that the regional settings in Windows on the server are mm/dd/yyyy - which explains why it works until the 12th.
|||Hi Rubes,
I have checked on the server's regional settings, the date format is
'dd/MM/yyyy'.
However, the problem still occurs.
Uskaka
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Adding to my query, I have done the data transformation test and the result shows in format 'dd/MM/yyyy' but when inserted, the format goes 'MM/dd/yyyy'.
Showing posts with label yyyy. Show all posts
Showing posts with label yyyy. Show all posts
Monday, March 12, 2012
Importing Data through DTS
Hi all,
I have a problem when I import a text delimited data into SQL Server. This h
appens only with the date. My date format is dd/mm/yyyy in both the text fil
e and regional settings in Windows. I have created a DTS package and schedul
e the job to run daily. The
imported data in SQL Server show mm/dd/yyyy.
The funny part is when I execute the package directly from DTS, the data wer
e imported without the problem. But when I execute the job in SQL Server Age
nt, the problem arises. Also this happens only early of the month, from 1st
- 12th.
I would appreciate it if anyone can help me in resolving this problem.
ps : My data type for the date column is datetime.when you execute the job in SQL Server Agent, it runs with the settings on t
he server.
when you execute the package directly from DTS, it runs with your local sett
ings.
It suggests that the regional settings in Windows on the server are mm/dd/yy
yy - which explains why it works until the 12th.|||Hi Rubes,
I have checked on the server's regional settings, the date format is
'dd/MM/yyyy'.
However, the problem still occurs.
Uskaka
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Adding to my query, I have done the data transformation test and the result
shows in format 'dd/MM/yyyy' but when inserted, the format goes 'MM/dd/yyyy'
.
I have a problem when I import a text delimited data into SQL Server. This h
appens only with the date. My date format is dd/mm/yyyy in both the text fil
e and regional settings in Windows. I have created a DTS package and schedul
e the job to run daily. The
imported data in SQL Server show mm/dd/yyyy.
The funny part is when I execute the package directly from DTS, the data wer
e imported without the problem. But when I execute the job in SQL Server Age
nt, the problem arises. Also this happens only early of the month, from 1st
- 12th.
I would appreciate it if anyone can help me in resolving this problem.
ps : My data type for the date column is datetime.when you execute the job in SQL Server Agent, it runs with the settings on t
he server.
when you execute the package directly from DTS, it runs with your local sett
ings.
It suggests that the regional settings in Windows on the server are mm/dd/yy
yy - which explains why it works until the 12th.|||Hi Rubes,
I have checked on the server's regional settings, the date format is
'dd/MM/yyyy'.
However, the problem still occurs.
Uskaka
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Adding to my query, I have done the data transformation test and the result
shows in format 'dd/MM/yyyy' but when inserted, the format goes 'MM/dd/yyyy'
.
Friday, March 9, 2012
Importing Data through DTS
Hi all
I have a problem when I import a text delimited data into SQL Server. This happens only with the date. My date format is dd/mm/yyyy in both the text file and regional settings in Windows. I have created a DTS package and schedule the job to run daily. The imported data in SQL Server show mm/dd/yyyy
The funny part is when I execute the package directly from DTS, the data were imported without the problem. But when I execute the job in SQL Server Agent, the problem arises. Also this happens only early of the month, from 1st - 12th
I would appreciate it if anyone can help me in resolving this problem
ps : My data type for the date column is datetime.when you execute the job in SQL Server Agent, it runs with the settings on the server.
when you execute the package directly from DTS, it runs with your local settings.
It suggests that the regional settings in Windows on the server are mm/dd/yyyy - which explains why it works until the 12th.|||Adding to my query, I have done the data transformation test and the result shows in format 'dd/MM/yyyy' but when inserted, the format goes 'MM/dd/yyyy'.
I have a problem when I import a text delimited data into SQL Server. This happens only with the date. My date format is dd/mm/yyyy in both the text file and regional settings in Windows. I have created a DTS package and schedule the job to run daily. The imported data in SQL Server show mm/dd/yyyy
The funny part is when I execute the package directly from DTS, the data were imported without the problem. But when I execute the job in SQL Server Agent, the problem arises. Also this happens only early of the month, from 1st - 12th
I would appreciate it if anyone can help me in resolving this problem
ps : My data type for the date column is datetime.when you execute the job in SQL Server Agent, it runs with the settings on the server.
when you execute the package directly from DTS, it runs with your local settings.
It suggests that the regional settings in Windows on the server are mm/dd/yyyy - which explains why it works until the 12th.|||Adding to my query, I have done the data transformation test and the result shows in format 'dd/MM/yyyy' but when inserted, the format goes 'MM/dd/yyyy'.
Subscribe to:
Posts (Atom)