Insert...exec doesn't work properly

Hello
MSSQL 2000 EE + SP3 on Windows 2000 AS + SP4
I have certain procedure which can't be reproduced
using my common technique.
CREATE table #t (text nvarchar(4000))
insert into #t exec sp_helptext 'objectname'
SELECT * FROM #T
DROP TABLE #T
exec sp_helptext 'objectname'
Two output resultsets are DIFFERENT!
Row order in temporary table doesn't coincide with real
row order (two rows with numbers 119 and 120 inserted
into positions 68 and 69).
This is critical for me!
Does anyone know the cause of this or any workaround?
Thanks,
Serge ShakhovThere is no way to totally control how rows are stored in a table. The
order in which you insert them has little to do with how they are stored or
placed into the pages on disk. Even with a clustered index you are not
guaranteed for everything to be physically and logically in order. So if
you want to get them out of a table in a specific order then you need to
specify an ORDER BY clause.
--
Andrew J. Kelly
SQL Server MVP
"Serge Shakhov" <REMOVETHIS_ACETYLENE@.mail.ru> wrote in message
news:48dgmb.5o3.ln@.proxyserver.ctd.mmk.chel.su...
> Hello
> MSSQL 2000 EE + SP3 on Windows 2000 AS + SP4
> I have certain procedure which can't be reproduced
> using my common technique.
> CREATE table #t (text nvarchar(4000))
> insert into #t exec sp_helptext 'objectname'
> SELECT * FROM #T
> DROP TABLE #T
> exec sp_helptext 'objectname'
> Two output resultsets are DIFFERENT!
> Row order in temporary table doesn't coincide with real
> row order (two rows with numbers 119 and 120 inserted
> into positions 68 and 69).
> This is critical for me!
> Does anyone know the cause of this or any workaround?
> Thanks,
> Serge Shakhov
>|||Hello
> MSSQL 2000 EE + SP3 on Windows 2000 AS + SP4
> I have certain procedure which can't be reproduced
> using my common technique.
> CREATE table #t (text nvarchar(4000))
> insert into #t exec sp_helptext 'objectname'
> SELECT * FROM #T
> DROP TABLE #T
> exec sp_helptext 'objectname'
> Two output resultsets are DIFFERENT!
I still don't know the reason of this behavior
but now I know that changing nvarchar datatype
to varchar forces server to work properly.
This can be considered as workaround.
Serge Shakhovsql

insert update problem

I have a couple Windows 2000 servers SP4, that cannot insert/updated to a
SQL 2000 SP3a server on a Windows 2003 server. Windows 2003 server was
installed fresh. Upgraded to 2000 to 2003 Windows servers with SQL 2000
SP3a work fine. I have ran MDAC 2.8 on the Windows 2000 SP4 server to see
if that would help, but it did not. Any ideas? Thanks, Marc
What query are you executing? What error or unexpected behavior do you get?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
sql

insert temp with linked server

Hi,
I have a problem with insert temp table with linked server. I have a sql
2000 with sp4 and I have a dozen linked servers. All of them work except one
which is running on windows 2003. I didn't get any error message and the
transaction just open and never stop. I have to kill it manually.
I have checked the DTC on windows 2003, which is quite different. I am sure
that the settings are all right, including tricks like network service, etc.
I guess it might be some kind of bug but I just can't find anything about it
after searching Google and MS KB.
Is anyone running same problem or has any clue,
Thanks,
m
I think I've got more or less the same problem.
Since I've load 2000 SP4 the data return from a SP called to a Default
instance is not the same as in the case of a Named Instance. Instead it does
not return a error but return false results.
IOW :
Before SP4 --> No Problems
After SP4 -->
exec[missql01].SERVER_CONTROL_DB.DBO.sp_Is_Job_Running
'Free_Disk_Space_Watcher',@.Result OUTPUT
/* For any Default Instance : Return Correct Results */
exec [M24BLACKB01\BES_001].SERVER_CONTROL_DB.DBO.sp_Is_Job_Running
'Free_Disk_Space_Watcher',@.Result OUTPUT
/* For Any Named Instance : Return INCORRECT Results */
Same command on Local server M24BLACKB01\BES_001:
exec SERVER_CONTROL_DB.DBO.sp_Is_Job_Running
'Free_Disk_Space_Watcher',@.Result OUTPUT
/* Return CORRECT Results */
"dp" wrote:

> Hi,
> I have a problem with insert temp table with linked server. I have a sql
> 2000 with sp4 and I have a dozen linked servers. All of them work except one
> which is running on windows 2003. I didn't get any error message and the
> transaction just open and never stop. I have to kill it manually.
> I have checked the DTC on windows 2003, which is quite different. I am sure
> that the settings are all right, including tricks like network service, etc.
> I guess it might be some kind of bug but I just can't find anything about it
> after searching Google and MS KB.
> Is anyone running same problem or has any clue,
> Thanks,
>
> --
> m

insert temp with linked server

Hi,
I have a problem with insert temp table with linked server. I have a sql
2000 with sp4 and I have a dozen linked servers. All of them work except one
which is running on windows 2003. I didn't get any error message and the
transaction just open and never stop. I have to kill it manually.
I have checked the DTC on windows 2003, which is quite different. I am sure
that the settings are all right, including tricks like network service, etc.
I guess it might be some kind of bug but I just can't find anything about it
after searching Google and MS KB.
Is anyone running same problem or has any clue,
Thanks,
mI think I've got more or less the same problem.
Since I've load 2000 SP4 the data return from a SP called to a Default
instance is not the same as in the case of a Named Instance. Instead it does
not return a error but return false results.
IOW :
Before SP4 --> No Problems
After SP4 -->
exec[missql01].SERVER_CONTROL_DB.DBO.sp_Is_Job_Running
'Free_Disk_Space_Watcher',@.Result OUTPUT
/* For any Default Instance : Return Correct Results */
exec [M24BLACKB01\BES_001].SERVER_CONTROL_DB.DBO.sp_Is_Job_Running
'Free_Disk_Space_Watcher',@.Result OUTPUT
/* For Any Named Instance : Return INCORRECT Results */
Same command on Local server M24BLACKB01\BES_001:
exec SERVER_CONTROL_DB.DBO.sp_Is_Job_Running
'Free_Disk_Space_Watcher',@.Result OUTPUT
/* Return CORRECT Results */
"dp" wrote:

> Hi,
> I have a problem with insert temp table with linked server. I have a sql
> 2000 with sp4 and I have a dozen linked servers. All of them work except o
ne
> which is running on windows 2003. I didn't get any error message and the
> transaction just open and never stop. I have to kill it manually.
> I have checked the DTC on windows 2003, which is quite different. I am sur
e
> that the settings are all right, including tricks like network service, et
c.
> I guess it might be some kind of bug but I just can't find anything about
it
> after searching Google and MS KB.
> Is anyone running same problem or has any clue,
> Thanks,
>
> --
> m