Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information, Line 0
| Author |
Message |
|
Danu
#1 / 6
|
 Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information, Line 0 I did a backup on a database and restore it to another database on the same server. On the first database the following sproc call works EXEC my_sproc
on the second one I get:
Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information,
Line 0
Error converting data type varchar to smalldatetime.
Is it a bug in SQL Server or some database options are different?
|
| Sat, 03 Sep 2005 04:15:51 GMT |
|
 |
|
Danu
#2 / 6
|
Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information, Line 0 Here is what I get when I try to use Enterprise Manager and see the db properties: Error 5: [SQL-DMO]Code execution exception: EXCEPTION_ACCESS_VIOLATION
Quote: > I did a backup on a database and restore it to another database on the same > server. > On the first database the following sproc call works > EXEC my_sproc
> on the second one I get:
> Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information,
> Line 0
> Error converting data type varchar to smalldatetime.
> Is it a bug in SQL Server or some database options are different?
|
| Sat, 03 Sep 2005 04:22:15 GMT |
|
|
|
Vinod
#3 / 6
|
Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information, Line 0 Are you on the same database version on both the servers ... Are you using the latest service packs ... --
Thanks,
Vinod Kumar
MCSE, DBA, MCAD
Quote: > Here is what I get when I try to use Enterprise Manager and see the db > properties: > Error 5: [SQL-DMO]Code execution exception: EXCEPTION_ACCESS_VIOLATION
> > I did a backup on a database and restore it to another database on the
> same
> > server.
> > On the first database the following sproc call works
> > EXEC my_sproc
> > on the second one I get:
> > Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information,
> > Line 0
> > Error converting data type varchar to smalldatetime.
> > Is it a bug in SQL Server or some database options are different?
|
| Sat, 03 Sep 2005 11:57:05 GMT |
|
|
|
Tibor Karasz
#4 / 6
|
Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information, Line 0 Pass the dates in below format, and you don't have to worry about different intl settings: YYYYMMDD --
Tibor Karaszi, SQL Server MVP
For help on TSQL, please provide code we can execute in Query Analyzer
Quote:
> I did a backup on a database and restore it to another database on the same > server. > On the first database the following sproc call works > EXEC my_sproc
> on the second one I get:
> Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information,
> Line 0
> Error converting data type varchar to smalldatetime.
> Is it a bug in SQL Server or some database options are different?
|
| Sat, 03 Sep 2005 19:03:30 GMT |
|
|
|
Ben Willia
#5 / 6
|
Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information, Line 0 Hi Danut: The default format for converting string formats into dates varies
depending on the local language setting of the server. The DATEFORMAT
system setting determines the order which will be used to interpret
this date. '03/17/2003' is only a valid date if the order is
month-day-year. In the UK (for example), the default date order is
day-month-year.
Try:
SET DATEFORMAT mdy
GO
GO
and see if that solves your problem.
Ben.
Quote:
> I did a backup on a database and restore it to another database on the same > server. > On the first database the following sproc call works > EXEC my_sproc
> on the second one I get:
> Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information,
> Line 0
> Error converting data type varchar to smalldatetime.
> Is it a bug in SQL Server or some database options are different?
|
| Sun, 04 Sep 2005 00:35:21 GMT |
|
|
|
Danu
#6 / 6
|
Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information, Line 0 We use US English everywhere and nothing else. Unfortunately the database was a dev database and it was wiped out. Someone created a new database where everything works fine. Too bad I can't figure out why it did not work.
Quote: > Hi Danut: > The default format for converting string formats into dates varies
> depending on the local language setting of the server. The DATEFORMAT
> system setting determines the order which will be used to interpret
> this date. '03/17/2003' is only a valid date if the order is
> month-day-year. In the UK (for example), the default date order is
> day-month-year.
> Try:
> SET DATEFORMAT mdy
> GO
> GO
> and see if that solves your problem.
> Ben.
Quote: > > I did a backup on a database and restore it to another database on the same > > server. > > On the first database the following sproc call works > > EXEC my_sproc
> > on the second one I get:
> > Server: Msg 8114, Level 16, State 1, Procedure co_AddTrader_Information,
> > Line 0
> > Error converting data type varchar to smalldatetime.
> > Is it a bug in SQL Server or some database options are different?
|
| Mon, 05 Sep 2005 06:09:44 GMT |
|
| |
1. Unable to use sp_AddRole = Server: Msg 8114, Level 16, State 4, Procedure sp_addrole, Line 0
2. Server: Msg 214, Level 16, State 2, Procedure sp_execute, Line 52
3. Server: Msg 8115, Level 16, State 2, Procedure sp_monitor, Line 94
4. Server: Msg 18757, Level 16, State 1, Procedure sp_repldone, Line 333 The databa
5. Server: Msg 7399, Level 16, State 1, Line 1 error on .mdb as linked server
6. Server: Msg 7399, Level 16, State 1, Line 1 error on .mdb as linked server
7. Server: Msg 4425, Level 16, State 1, Line 1
8. Server: Msg 1776, Level 16, State 1, Line 1
9. Server: Msg 7619, Level 16, State 1, Line 2
10. Server: Msg 7619, Level 16, State 1, Line 1
11. Server: Msg 7354, Level 16, State 1, Line 1
12. Server: Msg 4321, Level 16, State 1, Line 2
|
|
|
