I have a SQL Server 6.5 installation that I want to
migrate to sql 2000. I've installed sql 2000 on the same
machine, and next I'm starting the database upgrade.
Just before starting this process, the installation gives
me a "Warning" :
****************
Inconsistency Report for database : yumyum
****************
dbo.sp_ImporterEnteteCommande
Procedure
Text Not found
--
What can I do for that?Thanks for your Answer.
To bypass this problems here is what i've done (but not
sure if it's the best idea)
-generated a sql script of every stored proc in 6.5
-deleted every stored proc in 6.5
-migrating database to 2000
-creating every stored proc from the sql script of my
stored proc.
The migrating process gives me no warning and seems
succesfull. Then I just goes to the login section and re-
enter every password.
The problem is that on a client computer there is a c++
programm connecting to the sql server through odbc. He
is crashing at startup. After debugging this c++
programm, I've seen that the faulty lines is this one:
PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
CRecordset::none);
If you have any clue about this issue, let me know..
thanks!
Note: I have already tryed some version of Mdac component
in the client machine (running nt4) but no sucess.
>--Original Message--
>The upgrade needs the text to recreate the stored
procedure. As it is, this
>proc will not upgrade successfully. You can drop it and
the error will go
>away.
>For your new database, you should go to wherever you
keep the source of you
>stored procedures and recreate it from source code.
>(FWIW - In SQL 6.5 I believe that the text of a stored
procedure could be
>deleted as a 'security' measure to keep the code
hidden. From 7.0 forward
>this no longer works.)
>Russell Fields
>"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com>
wrote in message
>news:0a8c01c35daf$01514870$a301280a@.phx.gbl...
>> I have a SQL Server 6.5 installation that I want to
>> migrate to sql 2000. I've installed sql 2000 on the
same
>> machine, and next I'm starting the database upgrade.
>> Just before starting this process, the installation
gives
>> me a "Warning" :
>> ****************
>> Inconsistency Report for database : yumyum
>> ****************
>> dbo.sp_ImporterEnteteCommande
>> Procedure
>> Text Not found
>> --
>> What can I do for that?
>
>.
>|||Jean-Francois,
Well, I am not a C++ guy, so I am not much help here. Is the C++ crashing
on its own? (Could it be an ODBC or OLE DB error in setup?) Or is the SQL
Server failing to return it the expected result and crashing because of
that?
I would be interested in what is inside strSQL. It would be interesting if
it was a call to the stored procedure that had no text. (If, when you say
"generated a sql script of every stored proc in 6.5" you mean that you
generated them from the database, any procedure that had no text in
syscomments would not be recreated.)
Russell Fields
"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com> wrote in message
news:0b2d01c35db8$108122d0$a301280a@.phx.gbl...
> Thanks for your Answer.
> To bypass this problems here is what i've done (but not
> sure if it's the best idea)
> -generated a sql script of every stored proc in 6.5
> -deleted every stored proc in 6.5
> -migrating database to 2000
> -creating every stored proc from the sql script of my
> stored proc.
> The migrating process gives me no warning and seems
> succesfull. Then I just goes to the login section and re-
> enter every password.
> The problem is that on a client computer there is a c++
> programm connecting to the sql server through odbc. He
> is crashing at startup. After debugging this c++
> programm, I've seen that the faulty lines is this one:
> PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
> CRecordset::none);
> If you have any clue about this issue, let me know..
> thanks!
> Note: I have already tryed some version of Mdac component
> in the client machine (running nt4) but no sucess.
>
> >--Original Message--
> >The upgrade needs the text to recreate the stored
> procedure. As it is, this
> >proc will not upgrade successfully. You can drop it and
> the error will go
> >away.
> >
> >For your new database, you should go to wherever you
> keep the source of you
> >stored procedures and recreate it from source code.
> >
> >(FWIW - In SQL 6.5 I believe that the text of a stored
> procedure could be
> >deleted as a 'security' measure to keep the code
> hidden. From 7.0 forward
> >this no longer works.)
> >
> >Russell Fields
> >"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com>
> wrote in message
> >news:0a8c01c35daf$01514870$a301280a@.phx.gbl...
> >> I have a SQL Server 6.5 installation that I want to
> >> migrate to sql 2000. I've installed sql 2000 on the
> same
> >> machine, and next I'm starting the database upgrade.
> >>
> >> Just before starting this process, the installation
> gives
> >> me a "Warning" :
> >>
> >> ****************
> >> Inconsistency Report for database : yumyum
> >> ****************
> >> dbo.sp_ImporterEnteteCommande
> >> Procedure
> >> Text Not found
> >> --
> >>
> >> What can I do for that?
> >
> >
> >.
> >|||If you are getting an unhandled SQL exception, you might try a Profiler
trace to spot the errant SQL statement.
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com> wrote in message
news:0b2d01c35db8$108122d0$a301280a@.phx.gbl...
> Thanks for your Answer.
> To bypass this problems here is what i've done (but not
> sure if it's the best idea)
> -generated a sql script of every stored proc in 6.5
> -deleted every stored proc in 6.5
> -migrating database to 2000
> -creating every stored proc from the sql script of my
> stored proc.
> The migrating process gives me no warning and seems
> succesfull. Then I just goes to the login section and re-
> enter every password.
> The problem is that on a client computer there is a c++
> programm connecting to the sql server through odbc. He
> is crashing at startup. After debugging this c++
> programm, I've seen that the faulty lines is this one:
> PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
> CRecordset::none);
> If you have any clue about this issue, let me know..
> thanks!
> Note: I have already tryed some version of Mdac component
> in the client machine (running nt4) but no sucess.
>
> >--Original Message--
> >The upgrade needs the text to recreate the stored
> procedure. As it is, this
> >proc will not upgrade successfully. You can drop it and
> the error will go
> >away.
> >
> >For your new database, you should go to wherever you
> keep the source of you
> >stored procedures and recreate it from source code.
> >
> >(FWIW - In SQL 6.5 I believe that the text of a stored
> procedure could be
> >deleted as a 'security' measure to keep the code
> hidden. From 7.0 forward
> >this no longer works.)
> >
> >Russell Fields
> >"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com>
> wrote in message
> >news:0a8c01c35daf$01514870$a301280a@.phx.gbl...
> >> I have a SQL Server 6.5 installation that I want to
> >> migrate to sql 2000. I've installed sql 2000 on the
> same
> >> machine, and next I'm starting the database upgrade.
> >>
> >> Just before starting this process, the installation
> gives
> >> me a "Warning" :
> >>
> >> ****************
> >> Inconsistency Report for database : yumyum
> >> ****************
> >> dbo.sp_ImporterEnteteCommande
> >> Procedure
> >> Text Not found
> >> --
> >>
> >> What can I do for that?
> >
> >
> >.
> >|||Jean-Francois,
The texts for stored procedures are stored in the syscomments table.
Without the texts, it is not possible to create a script for the stored
procedures in question since the scripting tool cannot create the TSQL
needed.
Regarding your problem, if the stored procedure exists and the things it
references exist, then I have no idea. Dan's recommendation to trace your
efforts with Profiler is the best idea I have.
Russell Fields
"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com> wrote in message
news:06af01c36003$b4bf4c30$a301280a@.phx.gbl...
> Sorry I didn't paste the good c++ line that is crashing..
> here it is:
> PointeurSecuriteSet->Open(CRecordset::dynaset, "{call
> sp_SelectSecurite()}", CRecordset::none);
> It is a call to a simple stored procedure with no params.
> About the stored proc, the way i have transfer them
> between sql 6.5 to sql 2000 is:
> -I just generated a sql script from 6.5;
> -in sql 2000, I copied the content of the sql script in
> the query analyser and run it.
> Like you said, the "no text" error may not be solved this
> way.. Where are defined those "text" and what are they?
> Thanks!!
>
> >--Original Message--
> >Jean-Francois,
> >
> >Well, I am not a C++ guy, so I am not much help here.
> Is the C++ crashing
> >on its own? (Could it be an ODBC or OLE DB error in
> setup?) Or is the SQL
> >Server failing to return it the expected result and
> crashing because of
> >that?
> >
> >I would be interested in what is inside strSQL. It
> would be interesting if
> >it was a call to the stored procedure that had no text.
> (If, when you say
> >"generated a sql script of every stored proc in 6.5" you
> mean that you
> >generated them from the database, any procedure that had
> no text in
> >syscomments would not be recreated.)
> >
> >Russell Fields
> >
> >
> >"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com>
> wrote in message
> >news:0b2d01c35db8$108122d0$a301280a@.phx.gbl...
> >> Thanks for your Answer.
> >> To bypass this problems here is what i've done (but not
> >> sure if it's the best idea)
> >> -generated a sql script of every stored proc in 6.5
> >> -deleted every stored proc in 6.5
> >> -migrating database to 2000
> >> -creating every stored proc from the sql script of my
> >> stored proc.
> >>
> >> The migrating process gives me no warning and seems
> >> succesfull. Then I just goes to the login section and
> re-
> >> enter every password.
> >>
> >> The problem is that on a client computer there is a c++
> >> programm connecting to the sql server through odbc. He
> >> is crashing at startup. After debugging this c++
> >> programm, I've seen that the faulty lines is this one:
> >>
> >> PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
> >> CRecordset::none);
> >>
> >> If you have any clue about this issue, let me know..
> >> thanks!
> >>
> >> Note: I have already tryed some version of Mdac
> component
> >> in the client machine (running nt4) but no sucess.
> >>
> >>
> >> >--Original Message--
> >> >The upgrade needs the text to recreate the stored
> >> procedure. As it is, this
> >> >proc will not upgrade successfully. You can drop it
> and
> >> the error will go
> >> >away.
> >> >
> >> >For your new database, you should go to wherever you
> >> keep the source of you
> >> >stored procedures and recreate it from source code.
> >> >
> >> >(FWIW - In SQL 6.5 I believe that the text of a stored
> >> procedure could be
> >> >deleted as a 'security' measure to keep the code
> >> hidden. From 7.0 forward
> >> >this no longer works.)
> >> >
> >> >Russell Fields
> >> >"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com>
> >> wrote in message
> >> >news:0a8c01c35daf$01514870$a301280a@.phx.gbl...
> >> >> I have a SQL Server 6.5 installation that I want to
> >> >> migrate to sql 2000. I've installed sql 2000 on the
> >> same
> >> >> machine, and next I'm starting the database upgrade.
> >> >>
> >> >> Just before starting this process, the installation
> >> gives
> >> >> me a "Warning" :
> >> >>
> >> >> ****************
> >> >> Inconsistency Report for database : yumyum
> >> >> ****************
> >> >> dbo.sp_ImporterEnteteCommande
> >> >> Procedure
> >> >> Text Not found
> >> >> --
> >> >>
> >> >> What can I do for that?
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||The c++ programm was not working because the call to a
stored procedure in SQL 2000 must be without () if you
don't have parameters.
sp_SelectSecurite() must be :
sp_SelectSecurite
It's working well now, even with the inconsistency error.
Thanks guys