August 21, 2009 at 4:43 am
sysftinds
sysowners
sysprivs
sysschobjs
syscerts
systypedsubobjs
sysbinobjs
sysclsobjs
sysremsvcbinds
sysxmitqueue
sysrts
sysdercv
sysqnames
sysxmlcomponent
sysxmlfacet
sysxmlplacement
sysobjkeycrypts
sysasymkeys
sysbinsubobjs
queue_messages_1413632129
queue_messages_1445632243
queue_messages_1477632357
August 21, 2009 at 5:06 am
Hidden and not directly queryable. None of the system tables in sql 2005 or above are directly queryable.
Why do you want to know?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2009 at 5:11 am
Look below problem
http://qa.sqlservercentral.com/Forums/Topic774014-146-1.aspx
August 21, 2009 at 5:13 am
panwar.jt (8/21/2009)
http://qa.sqlservercentral.com/Forums/Topic774014-146-1.aspx%5B/quote%5D
I don't see anything to do with system tables in that thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2009 at 5:19 am
Dear Gail
that is my actual problem
I did every thing my DB
and then check that there some few other collation for these system table.
may be these table is creating trouble to me.
This is very strangble problem
August 21, 2009 at 5:25 am
Panwar,
SQL Server 2005 does not allow for direct user access to the underlying database and catalog system tables as was the case in previous versions of SQL Server, where you could issue the statement:
EXEC master..sp_configure 'Allow Updates', 1
RECONFIGURE WITH OVERRIDE
These tables can now only be accessed via Direct Administrator Connection (or DAC).
=======================================================================================
Visit my technical reference; you might find some of your issues already documented.
August 21, 2009 at 5:27 am
You can't change the collation of system tables. In fact, you can't change system tables.
I see you're changing collation, what specific problems/concerns do you have that you want/need to change the collation of system tables? Are you getting errors when querying? When doing DB maintenance?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2009 at 5:28 am
suleman_3014 (8/21/2009)
These tables can now only be accessed via Direct Administrator Connection (or DAC).
Using the DAC doesn't allow you to modify the system tables. Even on SQL 2000 (iirc) altering the design of a system table (to change collation) was not possible.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2009 at 5:34 am
Gail
I have no intention to change collation of system table.
look below proc
Suppose I had a proc attached with a report
Create Proc ProcName
@PAr1 varchar(4)
@PAr2 varchar(4)
@PAr3 varchar(4)
as
if @Par1=''
begin
select '' Par1,''Par2,''Par3
return
end
Craete #Temp
(
PAr1 varchar(4)
PAr2 varchar(4)
PAr3 varchar(4)
)
Now some cursor runs and Data insert into #Temp
Select * from #Temp
---Till Now report was printing only one chartor of each return dataset
I change proc as below and it working fine
Create Proc ProcName
@PAr1 varchar(4)
@PAr2 varchar(4)
@PAr3 varchar(4)
as
if @Par1=''
begin
select ' ' Par1,' 'Par2,' ' Par3----Notice paas blank space and report work fine
end
Craete #Temp
(
PAr1 varchar(4)
PAr2 varchar(4)
PAr3 varchar(4)
)
August 21, 2009 at 5:53 am
Gail,
I assumed the issue was only to query the base tables, and not modify. as per his first request.
I agree with you, we cannot change these tables even with DAC.
Regards,
S
=======================================================================================
Visit my technical reference; you might find some of your issues already documented.
August 21, 2009 at 6:03 am
Question is that
IF control is not steping in
following condition
Becoz @Par1 never be blank
if @Par1=''
begin
select ' ' Par1,' 'Par2,' ' Par3----Notice paas blank space and report work fine
end
then why it is impacting on report even if i make comment these condition report works fine
feeling very helpless
August 21, 2009 at 6:16 am
This doen't look like it has anything to do with the system tables, and it's also asked here: http://qa.sqlservercentral.com/Forums/Topic774014-146-1.aspx
No more replies here unless they're related to the system tables please.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2009 at 6:19 am
but problem is still there
August 21, 2009 at 7:15 am
panwar.jt (8/21/2009)
but problem is still there
One problem, one thread. Having multiple threads for the same problem just wastes people's time as they answer stuff already answered.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2009 at 7:41 am
Taken to http://qa.sqlservercentral.com/Forums/Topic774014-146-1.aspx. Too much confusion I think. Let's do as GilaMonster says and only use one thread for this one.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply