Showing posts with label level. Show all posts
Showing posts with label level. Show all posts

Thursday, March 29, 2012

Error 946: Cannot open database upgrade the database to the latest

I am trying to move a database from SQL Server 70 @. 70 compatibility level to
SQL Server 2000 @. 70 compatibility level.
But when execute restore stmt (cmd), I keep getting the errors:
Server: Msg 9002, Level 17, State 6, Line 2
The log file for database 'my_db' is full. Back up the transaction log for
the database to free up some log space.
Server: Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.
Converting database 'my_db' from version 515 to the current version 539.
Database 'my_db' running the upgrade step from version 515 to version 524.
Database 'my_db' running the upgrade step from version 524 to version 525.
Database 'my_db' running the upgrade step from version 525 to version 526.
Database 'my_db' running the upgrade step from version 526 to version 527.
Database 'my_db' running the upgrade step from version 527 to version 528.
Database 'my_db' running the upgrade step from version 528 to version 529.
Database 'my_db' running the upgrade step from version 529 to version 530.
Database 'my_db' running the upgrade step from version 530 to version 531.
Database 'my_db' running the upgrade step from version 531 to version 532.
Database 'my_db' running the upgrade step from version 532 to version 533.
Database 'my_db' running the upgrade step from version 533 to version 534.
Database 'my_db' running the upgrade step from version 534 to version 535.
Error 946: Cannot open database upgrade the database to the latest version
Any idea, how I can restore w/o errors?
Hi,
Looks like you do not have enough room in your hard disk in which the LDF
file resides. Could you identify the drive with more space and use
RESTORE DATABASE command with MOVE options to restore the database. See
Restore with Move option in Books online.
Thanks
Hari
SQL Server MVP
"Pari" <Pari@.discussions.microsoft.com> wrote in message
news:C74D6B5B-436D-4288-ABF3-31C835CC236B@.microsoft.com...
>I am trying to move a database from SQL Server 70 @. 70 compatibility level
>to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?
|||Hi
For an Upgrade, SQL Server needs space in the transaction log to work. You
don't have enough.
On the SQL Server 7.0, before you make the backup, dump the log, grow the
transaction log to at least 10% of the database size, then do the backup and
then the restore the SQL Server 2000.
Regards
Mike
"Pari" wrote:

> I am trying to move a database from SQL Server 70 @. 70 compatibility level to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?

Error 946: Cannot open database upgrade the database to the latest

I am trying to move a database from SQL Server 70 @. 70 compatibility level to
SQL Server 2000 @. 70 compatibility level.
But when execute restore stmt (cmd), I keep getting the errors:
Server: Msg 9002, Level 17, State 6, Line 2
The log file for database 'my_db' is full. Back up the transaction log for
the database to free up some log space.
Server: Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.
Converting database 'my_db' from version 515 to the current version 539.
Database 'my_db' running the upgrade step from version 515 to version 524.
Database 'my_db' running the upgrade step from version 524 to version 525.
Database 'my_db' running the upgrade step from version 525 to version 526.
Database 'my_db' running the upgrade step from version 526 to version 527.
Database 'my_db' running the upgrade step from version 527 to version 528.
Database 'my_db' running the upgrade step from version 528 to version 529.
Database 'my_db' running the upgrade step from version 529 to version 530.
Database 'my_db' running the upgrade step from version 530 to version 531.
Database 'my_db' running the upgrade step from version 531 to version 532.
Database 'my_db' running the upgrade step from version 532 to version 533.
Database 'my_db' running the upgrade step from version 533 to version 534.
Database 'my_db' running the upgrade step from version 534 to version 535.
Error 946: Cannot open database upgrade the database to the latest version
Any idea, how I can restore w/o errors?Hi,
Looks like you do not have enough room in your hard disk in which the LDF
file resides. Could you identify the drive with more space and use
RESTORE DATABASE command with MOVE options to restore the database. See
Restore with Move option in Books online.
Thanks
Hari
SQL Server MVP
"Pari" <Pari@.discussions.microsoft.com> wrote in message
news:C74D6B5B-436D-4288-ABF3-31C835CC236B@.microsoft.com...
>I am trying to move a database from SQL Server 70 @. 70 compatibility level
>to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?|||Hi
For an Upgrade, SQL Server needs space in the transaction log to work. You
don't have enough.
On the SQL Server 7.0, before you make the backup, dump the log, grow the
transaction log to at least 10% of the database size, then do the backup and
then the restore the SQL Server 2000.
Regards
Mike
"Pari" wrote:
> I am trying to move a database from SQL Server 70 @. 70 compatibility level to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?|||Hi, you are right my log file did not have enough space, however, do you know
what these messages mean?
> > Database 'my_db' running the upgrade step from version 524 to version 525.
> > Database 'my_db' running the upgrade step from version 525 to version 526.
> > Database 'my_db' running the upgrade step from version 526 to version 527.
> > Database 'my_db' running the upgrade step from version 527 to version 528.
> > Database 'my_db' running the upgrade step from version 528 to version 529.
Does it mean its upgrading the DB from 70 compatibility to 80'
Thanks
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> For an Upgrade, SQL Server needs space in the transaction log to work. You
> don't have enough.
> On the SQL Server 7.0, before you make the backup, dump the log, grow the
> transaction log to at least 10% of the database size, then do the backup and
> then the restore the SQL Server 2000.
> Regards
> Mike
> "Pari" wrote:
> > I am trying to move a database from SQL Server 70 @. 70 compatibility level to
> > SQL Server 2000 @. 70 compatibility level.
> >
> > But when execute restore stmt (cmd), I keep getting the errors:
> >
> > Server: Msg 9002, Level 17, State 6, Line 2
> > The log file for database 'my_db' is full. Back up the transaction log for
> > the database to free up some log space.
> > Server: Msg 3013, Level 16, State 1, Line 2
> > RESTORE DATABASE is terminating abnormally.
> > Converting database 'my_db' from version 515 to the current version 539.
> > Database 'my_db' running the upgrade step from version 515 to version 524.
> > Database 'my_db' running the upgrade step from version 524 to version 525.
> > Database 'my_db' running the upgrade step from version 525 to version 526.
> > Database 'my_db' running the upgrade step from version 526 to version 527.
> > Database 'my_db' running the upgrade step from version 527 to version 528.
> > Database 'my_db' running the upgrade step from version 528 to version 529.
> > Database 'my_db' running the upgrade step from version 529 to version 530.
> > Database 'my_db' running the upgrade step from version 530 to version 531.
> > Database 'my_db' running the upgrade step from version 531 to version 532.
> > Database 'my_db' running the upgrade step from version 532 to version 533.
> > Database 'my_db' running the upgrade step from version 533 to version 534.
> > Database 'my_db' running the upgrade step from version 534 to version 535.
> > Error 946: Cannot open database upgrade the database to the latest version
> >
> >
> > Any idea, how I can restore w/o errors?

