it's the shortcut SQL uses for data types; integer divided by integer yields an integer result.

multiply either the numerator or denominator by 1.0 and you'll get your 0.17

your welcome!

it...

i have already done something very similar...this code may help out, or just complicate matters...

it's a huge stack of updates to a temp table, so I could review the old...

you error message is not related to your (max) string, it's related to a specific varchar/char column in the sql statement you built...

if a column has a definition of a...

ahh i see what you are after...i think you'll end up finding that all the DMV's get set to zero whenever the server is stopped and started, though right?

so...

i think the original poster wanted a different database, not necessarily a different server, right?

a simple trigger like:

CREATE TRIGGER TR_MyTrigger On SomeTable

FOR UPDATE

AS

BEGIN

UPDATE MyAlias

SET col1 = INSERTED.col1,

col2=INSERTED.col2

...

FROM INSERTED

INNER...

jabba (6/30/2009)

---

My understanding is that the server side teace will not be retrospective and so will not achieve what I am looking for. I go back to my original question....

not enough information to help you; you can see how long a command took with a trace or by setting SET STATISTICS TIME ON , but not an estimated time,...

your co workers are under informed, I think.

when you move the primary key/clustered index of a table to a new file group, you move it's data as well.

example:

CREATE...

there's a pretty good thread on the issue here, but it may or may not be the same thing you are experiencing:

http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/ef029812-45d0-4544-a00f-bd9e66a6d4bf

it seems the default behavior of SQL 2005 changed,...

well, just as the error message says, the first thing I'd do is check to see if the server allows remote connections:

This issue vs your credentials in your signature don't...

the above trigger example assumes thre would only be ONE row ever updated at any one time...it best practice is to assume more than one row comes from the INSERTED...

yeah i agree; either fix the data, or the one parameter raising the issue. I would not try to change hundreds of other parameters...to many things for the QA team...

@Param1 NUMERIC(2, 0)---this says the definition is 2 digits, none after the decimal....but you are assigning a 5 digit number to it: @Param1 = 92229.0

since the biggist...

he can use a case statement to group them horizontally;

well...three case statements, right?

case

when c1 <= c2 and c1 c1 and c2 <= c3 then c2....