Viewing 15 posts - 136 through 150 (of 190 total)
DBCC will generate a report for you whether having issue or not.
July 11, 2008 at 12:11 pm
msdb.dbo.sysjobhistory
msdb.dbo.sysjobs
msdb.dob.sysjobschedules......
July 10, 2008 at 2:52 pm
Besides the above, plus Network, Security.....
July 10, 2008 at 2:51 pm
1. check INFORMATION_SCHEMA.TABLE_CONSTRAINTS for those having FK constraints.....
2. then, check sysobjects for those w/o FK.....
Hint: using LEFT JOIN.
*********************************
EDIT:
Actually, you can just query sysobjects.:D
July 10, 2008 at 11:32 am
Nnada Kumar (6/5/2006)
July 1, 2008 at 1:56 pm
By default, every one (in public role) can see it. But, not every one can query against it.
And, those INFORMATION_SCHEMAs are on BOL. So, what's your purpose of denying that...
June 27, 2008 at 11:19 am
I happened to have one: :w00t:
declare @temp table
(
Createdate varchar(10),
IDColumn smallint,
CustNumber int
)
-- INSERT DATA for testing
insert into @temp values('12/1/2005', 2, 100)
insert into @temp values('5/1/2007', 1, 100)
insert...
June 25, 2008 at 2:03 pm
The users can SEE the INFORMATION_SCHEMA, but, they get DENIED when they query INFORMATION_SCHEMA if you deny SELECT on those SCHEMA.
June 25, 2008 at 11:56 am
Is there any difference in 2005 for sp_readerrorlog and xp_readerrorlog? (because I got the same result)
June 25, 2008 at 11:26 am
Service Pack DOES matter for SQL Server's health.
You'd better test the SP before you move on.
June 25, 2008 at 11:22 am
Besides the INDEX part,
(convert(VARCHAR(6), CombinedTT.StartTime, 112)= '{?Period}')
---- this one takes longer in WHERE clause.....
Better move the CONVERT into your SELECT...UNION ALL....part
June 24, 2008 at 12:06 pm
I use profiler or system sprocs to trace those kinds of activities.:hehe:
June 23, 2008 at 3:04 pm
Viewing 15 posts - 136 through 150 (of 190 total)