Error 946: Cannot open database upgrade the database to the latest

I am trying to move a database from SQL Server 70 @. 70 compatibility level t
o
SQL Server 2000 @. 70 compatibility level.
But when execute restore stmt (cmd), I keep getting the errors:
Server: Msg 9002, Level 17, State 6, Line 2
The log file for database 'my_db' is full. Back up the transaction log for
the database to free up some log space.
Server: Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.
Converting database 'my_db' from version 515 to the current version 539.
Database 'my_db' running the upgrade step from version 515 to version 524.
Database 'my_db' running the upgrade step from version 524 to version 525.
Database 'my_db' running the upgrade step from version 525 to version 526.
Database 'my_db' running the upgrade step from version 526 to version 527.
Database 'my_db' running the upgrade step from version 527 to version 528.
Database 'my_db' running the upgrade step from version 528 to version 529.
Database 'my_db' running the upgrade step from version 529 to version 530.
Database 'my_db' running the upgrade step from version 530 to version 531.
Database 'my_db' running the upgrade step from version 531 to version 532.
Database 'my_db' running the upgrade step from version 532 to version 533.
Database 'my_db' running the upgrade step from version 533 to version 534.
Database 'my_db' running the upgrade step from version 534 to version 535.
Error 946: Cannot open database upgrade the database to the latest version
Any idea, how I can restore w/o errors?Hi,
Looks like you do not have enough room in your hard disk in which the LDF
file resides. Could you identify the drive with more space and use
RESTORE DATABASE command with MOVE options to restore the database. See
Restore with Move option in Books online.
Thanks
Hari
SQL Server MVP
"Pari" <Pari@.discussions.microsoft.com> wrote in message
news:C74D6B5B-436D-4288-ABF3-31C835CC236B@.microsoft.com...
>I am trying to move a database from SQL Server 70 @. 70 compatibility level
>to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?|||Hi
For an Upgrade, SQL Server needs space in the transaction log to work. You
don't have enough.
On the SQL Server 7.0, before you make the backup, dump the log, grow the
transaction log to at least 10% of the database size, then do the backup and
then the restore the SQL Server 2000.
Regards
Mike
"Pari" wrote:

> I am trying to move a database from SQL Server 70 @. 70 compatibility level
to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?sql

Tuesday, March 27, 2012

