I dont know if this is what you have in mind but You could use dateadd function to do that.

Create table #tbDate (id int identity, dt datetime)

declare @effectiveDate datetime

set @effectivedate...

Do not update any System tables. What you can do is drop the user and the login and recreate them again and add it to the Role that is there.

We have a profiler trace running 24/7. But we only store information of SP's that take more than 250 Millisec. We do not see any perfomance issue on our DB...

Thanks Adam. I still am not good at answering questions yet I guess. I am not good at explaining..:-)

You can always feel free to ask questions here with your problem and you will get atleast 2 to 3 different ways to solve it... There are lots of real...

When you created the user, did you create it with the their SID?

If not try recreating the logins with the SID. Or drop the user from the DB and the...

Like someone said above, You are doing a coinditional search...

You could try using DateAdd and give a between condition. Dateadd(dd,30,ColumnName) and Dateadd(dd,-30,columnName)

You can add an index on multipole columns. Username, BusinessObjectTypeFullName and Timestamp.

Also try to rewrite the where clause with CASE Statement. It will look more clean.

Where USERNAME = CASE when...

Indexing would defiently help you query speed since you are not querying based on the primary Key.

Be carefull about adding too many indexes since indexes can slow down DML...

Check on the Services under what account The SQL Server is being Run. If it is a domain account try with it. Also try to alter the DB and let...

What user did you use to get access to the DB and see user tables? Is Windows Authentication blocked on the DB? If not, try logging on to the DB...

Tagging along with the two of them have already stated, you could also use PLAN Hints

OPTION (OPTIMIZE FOR (@parameter = ))

I dont know if this will help but, Cant you use replace? Something like this?

declare @t char(20)

set @t = 'testing, for comma'

Select replace(@t,',','","')

SQL 2005 does not support JOINS that uses *=. If you still want it to work, you will have to put SQL in either 7 or 8 compatability Mode. But...