cannot get data from syscomments

Hi!
My user cannot retreive data from syscomments system view., but can do
it from sysobjects. What can be done wrong when upgrading from ms sql
7 to ms sql 5k5? The same upgrade process was done on 400 servers and
problem is known only on seveal
Syscomments is no more an available view: to view stored procedures and
triggers definition you should query the cataloged view sys.sql_modules, or
use OBJECT DEFINITION or the sp_helptext system stored procedure.
See the related topics on the Books on Line.
Gilberto Zampatti
"Jacek.Piechucki@.gmail.com" wrote:

> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal
>
|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180006384.209339.161890@.q75g2000hsh.googlegr oups.com...
> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal
>
Since these are 'undocumented' views I believe, their functionality changes
from version to version.
SQL 2005 has changed a lot of this and has some views for backwards
compatibility,
But most likely the code needs to be updated for 2005.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||If so, why do I have problems only on several from whole 400 servers?
On more tahn 380 others everything works well.
What can be valuable: all of our databses (except of master) work with
compatibility level of SQL Server 7.0.
On 24 Maj, 15:36, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> Syscomments is no more an available view: to view stored procedures and
> triggers definition you should query the cataloged view sys.sql_modules, or
> use OBJECT DEFINITION or the sp_helptext system stored procedure.
> See the related topics on the Books on Line.
> Gilberto Zampatti
>
> "Jacek.Piechu...@.gmail.com" wrote:
> - Poka cytowany tekst -
|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180018413.412996.83620@.w5g2000hsg.googlegrou ps.com...
> If so, why do I have problems only on several from whole 400 servers?
It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
It sounded like it was only breaking on the one.
In any event, most likely a permissions problem.

> On more tahn 380 others everything works well.
> What can be valuable: all of our databses (except of master) work with
> compatibility level of SQL Server 7.0.
That really doesn't matter here.
I'd check to see if the permissions are the same across all 400 servers.

>
> On 24 Maj, 15:36, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Anything related to permissions is identical on all servers.
On 24 Maj, 17:21, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.com> wrote:
> <Jacek.Piechu...@.gmail.com> wrote in message
> news:1180018413.412996.83620@.w5g2000hsg.googlegrou ps.com...
>
> It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
> It sounded like it was only breaking on the one.
> In any event, most likely a permissions problem.
>
> That really doesn't matter here.
> I'd check to see if the permissions are the same across all 400 servers.
>
>
>
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html- Ukryj cytowany tekst -
> - Poka cytowany tekst -