Error 8623

Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on technet and find the following article
(http://support.microsoft.com/defaul...kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e no encontrei informaes sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/defaul...4&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on technet and find the following article
> (http://support.microsoft.com/defaul...kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e no encontrei informaes sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>

Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
MarekMarek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search...>
ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>sql

Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
Marek
Marek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search/...2&ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>

Error 8623

Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default...b;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e no encontrei informaes sobre este FLAG.
Does someone know any information about this error or about this flag?
I found several KB's associated with that error such as this one:
http://support.microsoft.com/default...&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default...b;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e no encontrei informaes sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>

Error 8623

Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e não encontrei informações sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;841404&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e não encontrei informações sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>

Thursday, March 22, 2012

error 8152 in sql update statement

hi all.
I am doing a simple sql update and getting below error:
Error Messages:
Server: Msg 8152, Level 16, State 4, Line 1
String or binary data would be truncated.
The statement has been terminated.
I verified that the values specified are within the column length limits of
the table. I tried to searche for troubleshooting guidelines and couldnt
find any.
Please assist. Thanks.
Please post your DDL plus the statement that is giving you trouble.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
..
"KristinaY" <KristinaY@.discussions.microsoft.com> wrote in message
news:56B41165-C240-4111-9914-04672C4FA8BF@.microsoft.com...
hi all.
I am doing a simple sql update and getting below error:
Error Messages:
Server: Msg 8152, Level 16, State 4, Line 1
String or binary data would be truncated.
The statement has been terminated.
I verified that the values specified are within the column length limits of
the table. I tried to searche for troubleshooting guidelines and couldnt
find any.
Please assist. Thanks.

error 8152 in sql update statement

hi all.
I am doing a simple sql update and getting below error:
Error Messages:
Server: Msg 8152, Level 16, State 4, Line 1
String or binary data would be truncated.
The statement has been terminated.
I verified that the values specified are within the column length limits of
the table. I tried to searche for troubleshooting guidelines and couldnt
find any.
Please assist. Thanks.Please post your DDL plus the statement that is giving you trouble.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
.
"KristinaY" <KristinaY@.discussions.microsoft.com> wrote in message
news:56B41165-C240-4111-9914-04672C4FA8BF@.microsoft.com...
hi all.
I am doing a simple sql update and getting below error:
Error Messages:
Server: Msg 8152, Level 16, State 4, Line 1
String or binary data would be truncated.
The statement has been terminated.
I verified that the values specified are within the column length limits of
the table. I tried to searche for troubleshooting guidelines and couldnt
find any.
Please assist. Thanks.sql

error 8152 in sql update statement

hi all.
I am doing a simple sql update and getting below error:
Error Messages:
Server: Msg 8152, Level 16, State 4, Line 1
String or binary data would be truncated.
The statement has been terminated.
I verified that the values specified are within the column length limits of
the table. I tried to searche for troubleshooting guidelines and couldnt
find any.
Please assist. Thanks.Please post your DDL plus the statement that is giving you trouble.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
.
"KristinaY" <KristinaY@.discussions.microsoft.com> wrote in message
news:56B41165-C240-4111-9914-04672C4FA8BF@.microsoft.com...
hi all.
I am doing a simple sql update and getting below error:
Error Messages:
Server: Msg 8152, Level 16, State 4, Line 1
String or binary data would be truncated.
The statement has been terminated.
I verified that the values specified are within the column length limits of
the table. I tried to searche for troubleshooting guidelines and couldnt
find any.
Please assist. Thanks.

Error 8114 Date data

I am trying to pull over data in for a specified date from an ODBC connected
AS/400 table, and I get the following error.
Server: Msg 8114, Level 16, State 8, Line 1
Error converting data type DBTYPE_DBTIMESTAMP to datetime.
Here's an example of what the field looks like in the AS/400 table:
1999-08-24 00:00:00.000
I thought that I could just as "where date = '2005-07-01 00:00:00.00'" but
it doesn't work.
Any thoughts'
Thanks in advance.This could be the limitation of the provider you use. Try a different or
newer provider.
Adrian
"aschossler" <aschossler@.discussions.microsoft.com> wrote in message
news:6C6CD9AF-F37E-459E-9A42-64CE221D2E94@.microsoft.com...
>I am trying to pull over data in for a specified date from an ODBC
>connected
> AS/400 table, and I get the following error.
> Server: Msg 8114, Level 16, State 8, Line 1
> Error converting data type DBTYPE_DBTIMESTAMP to datetime.
> Here's an example of what the field looks like in the AS/400 table:
> 1999-08-24 00:00:00.000
> I thought that I could just as "where date = '2005-07-01 00:00:00.00'"
> but
> it doesn't work.
> Any thoughts'
> Thanks in advance.sql

Error 8114 Date data

I am trying to pull over data in for a specified date from an ODBC connected
AS/400 table, and I get the following error.
Server: Msg 8114, Level 16, State 8, Line 1
Error converting data type DBTYPE_DBTIMESTAMP to datetime.
Here's an example of what the field looks like in the AS/400 table:
1999-08-24 00:00:00.000
I thought that I could just as "where date = '2005-07-01 00:00:00.00'" but
it doesn't work.
Any thoughts?
Thanks in advance.
This could be the limitation of the provider you use. Try a different or
newer provider.
Adrian
"aschossler" <aschossler@.discussions.microsoft.com> wrote in message
news:6C6CD9AF-F37E-459E-9A42-64CE221D2E94@.microsoft.com...
>I am trying to pull over data in for a specified date from an ODBC
>connected
> AS/400 table, and I get the following error.
> Server: Msg 8114, Level 16, State 8, Line 1
> Error converting data type DBTYPE_DBTIMESTAMP to datetime.
> Here's an example of what the field looks like in the AS/400 table:
> 1999-08-24 00:00:00.000
> I thought that I could just as "where date = '2005-07-01 00:00:00.00'"
> but
> it doesn't work.
> Any thoughts?
> Thanks in advance.

Error 8114 Date data

I am trying to pull over data in for a specified date from an ODBC connected
AS/400 table, and I get the following error.
Server: Msg 8114, Level 16, State 8, Line 1
Error converting data type DBTYPE_DBTIMESTAMP to datetime.
Here's an example of what the field looks like in the AS/400 table:
1999-08-24 00:00:00.000
I thought that I could just as "where date = '2005-07-01 00:00:00.00'" but
it doesn't work.
Any thoughts'
Thanks in advance.This could be the limitation of the provider you use. Try a different or
newer provider.
Adrian
"aschossler" <aschossler@.discussions.microsoft.com> wrote in message
news:6C6CD9AF-F37E-459E-9A42-64CE221D2E94@.microsoft.com...
>I am trying to pull over data in for a specified date from an ODBC
>connected
> AS/400 table, and I get the following error.
> Server: Msg 8114, Level 16, State 8, Line 1
> Error converting data type DBTYPE_DBTIMESTAMP to datetime.
> Here's an example of what the field looks like in the AS/400 table:
> 1999-08-24 00:00:00.000
> I thought that I could just as "where date = '2005-07-01 00:00:00.00'"
> but
> it doesn't work.
> Any thoughts'
> Thanks in advance.

Wednesday, March 21, 2012

Error 7399 in Openquery. GetNextRow in Informix

When I execute a Select using Openquery against Informix, sometimes I receive the error below:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Informix][Informix ODBC Driver]Error in row.]
[OLE/DB provider returned message: sqlerrm(table_name)]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowset::GetNextRows returned 0x80004005: ].

