select t.* from #temp t

inner join (select ID,DEP from #temp

group by ID,DEP

having max()=0) t1 on t1.id=t.id and t1.dep=t.dep

Try the following for the values giving trouble and post the results:

select charindex('AB20',C), charindex('AB',C),charindex('20',C),C from T

It should indicate whether there's another character between the 'AB' and the '20'

It's difficult to be sure what you're after without posting the create table statements and giving some sample data (I'm sure someone will be along to post a link to...

It's because you're relying on an implicit conversion from a string to a decimal data type which SQL server will do to 2 decimal places by default, so you're losing...

Well the point is that SQL Server is the back-end and nicely formatting things is the job of the front-end. It's just not what SQL was designed for.

It's also beneficial...

Is the target IO duration the same in both cases?

With the default settings, that metric means the number of times a response went over 100ms and it slowed down...

Are you using the Import/Export Wizard to transfer from one db to another?

If so, the answer is to go to Edit Mappings... then Edit SQL... and change the create table...

In Simple recovery mode, the log space is recovered as soon as the transaction ends - this is a very lightweight process that only puts a pointer that the log...

Hi Ville,

No, you don't necessarily need the begin tran, commit tran. Take the shrinkfile out though, it's not required.

By definition, if the file can be shrunk, then the disk...

You shouldn't need to do a dbcc shrinkfile if you're in simple recovery mode - once each transaction commits, the log space will be available to be re-used for the...

That looks like the outer exception, what's the inner exception?

What's the inner exception when you use the code I posted? Definitely works in my environment

I'm assuming the table already exists? If so, you're doing this the wrong way as you're trying to create the table which will fail as the table already exists.

try:

...

If you're using sql 2005 (as I assume you are from where this is posted):

select schema_name(schema_id), name from sys.objects where type='U'

or

select schema_name(schema_id),name from sys.tables

I have to say, I haven't started rolling out SP3 yet, but unless it's changed significantly from SP2, rolling back aint pretty.

Effectively, the MS advice is uninstall/re-install SQL Server including...