Thew fact of choosing keys does not depend only on the uniqueness of the column values (or their combination)... you should consider the essence of your entities and relations to...

select A.* from table A

inner join

(

select distinct

group,

(select top 1 subgroup from table t where table.group=t.group order by subgroup) as subgroup

from table as A

) B

on A.group=B.group and A.subgroup=B.subgroup

You should try to insert a record using a query directly in the management studio:

insert sales (code,amount) values ('A001',1000)

and see what happens....

DBCC CHECKTABLE ('TableName') will check your specific table... however if DBCC CHECKDB is not returning errors then the table seems to be OK... check your datasource params, because it looks...

Could you post the error raised when trying to insert data??

If the recovery mode is set to full you have to make transaction log backups regularly (each 5 or 10 minutes) . The period depends on the workload.

Transaction log...

SELECT tname, oid, [tot_sh_unit], [wgt_uom], [total_qty]

FROM

(SELECT field_id,tname, oid, data_value

FROM #test) p

PIVOT

(

SUM (data_value)

FOR field_id IN

( [tot_sh_unit], [wgt_uom], [total_qty])

) AS pvt

I just added an identity column to both auxiliary tables and then full joined then just to ensure that both inserts will start in the first row... try it and...

I did not understand the original question.... here goes another solution... hope this helps

select distinct id= identity (int,1,1), age into #c from #tempa

select distinct id= identity (int,1,1), hobbycode...

insert TableB select select distinct null,age,null, hobbycode from TableA

Did you grant the access permission to the database for the that login??

The advantage of the active/active configuration is that you can save on hardware resources (provided that each of the servers in the cluster can handle the workload in the event...

In this case... the only cause I can see is that you have a very long active transaction running...

Do you have configured database mirroring or replication on this database???

It's not very clear what you are asking, but in fact

SELECT CONVERT(VARCHAR(20),GETDATE(),109)

really works and returns the value in the expected format: "May 12 2009 10:07:07"