I noticed that the error is occuring when an user is Updating/Deleting or Inserting data in the table at the same time.

Environment:
Windows 2K
SQL Server 2000 with SP 3a
SDK Client 2.81 for Informix
ODBC 3.81 for Informix

Informix 7.3 running on a Unix machineHi,

Do you found any solution about this case? I have the same problem as you. Please send me information if you have some, this will be a big help for me.

Thank you and best regards,
ThinkMan|||Hi Thinkman,

Sorry, but I didnt find any solution for OUR problem.

Norivalsql

Error 7391 running distributed transaction

When attempting to run a distributed transaction I get the following
error:
Server: Msg 7391, Level 16, State 1, Line 4
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in
the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
I have two servers.
ServerA
Windows 2003
SQL Server 2000 SP3a
MDAC 2.8 RTM
ServerB
Windows 2000
SQL Server 2000 SP3a
MDAC 2.8 RTM
When I open Query Analyzer on ServerA and execute the following
statement, I get the error.
begin distributed transaction
exec ServerB.master.dbo.sp_helpdb
I've already enabled network access for Component Services:
http://support.microsoft.com/default.aspx?kbid=329332
Didn't fix the issue.
Any ideas?
Thanks,
MarkMake sure that the DTC Service is running on both machines as well..
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mark Newton" <mark.newton@.bdsmarketing.com> wrote in message
news:0ia5sv0ifue6po44fbc1j3aipvpas38put@.4ax.com...
> When attempting to run a distributed transaction I get the following
> error:
> Server: Msg 7391, Level 16, State 1, Line 4
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in
> the specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>
> I have two servers.
> ServerA
> Windows 2003
> SQL Server 2000 SP3a
> MDAC 2.8 RTM
> ServerB
> Windows 2000
> SQL Server 2000 SP3a
> MDAC 2.8 RTM
> When I open Query Analyzer on ServerA and execute the following
> statement, I get the error.
> begin distributed transaction
> exec ServerB.master.dbo.sp_helpdb
>
> I've already enabled network access for Component Services:
> http://support.microsoft.com/default.aspx?kbid=329332
> Didn't fix the issue.
> Any ideas?
> Thanks,
> Mark|||MSDTC is running on both machines.
On Tue, 25 Nov 2003 05:45:42 -0500, "Wayne Snyder"
<wsnyder@.computeredservices.com> wrote:
>Make sure that the DTC Service is running on both machines as well..

