|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Bug in Enterprise Manager (SQL 2000)I have installed Enterprise Manager ver 8.0 (SQL 2000) and installed SP4.
Using Enterprise Manager I manually typed in the Query (Action > Open Table > Query) select * from syscomments where text like '%COA%' Currently this gives me three records with the field [text] shown as empty I used the same query in Query Analyser and the [text] field now has data. Can someone please explain this? How do I fix this? On 11.09.2006 13:58, Herbert Schroder wrote:
Show quote > I have installed Enterprise Manager ver 8.0 (SQL 2000) and installed SP4. Different user? Different database?> > Using Enterprise Manager I manually typed in the Query > (Action > Open Table > Query) > > select * from syscomments > where text like '%COA%' > > Currently this gives me three records with the field [text] shown as empty > > I used the same query in Query Analyser and the [text] field now has data. > > Can someone please explain this? > How do I fix this? > robert Hi Robert
Same User, same PC , same Database Show quote "Robert Klemme" wrote: > On 11.09.2006 13:58, Herbert Schroder wrote: > > I have installed Enterprise Manager ver 8.0 (SQL 2000) and installed SP4. > > > > Using Enterprise Manager I manually typed in the Query > > (Action > Open Table > Query) > > > > select * from syscomments > > where text like '%COA%' > > > > Currently this gives me three records with the field [text] shown as empty > > > > I used the same query in Query Analyser and the [text] field now has data. > > > > Can someone please explain this? > > How do I fix this? > > > > Different user? Different database? > > robert > On 11.09.2006 14:13, Herbert Schroder wrote:
> Hi Robert Maybe a limit on the column width. Try to query the large column with > Same User, same PC , same Database LEFT to truncate long values. Generally EM is not a great tool for dealing with DML and data. I'd use QA for that anyway. Kind regards robert Thanks For the response Robert and Hari
I have just tried the identical query on another workstation and there it worked 100% both in Enterprise Manager as well as Query Analyser - as far as I can see there are no differences between this second workstation and mine. The reason why I like using the Enterprise Manager for this query, is that you can expand the width of the row and thereby see all the text ( In this case Stored Procedure) Show quote "Robert Klemme" wrote: > On 11.09.2006 14:13, Herbert Schroder wrote: > > Hi Robert > > Same User, same PC , same Database > > Maybe a limit on the column width. Try to query the large column with > LEFT to truncate long values. > > Generally EM is not a great tool for dealing with DML and data. I'd use > QA for that anyway. > > Kind regards > > robert > When using Query Analyzer, go to the [Tools] menu, select [Option], then
[Results] and change the [Maximum Characters per Column] in order to be able to see the entire column for wide columns. And EM is 'unreliable' for a data manipulation tool. QA is the best tool for the job. -- Show quoteArnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous "Herbert Schroder" <HerbertSchro***@discussions.microsoft.com> wrote in message news:11EE54BD-7708-4933-8474-F5EE860B2221@microsoft.com... > Thanks For the response Robert and Hari > > I have just tried the identical query on another workstation and there it > worked 100% both in Enterprise Manager as well as Query Analyser - as far > as > I can see there are no differences between this second workstation and > mine. > > The reason why I like using the Enterprise Manager for this query, is that > you can expand the width of the row and thereby see all the text ( In > this > case Stored Procedure) > > "Robert Klemme" wrote: > >> On 11.09.2006 14:13, Herbert Schroder wrote: >> > Hi Robert >> > Same User, same PC , same Database >> >> Maybe a limit on the column width. Try to query the large column with >> LEFT to truncate long values. >> >> Generally EM is not a great tool for dealing with DML and data. I'd use >> QA for that anyway. >> >> Kind regards >> >> robert >> Hi Arnie
Thanks my QA works fine and judging by the response, I guess I will just have to "accept" that I'm stuck with this problem regarding EM. I must say however it is highly frustrating to see this working on other workstations and not mine! Regards Herbert Show quote "Arnie Rowland" wrote: > When using Query Analyzer, go to the [Tools] menu, select [Option], then > [Results] and change the [Maximum Characters per Column] in order to be able > to see the entire column for wide columns. > > And EM is 'unreliable' for a data manipulation tool. QA is the best tool for > the job. > > -- > Arnie Rowland, Ph.D. > Westwood Consulting, Inc > > Most good judgment comes from experience. > Most experience comes from bad judgment. > - Anonymous > > > "Herbert Schroder" <HerbertSchro***@discussions.microsoft.com> wrote in > message news:11EE54BD-7708-4933-8474-F5EE860B2221@microsoft.com... > > Thanks For the response Robert and Hari > > > > I have just tried the identical query on another workstation and there it > > worked 100% both in Enterprise Manager as well as Query Analyser - as far > > as > > I can see there are no differences between this second workstation and > > mine. > > > > The reason why I like using the Enterprise Manager for this query, is that > > you can expand the width of the row and thereby see all the text ( In > > this > > case Stored Procedure) > > > > "Robert Klemme" wrote: > > > >> On 11.09.2006 14:13, Herbert Schroder wrote: > >> > Hi Robert > >> > Same User, same PC , same Database > >> > >> Maybe a limit on the column width. Try to query the large column with > >> LEFT to truncate long values. > >> > >> Generally EM is not a great tool for dealing with DML and data. I'd use > >> QA for that anyway. > >> > >> Kind regards > >> > >> robert > >> > > > There is an small possibility that this may be related to memory issues. You
might reboot to clear you system's memory -this is just a 'wag'. -- Show quoteArnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous "Herbert Schroder" <HerbertSchro***@discussions.microsoft.com> wrote in message news:B68119F6-8974-4C6E-B775-1AD0C1185730@microsoft.com... > Hi Arnie > > Thanks my QA works fine and judging by the response, I guess I will just > have to "accept" that I'm stuck with this problem regarding EM. > I must say however it is highly frustrating to see this working on other > workstations and not mine! > > Regards > Herbert > > "Arnie Rowland" wrote: > >> When using Query Analyzer, go to the [Tools] menu, select [Option], then >> [Results] and change the [Maximum Characters per Column] in order to be >> able >> to see the entire column for wide columns. >> >> And EM is 'unreliable' for a data manipulation tool. QA is the best tool >> for >> the job. >> >> -- >> Arnie Rowland, Ph.D. >> Westwood Consulting, Inc >> >> Most good judgment comes from experience. >> Most experience comes from bad judgment. >> - Anonymous >> >> >> "Herbert Schroder" <HerbertSchro***@discussions.microsoft.com> wrote in >> message news:11EE54BD-7708-4933-8474-F5EE860B2221@microsoft.com... >> > Thanks For the response Robert and Hari >> > >> > I have just tried the identical query on another workstation and there >> > it >> > worked 100% both in Enterprise Manager as well as Query Analyser - as >> > far >> > as >> > I can see there are no differences between this second workstation and >> > mine. >> > >> > The reason why I like using the Enterprise Manager for this query, is >> > that >> > you can expand the width of the row and thereby see all the text ( In >> > this >> > case Stored Procedure) >> > >> > "Robert Klemme" wrote: >> > >> >> On 11.09.2006 14:13, Herbert Schroder wrote: >> >> > Hi Robert >> >> > Same User, same PC , same Database >> >> >> >> Maybe a limit on the column width. Try to query the large column with >> >> LEFT to truncate long values. >> >> >> >> Generally EM is not a great tool for dealing with DML and data. I'd >> >> use >> >> QA for that anyway. >> >> >> >> Kind regards >> >> >> >> robert >> >> >> >> >> Hi Arnie
Nope already tried that. Show quote "Arnie Rowland" wrote: > There is an small possibility that this may be related to memory issues. You > might reboot to clear you system's memory -this is just a 'wag'. > > -- > Arnie Rowland, Ph.D. > Westwood Consulting, Inc > > Most good judgment comes from experience. > Most experience comes from bad judgment. > - Anonymous > > > "Herbert Schroder" <HerbertSchro***@discussions.microsoft.com> wrote in > message news:B68119F6-8974-4C6E-B775-1AD0C1185730@microsoft.com... > > Hi Arnie > > > > Thanks my QA works fine and judging by the response, I guess I will just > > have to "accept" that I'm stuck with this problem regarding EM. > > I must say however it is highly frustrating to see this working on other > > workstations and not mine! > > > > Regards > > Herbert > > > > "Arnie Rowland" wrote: > > > >> When using Query Analyzer, go to the [Tools] menu, select [Option], then > >> [Results] and change the [Maximum Characters per Column] in order to be > >> able > >> to see the entire column for wide columns. > >> > >> And EM is 'unreliable' for a data manipulation tool. QA is the best tool > >> for > >> the job. > >> > >> -- > >> Arnie Rowland, Ph.D. > >> Westwood Consulting, Inc > >> > >> Most good judgment comes from experience. > >> Most experience comes from bad judgment. > >> - Anonymous > >> > >> > >> "Herbert Schroder" <HerbertSchro***@discussions.microsoft.com> wrote in > >> message news:11EE54BD-7708-4933-8474-F5EE860B2221@microsoft.com... > >> > Thanks For the response Robert and Hari > >> > > >> > I have just tried the identical query on another workstation and there > >> > it > >> > worked 100% both in Enterprise Manager as well as Query Analyser - as > >> > far > >> > as > >> > I can see there are no differences between this second workstation and > >> > mine. > >> > > >> > The reason why I like using the Enterprise Manager for this query, is > >> > that > >> > you can expand the width of the row and thereby see all the text ( In > >> > this > >> > case Stored Procedure) > >> > > >> > "Robert Klemme" wrote: > >> > > >> >> On 11.09.2006 14:13, Herbert Schroder wrote: > >> >> > Hi Robert > >> >> > Same User, same PC , same Database > >> >> > >> >> Maybe a limit on the column width. Try to query the large column with > >> >> LEFT to truncate long values. > >> >> > >> >> Generally EM is not a great tool for dealing with DML and data. I'd > >> >> use > >> >> QA for that anyway. > >> >> > >> >> Kind regards > >> >> > >> >> robert > >> >> > >> > >> > >> > > > Hi,
Probably enterprise manager should be having issue with displaying big texts. So identify the object and thne use sp_helptext to display... select object_name(id) from syscomments where text like '%COA%' This will give you the object which contains text COA. After that use the sp_helptext. The above command must work in enterprise manager as well.. Thanks Hari SQL Server MVP Show quote "Robert Klemme" <shortcut***@googlemail.com> wrote in message news:e%23zoBqZ1GHA.1256@TK2MSFTNGP02.phx.gbl... > On 11.09.2006 13:58, Herbert Schroder wrote: >> I have installed Enterprise Manager ver 8.0 (SQL 2000) and installed >> SP4. >> >> Using Enterprise Manager I manually typed in the Query (Action > Open >> Table > Query) >> >> select * from syscomments where text like '%COA%' Currently this gives >> me three records with the field [text] shown as empty >> >> I used the same query in Query Analyser and the [text] field now has >> data. >> >> Can someone please explain this? How do I fix this? >> > > Different user? Different database? > > robert |
|||||||||||||||||||||||