I know this may seem like a weird thing, but today something very strange
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
David Portas
SQL Server MVP
--|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
Showing posts with label weird. Show all posts
Showing posts with label weird. Show all posts
Monday, March 19, 2012
Mysteriously changing datetime data
I know this may seem like a weird thing, but today something very strange
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
--
David Portas
SQL Server MVP
--|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
--
David Portas
SQL Server MVP
--|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
Mysteriously changing datetime data
I know this may seem like a weird thing, but today something very strange
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?
DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
David Portas
SQL Server MVP
|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?
DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
David Portas
SQL Server MVP
|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
Monday, February 20, 2012
My menubar is all messed up
Ok..this is a weird one.
When I open up SQL Server Management Studio Express my menubar has multiple
instances of the File, Edit, View...menu options... and every toolbar
(Standard, Query Designer, Database Diagram, etc..) all have multiple options
as well.
I've gone in an modified those items as well and I get it to a point where
it looks ok, then when I shut it down and re-open it, all my changes are gone
and it's back to the way it was.
Can anyone help me on this one? Is this the right place to post this
question?
Thanks in advance,
John Scott.
SQL Server 2005 stores it's configuration information in following location:
My Documents\SQL Server Management
Studio\Settings\CurrentSettings-2007-06-06.vssettings
Check to make sure there is no writing problems to that.
The path information for the config file is located at
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\90\Tools\Shell\Profile\
Thanks!
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John Scott" wrote:
> Ok..this is a weird one.
> When I open up SQL Server Management Studio Express my menubar has multiple
> instances of the File, Edit, View...menu options... and every toolbar
> (Standard, Query Designer, Database Diagram, etc..) all have multiple options
> as well.
> I've gone in an modified those items as well and I get it to a point where
> it looks ok, then when I shut it down and re-open it, all my changes are gone
> and it's back to the way it was.
> Can anyone help me on this one? Is this the right place to post this
> question?
>
> --
> Thanks in advance,
> John Scott.
|||Thank for the reply Mohit,
I checked two things...there are some goofy entries in the vssettings file
in my My Documents...file.
I made changes to it, but there is no change when I open up SQL Express...
I also checked and I don't have the
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\90\Tools\Shell\Profile\ key I have all the way up to the Shell..I
have no Profile in there.
Other suggestions?
Thanks,
John Scott.
"Mohit K. Gupta" wrote:
[vbcol=seagreen]
> SQL Server 2005 stores it's configuration information in following location:
> My Documents\SQL Server Management
> Studio\Settings\CurrentSettings-2007-06-06.vssettings
> Check to make sure there is no writing problems to that.
> The path information for the config file is located at
> HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> Server\90\Tools\Shell\Profile\
> Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "John Scott" wrote:
|||Sorry for late reply.
Sorry the proper path in registry is
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\90\Tools\ShellSEM\Profile\.
I can't get the issue to replicate. Here are two options ...
- Delete the CurrentSettings-DATE.vsssettings file.
This will force SSMSEE to reinitialize the settings. Do a search on your
computer for vsssettings delete anything with CurrentSettings in it.
OR
- Try Reinstalling the SSMSEE.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
|||Ok...I did a few things.
1. I deleted my CurrentSettings file in ssmses settings folder...when I
opened up ssmses it poped up a message saying it coudn't find my settings
folder and that it would use the most recent settings for this session
2. I checked that registry path...and i did find it, didn't find anything
out of the ordinary...it had 13 values inside that key
AutoSaveFile
AutoSaveFILETIMEHigh
AutoSaveFILETimeLow
BuildNum
DefaultSettinsDirectory
LastResetSettingsFile
SettingsCachesFILEIMEHigh
SettingsCachesFILEIMELow
Sku
TeamSettingsFile
TeamSettingsFILETIMEHigh
TeamSettingsFILETIMELow
TraackTeamSettings
for the LastResetSettingsFile the value was
'%vsspv_vs_install_directory%\Profiles\ssmsee.vsse ttings'
I checked out this file and there is a node called Caegory
name="Environment_WindowLayout"
inside it, there is another node call "PropertyVale name="WindowLayout">
then after that there is a whole bunch of garbled text (looks like viewstate
data)
then the PropertyValue node closes...
I don't know if that is normal or not...
Any other suggestions?
Thanks,
John Scott.
"Mohit K. Gupta" wrote:
> Sorry for late reply.
> Sorry the proper path in registry is
> HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> Server\90\Tools\ShellSEM\Profile\.
> I can't get the issue to replicate. Here are two options ...
> - Delete the CurrentSettings-DATE.vsssettings file.
> This will force SSMSEE to reinitialize the settings. Do a search on your
> computer for vsssettings delete anything with CurrentSettings in it.
> OR
> - Try Reinstalling the SSMSEE.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
|||Delete all settings files. I would just try reinstalling though.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John Scott" wrote:
[vbcol=seagreen]
> Ok...I did a few things.
> 1. I deleted my CurrentSettings file in ssmses settings folder...when I
> opened up ssmses it poped up a message saying it coudn't find my settings
> folder and that it would use the most recent settings for this session
> 2. I checked that registry path...and i did find it, didn't find anything
> out of the ordinary...it had 13 values inside that key
> AutoSaveFile
> AutoSaveFILETIMEHigh
> AutoSaveFILETimeLow
> BuildNum
> DefaultSettinsDirectory
> LastResetSettingsFile
> SettingsCachesFILEIMEHigh
> SettingsCachesFILEIMELow
> Sku
> TeamSettingsFile
> TeamSettingsFILETIMEHigh
> TeamSettingsFILETIMELow
> TraackTeamSettings
>
> for the LastResetSettingsFile the value was
> '%vsspv_vs_install_directory%\Profiles\ssmsee.vsse ttings'
> I checked out this file and there is a node called Caegory
> name="Environment_WindowLayout"
> inside it, there is another node call "PropertyVale name="WindowLayout">
> then after that there is a whole bunch of garbled text (looks like viewstate
> data)
> then the PropertyValue node closes...
> I don't know if that is normal or not...
> Any other suggestions?
>
> --
> Thanks,
> John Scott.
>
> "Mohit K. Gupta" wrote:
When I open up SQL Server Management Studio Express my menubar has multiple
instances of the File, Edit, View...menu options... and every toolbar
(Standard, Query Designer, Database Diagram, etc..) all have multiple options
as well.
I've gone in an modified those items as well and I get it to a point where
it looks ok, then when I shut it down and re-open it, all my changes are gone
and it's back to the way it was.
Can anyone help me on this one? Is this the right place to post this
question?
Thanks in advance,
John Scott.
SQL Server 2005 stores it's configuration information in following location:
My Documents\SQL Server Management
Studio\Settings\CurrentSettings-2007-06-06.vssettings
Check to make sure there is no writing problems to that.
The path information for the config file is located at
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\90\Tools\Shell\Profile\
Thanks!
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John Scott" wrote:
> Ok..this is a weird one.
> When I open up SQL Server Management Studio Express my menubar has multiple
> instances of the File, Edit, View...menu options... and every toolbar
> (Standard, Query Designer, Database Diagram, etc..) all have multiple options
> as well.
> I've gone in an modified those items as well and I get it to a point where
> it looks ok, then when I shut it down and re-open it, all my changes are gone
> and it's back to the way it was.
> Can anyone help me on this one? Is this the right place to post this
> question?
>
> --
> Thanks in advance,
> John Scott.
|||Thank for the reply Mohit,
I checked two things...there are some goofy entries in the vssettings file
in my My Documents...file.
I made changes to it, but there is no change when I open up SQL Express...
I also checked and I don't have the
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\90\Tools\Shell\Profile\ key I have all the way up to the Shell..I
have no Profile in there.
Other suggestions?
Thanks,
John Scott.
"Mohit K. Gupta" wrote:
[vbcol=seagreen]
> SQL Server 2005 stores it's configuration information in following location:
> My Documents\SQL Server Management
> Studio\Settings\CurrentSettings-2007-06-06.vssettings
> Check to make sure there is no writing problems to that.
> The path information for the config file is located at
> HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> Server\90\Tools\Shell\Profile\
> Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "John Scott" wrote:
|||Sorry for late reply.
Sorry the proper path in registry is
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\90\Tools\ShellSEM\Profile\.
I can't get the issue to replicate. Here are two options ...
- Delete the CurrentSettings-DATE.vsssettings file.
This will force SSMSEE to reinitialize the settings. Do a search on your
computer for vsssettings delete anything with CurrentSettings in it.
OR
- Try Reinstalling the SSMSEE.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
|||Ok...I did a few things.
1. I deleted my CurrentSettings file in ssmses settings folder...when I
opened up ssmses it poped up a message saying it coudn't find my settings
folder and that it would use the most recent settings for this session
2. I checked that registry path...and i did find it, didn't find anything
out of the ordinary...it had 13 values inside that key
AutoSaveFile
AutoSaveFILETIMEHigh
AutoSaveFILETimeLow
BuildNum
DefaultSettinsDirectory
LastResetSettingsFile
SettingsCachesFILEIMEHigh
SettingsCachesFILEIMELow
Sku
TeamSettingsFile
TeamSettingsFILETIMEHigh
TeamSettingsFILETIMELow
TraackTeamSettings
for the LastResetSettingsFile the value was
'%vsspv_vs_install_directory%\Profiles\ssmsee.vsse ttings'
I checked out this file and there is a node called Caegory
name="Environment_WindowLayout"
inside it, there is another node call "PropertyVale name="WindowLayout">
then after that there is a whole bunch of garbled text (looks like viewstate
data)
then the PropertyValue node closes...
I don't know if that is normal or not...
Any other suggestions?
Thanks,
John Scott.
"Mohit K. Gupta" wrote:
> Sorry for late reply.
> Sorry the proper path in registry is
> HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> Server\90\Tools\ShellSEM\Profile\.
> I can't get the issue to replicate. Here are two options ...
> - Delete the CurrentSettings-DATE.vsssettings file.
> This will force SSMSEE to reinitialize the settings. Do a search on your
> computer for vsssettings delete anything with CurrentSettings in it.
> OR
> - Try Reinstalling the SSMSEE.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
|||Delete all settings files. I would just try reinstalling though.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"John Scott" wrote:
[vbcol=seagreen]
> Ok...I did a few things.
> 1. I deleted my CurrentSettings file in ssmses settings folder...when I
> opened up ssmses it poped up a message saying it coudn't find my settings
> folder and that it would use the most recent settings for this session
> 2. I checked that registry path...and i did find it, didn't find anything
> out of the ordinary...it had 13 values inside that key
> AutoSaveFile
> AutoSaveFILETIMEHigh
> AutoSaveFILETimeLow
> BuildNum
> DefaultSettinsDirectory
> LastResetSettingsFile
> SettingsCachesFILEIMEHigh
> SettingsCachesFILEIMELow
> Sku
> TeamSettingsFile
> TeamSettingsFILETIMEHigh
> TeamSettingsFILETIMELow
> TraackTeamSettings
>
> for the LastResetSettingsFile the value was
> '%vsspv_vs_install_directory%\Profiles\ssmsee.vsse ttings'
> I checked out this file and there is a node called Caegory
> name="Environment_WindowLayout"
> inside it, there is another node call "PropertyVale name="WindowLayout">
> then after that there is a whole bunch of garbled text (looks like viewstate
> data)
> then the PropertyValue node closes...
> I don't know if that is normal or not...
> Any other suggestions?
>
> --
> Thanks,
> John Scott.
>
> "Mohit K. Gupta" wrote:
Subscribe to:
Posts (Atom)