Monday, March 19, 2012

error 7390 when isolation level is set to serializable...

am trying to replicate the execution of a stored procedure and hence am using isolation level of serializable as recommended by BOL for purge operations.
This following code works fine when executed on the server ( logging in via terminal services) bu gives me an error when executed thru Query Analyzer.
Really puzzled.
__________________________________________________ ______
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
GO
begin transaction
exec dbo.DeleteJobRunResults @.SourceSystem = 'GSP Risk Engine',
@.SourceSystemCode = '13397'
commit transaction
go
__________________________________________________ _______
************************************************** *
Server: Msg 7390, Level 16, State 1, Line 1
The requested operation could not be performed because the OLE DB provider 'ADSDSOObject' does not support the required transaction interface.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' IUnknown::QueryInterface returned 0x80004002].
************************************************** ***
Any help will be appreciated
thanks
-srini
the error message is coming from the ADSI (Active Directory) provider.
is active directory in the mix somehow?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"srini" <srini@.discussions.microsoft.com> wrote in message
news:32ED50DF-5820-42FF-88E8-E7A7475DAE3D@.microsoft.com...
> am trying to replicate the execution of a stored procedure and hence am
using isolation level of serializable as recommended by BOL for purge
operations.
> This following code works fine when executed on the server ( logging in
via terminal services) bu gives me an error when executed thru Query
Analyzer.
> Really puzzled.
> __________________________________________________ ______
> SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
> GO
> begin transaction
> exec dbo.DeleteJobRunResults @.SourceSystem = 'GSP Risk Engine',
> @.SourceSystemCode = '13397'
> commit transaction
> go
> __________________________________________________ _______
> ************************************************** *
> Server: Msg 7390, Level 16, State 1, Line 1
> The requested operation could not be performed because the OLE DB provider
'ADSDSOObject' does not support the required transaction interface.
> OLE DB error trace [OLE/DB Provider 'ADSDSOObject'
IUnknown::QueryInterface returned 0x80004002].
> ************************************************** ***
> Any help will be appreciated
> thanks
> -srini
|||Hilary:
Is there a way to figure that out ? Just joined a new job and this
workstation was being used by another developer. Let me look at the proc in
more detail
-srini
"Hilary Cotter" wrote:

