Viewing 15 posts - 2,191 through 2,205 (of 5,103 total)
As I see it the query is good you just need to change the *in* as you needed.
ex:
SELECT [Dept],
[Job Code],
SUM(CASE WHEN [Charge Code] IN ('NPO','REG E','REG N','PRO')...
October 3, 2006 at 11:58 am
Curently I am fighting a Bug with M$ that only happens under very special conditions and makes the log grow exponentially ![]()
For your conditions....
October 3, 2006 at 11:35 am
Large Transactions in the Log produce these effects.
October 3, 2006 at 11:25 am
the recovery model will only impose a restriction on your point-in-time restore. You can use *any* of the three.
When combining technologies though, Like log shipping or DB Mirroing, Log...
October 3, 2006 at 11:23 am
When you get into a rollback situation, there is nothing to do but wait, unless the process that is rolling back is being blocked.
Stopping SQL Server is *NOT* going to...
September 28, 2006 at 11:31 am
The funny part is the error message. In sql 2000 it says "invalid connection settings" when the conditions that you described happens. It is good to know that I may...
September 28, 2006 at 8:04 am
GUIDs have their place but High transaction systems is *not* an advantage for them to be considered better than ints. You can controll the *hot* spot issue by setting your...
September 28, 2006 at 7:48 am
First of all you need to specify the schema ex: "dbo".
Second the correct syntax should include "exec"
Third the Openquery rowset must be aliased in my example : dt
Fourth If...
September 28, 2006 at 7:38 am
Log shipping will cover *all* database objects.
Logins though are Server wide, you will need to devise a separate strategy to keep them in synch.
September 28, 2006 at 7:28 am
I am also against this answer.
The correct one is the FIRST. As pointed above there should not be reliance on blogs "before" BOL
September 27, 2006 at 9:47 am
This is the way to get those without hardcoding names:
select OBJECT_NAME(i.id) as tab , i.name as idx
from sysindexes i
where i.indid between 1 and 249
...
September 14, 2006 at 12:07 pm
But it is pretty handy and it works on 2005 too ![]()
By the way the syntax can be rewritten as :
exec sp_MSforeachdb '?.dbo.sp_helpfile'...
September 14, 2006 at 11:33 am
As you probably already know you can't have varchar columns of more that 8000 therefore in SQL Server 2000 your only option is "text" datatype. To audit those from...
September 14, 2006 at 11:30 am
Are you using "UPDATE" to archive ???
September 14, 2006 at 11:26 am
Viewing 15 posts - 2,191 through 2,205 (of 5,103 total)