Where is Log Reader Agent????

LutzM (5/12/2011)

---

Without knowing what the functions used in the query actually look like it's close to impossible to help you any further...

All I can say is: maybe the good old...

What was the command you used to update stats?

I would recommend to use Update statistics.

What the use of a replication for a read only database?

Appreciate if someone can give lights on the same.

Thanks for your reply.

That makes me to ask one more question:

If I have configured two publishers, single Log reader Agent will place two different log entries in distriutor database or...

Would the beloe help you at an extend?

Declare @StartDate Date, @EndDate DateSet @StartDate = Getdate()-20Set @EndDate = Getdate() SELECT (DATEDIFF(dd, @StartDate, @EndDate) + 1) -(DATEDIFF(wk, @StartDate, @EndDate)...

Check this would help you or not!!!

Its always good at looking thw wait types occured in your production

use master

go

Select A.[SQL text],A.Session_id,A.wait_duration_ms,a.wait_type,a.blocking_session_id,B.Status,B.statement_executing,B.DatabaseName,B.CPU_time,B.total_elapsed_time,b.reads,b.writes,b.logical_reads From (

SELECT st.text AS [SQL Text],

w.session_id,

w.wait_duration_ms,

w.wait_type, w.resource_address,

w.blocking_session_id,...

My bad, i used the same window for testing...As soon as I restarted the SSMS, started working...

Vijy, You have to try the things to understand, we have some limitations always as not dealing with the data...

Anyway, just look at the below and let us know

create table...

Is the below you are looking for?

create Table T1(Col1 int ,Col2 int)

Insert Into T1 Select 1,2

Insert Into T1 Select 2,2

Insert Into T1 Select 2,1

Select Col1,

(Case When (Select COUNT(1) From T1...

Take the count first and then return null value if it does not have any value else return the resultset of the query

Okei, say, I want to restrict a login to connect less than 5 sessions from SSMS.

I guess, it s possible through LOGON trigger, using rollback checking by the LOGIN_NAME. Am...

Do you really mean 'cannot'...

As Gail said, SQL optimizer had choosen HASH join is the best option here as long as you have plenty of data in both tables for SORT is costly operation.