> the error message is coming from the ADSI (Active Directory) provider.
> is active directory in the mix somehow?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "srini" <srini@.discussions.microsoft.com> wrote in message
> news:32ED50DF-5820-42FF-88E8-E7A7475DAE3D@.microsoft.com...
> using isolation level of serializable as recommended by BOL for purge
> operations.
> via terminal services) bu gives me an error when executed thru Query
> Analyzer.
> 'ADSDSOObject' does not support the required transaction interface.
> IUnknown::QueryInterface returned 0x80004002].
>
>
|||Here is the code. inherited it ;-)
*******************************************
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE DeleteJobRunResults
-- procedure to delete job run results given the source system's job id
-- INPUT Parameters
@.SourceSystemVARCHAR(80),
@.SourceSystemCodeVARCHAR(255)
-- OUTPUT Parameters
AS
BEGIN
DECLARE @.ErrNumINT
DECLARE @.CountINT
DECLARE @.ResultsType CHAR(2)-- 'MD' = market data
-- 'TV' = trade valuations
DECLARE @.JobRunUID INT
SELECT
@.JobRunUID = JobRunUID
FROM
JobRun jr
INNER JOIN
CodeLegend cl
ON jr.SourceSystemUID = cl.CodeLegendUID
WHERE
jr.SourceSystemCode = @.SourceSystemCode AND
cl.FullName = @.SourceSystem
-- determine if the job results are market data or trade valuations
IF EXISTS (SELECT 1 FROM JobMarketData WHERE JobRunUID = @.JobRunUID)
SELECT @.ResultsType = 'MD'
ELSE
SELECT @.ResultsType = 'TV'
IF @.ResultsType = 'TV'
BEGIN
CREATE TABLE #TradeValueUIDs (
TradeValueUID INT,
PRIMARY KEY CLUSTERED (TradeValueUID))
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
INSERT #TradeValueUIDs
SELECT TradeValueUID
FROM
JobTradeValue jtv1
WHERE
JobRunUID = @.JobRunUID AND
(SELECT COUNT(*) FROM JobTradeValue jtv2 WHERE jtv1.TradeValueUID =
jtv2.TradeValueUID) = 1
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
-- This holds shared locks on TradeValue until the transaction commits.
The count is not used.
SELECT @.Count = COUNT(*) FROM TradeValue tv WITH (HOLDLOCK) INNER JOIN
#TradeValueUIDs tvu ON tv.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE PnlComponentFROM PnlComponent pcINNER JOIN #TradeValueUIDs tvu ON
pc.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE PnLMark FROM PnLMark pm INNER JOIN #TradeValueUIDs tvu ON
pm.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE CDSens FROM CDSens cdsINNER JOIN #TradeValueUIDs tvu ON
cds.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE CSSens FROM CSSens css INNER JOIN #TradeValueUIDs tvu ON
css.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE IRSens FROM IRSens irs INNER JOIN #TradeValueUIDs tvu ON
irs.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE IRVega FROM IRVega irv INNER JOIN #TradeValueUIDs tvu ON
irv.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE SimpleValue FROM SimpleValue sv INNER JOIN #TradeValueUIDs tvu ON
sv.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE JobTradeValueWHERE JobRunUID = @.JobRunUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE TradeValueFROM TradeValue tvINNER JOIN #TradeValueUIDs tvu ON
tv.TradeValueUID = tvu.TradeValueUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE StatusMessageWHERE JobRunUID = @.JobRunUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE JobRunWHERE JobRunUID = @.JobRunUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
END
ELSE
BEGIN
CREATE TABLE #MarketDataUIDs (
MarketDataUID INT,
PRIMARY KEY CLUSTERED (MarketDataUID))
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
INSERT #MarketDataUIDs
SELECT MarketDataUID
FROM
JobMarketData jmd1
WHERE
JobRunUID = @.JobRunUID AND
(SELECT COUNT(*) FROM JobMarketData jmd2 WHERE jmd1.MarketDataUID =
jmd2.MarketDataUID) = 1
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
-- This holds shared locks on TradeValue until the transaction commits.
The count is not used.
SELECT @.Count = COUNT(*) FROM MarketData md WITH (HOLDLOCK) INNER JOIN
#MarketDataUIDs mdu ON md.MarketDataUID = mdu.MarketDataUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE FXRateFROM FXRate fxINNER JOIN #MarketDataUIDs mdu ON
fx.MarketDataUID = mdu.MarketDataUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE IRRate FROM IRRate ir INNER JOIN #MarketDataUIDs mdu ON
ir.MarketDataUID = mdu.MarketDataUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE CreditCurveSpreads FROM CreditCurveSpreads ccsINNER JOIN
#MarketDataUIDs mdu ON ccs.MarketDataUID = mdu.MarketDataUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE IRDiscountRate FROM IRDiscountRate idrINNER JOIN
#MarketDataUIDs mdu ON idr.MarketDataUID = mdu.MarketDataUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE JobMarketDataWHERE JobRunUID = @.JobRunUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE MarketDataFROM MarketData mdINNER JOIN #MarketDataUIDs mdu ON
md.MarketDataUID = mdu.MarketDataUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE StatusMessageWHERE JobRunUID = @.JobRunUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
DELETE JobRunWHERE JobRunUID = @.JobRunUID
SELECT @.ErrNum = @.@.ERROR
IF @.ErrNum <> 0 GOTO Exit_no_log
END
RETURN 0
Exit_no_log:
RETURN 999
END
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
"srini" wrote:
[vbcol=seagreen]
> Hilary:
> Is there a way to figure that out ? Just joined a new job and this
> workstation was being used by another developer. Let me look at the proc in
> more detail
> -srini
> "Hilary Cotter" wrote:
|||there is no ADSI there. Let me look into this further.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"srini" <srini@.discussions.microsoft.com> wrote in message
news:6543B87F-DA49-44AC-A2D1-FD4340A5969F@.microsoft.com...
> Here is the code. inherited it ;-)
> *******************************************
> SET QUOTED_IDENTIFIER ON
> GO
> SET ANSI_NULLS ON
> GO
> CREATE PROCEDURE DeleteJobRunResults
> -- procedure to delete job run results given the source system's job id
> -- INPUT Parameters
> @.SourceSystem VARCHAR(80),
> @.SourceSystemCode VARCHAR(255)
> -- OUTPUT Parameters
> AS
> BEGIN
> DECLARE @.ErrNum INT
> DECLARE @.Count INT
>
> DECLARE @.ResultsType CHAR(2) -- 'MD' = market data
> -- 'TV' = trade valuations
> DECLARE @.JobRunUID INT
>
> SELECT
> @.JobRunUID = JobRunUID
> FROM
> JobRun jr
> INNER JOIN
> CodeLegend cl
> ON jr.SourceSystemUID = cl.CodeLegendUID
> WHERE
> jr.SourceSystemCode = @.SourceSystemCode AND
> cl.FullName = @.SourceSystem
>
> -- determine if the job results are market data or trade valuations
> IF EXISTS (SELECT 1 FROM JobMarketData WHERE JobRunUID = @.JobRunUID)
> SELECT @.ResultsType = 'MD'
> ELSE
> SELECT @.ResultsType = 'TV'
>
> IF @.ResultsType = 'TV'
> BEGIN
> CREATE TABLE #TradeValueUIDs (
> TradeValueUID INT,
> PRIMARY KEY CLUSTERED (TradeValueUID))
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
>
> INSERT #TradeValueUIDs
> SELECT TradeValueUID
> FROM
> JobTradeValue jtv1
> WHERE
> JobRunUID = @.JobRunUID AND
> (SELECT COUNT(*) FROM JobTradeValue jtv2 WHERE jtv1.TradeValueUID =
> jtv2.TradeValueUID) = 1
>
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
>
> -- This holds shared locks on TradeValue until the transaction commits.
> The count is not used.
> SELECT @.Count = COUNT(*) FROM TradeValue tv WITH (HOLDLOCK) INNER JOIN
> #TradeValueUIDs tvu ON tv.TradeValueUID = tvu.TradeValueUID
>
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE PnlComponent FROM PnlComponent pc INNER JOIN #TradeValueUIDs tvu ON
> pc.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE PnLMark FROM PnLMark pm INNER JOIN #TradeValueUIDs tvu ON
> pm.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE CDSens FROM CDSens cds INNER JOIN #TradeValueUIDs tvu ON
> cds.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE CSSens FROM CSSens css INNER JOIN #TradeValueUIDs tvu ON
> css.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE IRSens FROM IRSens irs INNER JOIN #TradeValueUIDs tvu ON
> irs.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE IRVega FROM IRVega irv INNER JOIN #TradeValueUIDs tvu ON
> irv.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE SimpleValue FROM SimpleValue sv INNER JOIN #TradeValueUIDs tvu ON
> sv.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE JobTradeValue WHERE JobRunUID = @.JobRunUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE TradeValue FROM TradeValue tv INNER JOIN #TradeValueUIDs tvu ON
> tv.TradeValueUID = tvu.TradeValueUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE StatusMessage WHERE JobRunUID = @.JobRunUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE JobRun WHERE JobRunUID = @.JobRunUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> END
> ELSE
> BEGIN
> CREATE TABLE #MarketDataUIDs (
> MarketDataUID INT,
> PRIMARY KEY CLUSTERED (MarketDataUID))
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> INSERT #MarketDataUIDs
> SELECT MarketDataUID
> FROM
> JobMarketData jmd1
> WHERE
> JobRunUID = @.JobRunUID AND
> (SELECT COUNT(*) FROM JobMarketData jmd2 WHERE jmd1.MarketDataUID =
> jmd2.MarketDataUID) = 1
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> -- This holds shared locks on TradeValue until the transaction commits.
> The count is not used.
> SELECT @.Count = COUNT(*) FROM MarketData md WITH (HOLDLOCK) INNER JOIN
> #MarketDataUIDs mdu ON md.MarketDataUID = mdu.MarketDataUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
>
> DELETE FXRate FROM FXRate fx INNER JOIN #MarketDataUIDs mdu ON
> fx.MarketDataUID = mdu.MarketDataUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE IRRate FROM IRRate ir INNER JOIN #MarketDataUIDs mdu ON
> ir.MarketDataUID = mdu.MarketDataUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE CreditCurveSpreads FROM CreditCurveSpreads ccs INNER JOIN
> #MarketDataUIDs mdu ON ccs.MarketDataUID = mdu.MarketDataUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE IRDiscountRate FROM IRDiscountRate idr INNER JOIN
> #MarketDataUIDs mdu ON idr.MarketDataUID = mdu.MarketDataUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE JobMarketData WHERE JobRunUID = @.JobRunUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE MarketData FROM MarketData md INNER JOIN #MarketDataUIDs mdu ON
> md.MarketDataUID = mdu.MarketDataUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE StatusMessage WHERE JobRunUID = @.JobRunUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> DELETE JobRun WHERE JobRunUID = @.JobRunUID
> SELECT @.ErrNum = @.@.ERROR
> IF @.ErrNum <> 0 GOTO Exit_no_log
> END
> RETURN 0
> ----
--[vbcol=seagreen]
> Exit_no_log:
> RETURN 999
> END
> GO
> SET QUOTED_IDENTIFIER OFF
> GO
> SET ANSI_NULLS ON
> GO
>
> "srini" wrote:
in[vbcol=seagreen]
am[vbcol=seagreen]
in[vbcol=seagreen]
provider[vbcol=seagreen]

