This should do it :

SELECT CONVERT(VARCHAR(8),GetDate(),108)

if you don't want the seconds then you can add left(..., 5) to trim that too.

This solution however means that the user could not...

I've only heard of problems like this in replication, but then again it's real easy to fix with a single commande. So I would just go ahead and push...

Hehe... that too .

One might also consider buying more ram and cpu power to handle such a query without a where clause to avoid...

A job can be scheduled to run whenever you want just like a sceduled task in Windows... You'll have 1 more step to do and you're sure that nothing will...

I can imagine... but I'd rather not have any nightmares tonight .

I would stick with AJ's point that you MUST NOT ALTER SYSTEM TABLES. I cannot stress this point enough. However what you could do that would have almost...

Ya you just don't need a case in this situation. You can do it with a case but that's just wasted cpu cycles if you want my opinion.

One way to do it would be this :

Select right('0' + cast(ST.GR as varchar(2)), 2)

PS a smallint can go up to 32 768 and your column seems to hold...

You can use the function COUNT_BIG() instead which returns a bigint.

It uses the same parameters as the count() function.

""And indeed, a trigger fires, even if the desired table statement did not affect any rows ! ""

Indeed that's why you should always do an inner join on the deleted...

You can lookup the "ISNULL" function in the books online

SELECT

Account_Code,

SUM( Amount) AS GROSS,

SUM(case WHEN (Transaction_Date <= DATEADD(DAY, -90, '20041231'))then (Amount) else 0 end) as "BAL_OVER_90",

ISNULL((select AmountSC ...

Hehe.. I have to write that down somewhere

Have you tried this?

CREATE PROCEDURE test

@m1 varchar(10)

as

declare @sql varchar(100)

select @sql = 'SET ANSI_NULLS ON GO SET ANSI_WARNING ON GO select LastName from ' + @m1 + '.Northwind.dbo.employees'

print @sql

exec...

SELECT TOP 100 PERCENT dbo.sysobjects.name, dbo.sysobjects.xtype

FROM dbo.sysobjects INNER JOIN

...

I hear one thing here.

It seens that the developers are working on their own little system with no code centralisation. That could be a problem, or the solution. ...