error 7390 when isolation level is set to serializable...

I am trying to replicate the execution of a stored procedure and hence am using isolation level of serializable as recommended by BOL for purge operations.
This following code works fine when executed on the server ( logging in via terminal services) bu gives me an error when executed thru Query Analyzer.
Really puzzled.
________________________________________________________
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
GO
begin transaction
exec dbo.DeleteJobRunResults @.SourceSystem = 'GSP Risk Engine',
@.SourceSystemCode = '13397'
commit transaction
go
_________________________________________________________
***************************************************
Server: Msg 7390, Level 16, State 1, Line 1
The requested operation could not be performed because the OLE DB provider 'ADSDSOObject' does not support the required transaction interface.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' IUnknown::QueryInterface returned 0x80004002].
*****************************************************
Any help will be appreciated
thanks
-sriniHi srinivas,
Check the following registry key and make sure it is set to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Providers\ADSDSOObject
Thanks,
Chandan
"srinivas" wrote:
> I am trying to replicate the execution of a stored procedure and hence am using isolation level of serializable as recommended by BOL for purge operations.
> This following code works fine when executed on the server ( logging in via terminal services) bu gives me an error when executed thru Query Analyzer.
> Really puzzled.
> ________________________________________________________
> SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
> GO
> begin transaction
> exec dbo.DeleteJobRunResults @.SourceSystem = 'GSP Risk Engine',
> @.SourceSystemCode = '13397'
> commit transaction
> go
> _________________________________________________________
> ***************************************************
> Server: Msg 7390, Level 16, State 1, Line 1
> The requested operation could not be performed because the OLE DB provider 'ADSDSOObject' does not support the required transaction interface.
> OLE DB error trace [OLE/DB Provider 'ADSDSOObject' IUnknown::QueryInterface returned 0x80004002].
> *****************************************************
> Any help will be appreciated
> thanks
> -srini

error 7390 when isolation level is set to serializable...

I am trying to replicate the execution of a stored procedure and hence am us
ing isolation level of serializable as recommended by BOL for purge operatio
ns.
This following code works fine when executed on the server ( logging in via
terminal services) bu gives me an error when executed thru Query Analyzer.
Really puzzled.
________________________________________
________________
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
GO
begin transaction
exec dbo.DeleteJobRunResults @.SourceSystem = 'GSP Risk Engine',
@.SourceSystemCode = '13397'
commit transaction
go
________________________________________
_________________
****************************************
***********
Server: Msg 7390, Level 16, State 1, Line 1
The requested operation could not be performed because the OLE DB provider '
ADSDSOObject' does not support the required transaction interface.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' IUnknown::QueryInterf
ace returned 0x80004002].
****************************************
*************
Any help will be appreciated
thanks
-sriniHi srinivas,
Check the following registry key and make sure it is set to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\ Providers\ADSDSOObject
Thanks,
Chandan
"srinivas" wrote:

> I am trying to replicate the execution of a stored procedure and hence am
using isolation level of serializable as recommended by BOL for purge operat
ions.
> This following code works fine when executed on the server ( logging in vi
a terminal services) bu gives me an error when executed thru Query Analyzer.
> Really puzzled.
> ________________________________________
________________
> SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
> GO
> begin transaction
> exec dbo.DeleteJobRunResults @.SourceSystem = 'GSP Risk Engine',
> @.SourceSystemCode = '13397'
> commit transaction
> go
> ________________________________________
_________________
> ****************************************
***********
> Server: Msg 7390, Level 16, State 1, Line 1
> The requested operation could not be performed because the OLE DB provider
'ADSDSOObject' does not support the required transaction interface.
> OLE DB error trace [OLE/DB Provider 'ADSDSOObject' IUnknown::QueryInte
rface returned 0x80004002].
> ****************************************
*************
> Any help will be appreciated
> thanks
> -srini

error 7390 when isolation level is set to serializable...

I am trying to replicate the execution of a stored procedure and hence am using isolation level of serializable as recommended by BOL for purge operations.
This following code works fine when executed on the server ( logging in via terminal services) bu gives me an error when executed thru Query Analyzer.
Really puzzled.
__________________________________________________ ______
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
GO
begin transaction
exec dbo.DeleteJobRunResults @.SourceSystem = 'GSP Risk Engine',
@.SourceSystemCode = '13397'
commit transaction
go
__________________________________________________ _______
************************************************** *
Server: Msg 7390, Level 16, State 1, Line 1
The requested operation could not be performed because the OLE DB provider 'ADSDSOObject' does not support the required transaction interface.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' IUnknown::QueryInterface returned 0x80004002].
************************************************** ***
Any help will be appreciated
thanks
-srini
Is DeleteJobRunResults performing a linked server query using the ADSI
OLEDB provider? This is what the ADSDSOObject is referring to. What is the
MDAC version on the SQL Server and on the machine where Query Analyzer is
running on? If the MDAC on the client is at a lower version, then upgrade
it so that it is at the same level as the SQL Server. You can use Component
Checker to get the MDAC versions. It is available at
http://www.microsoft.com/downloads/d...df6-4a21-4b43-
bf53-14332ef092c9&displaylang=en.
Regards,
Farooq Mahmud [MS SQL Support]
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.