schwizzla (5/5/2009)

---

I have a table with 6120 records

2275 records = Unique LicenseNumber

1941 records = duplicate x2

11 records = x3

5 records = x4

ProductLicense_Idn (PK, int, not null)

LicenseNumber (Varchar(255), not...

INSERT INTO...SELECT into a table with a clustered index can still be minimally logged, unless it contained rows before the INSERT, in which case it will be fully logged regardless...

Hang on. Are you doing SELECT ... INTO (in which case the destination table doesn't exist prior to the execution) or INSERT INTO ... SELECT (where the destination table does)

Where's...

Thank you, I already learned a lot today....

Thanks Paul. I will try to make a full backup but currently I'm waiting for a rollback (transaction log could not grow..:w00t:)

Is there a History where I can see, what...

no, there is no transaction. Meanwhile I learned to update the MinLSN in the transaction log using a checkpoint. That helped.

But there is still one Statement which causes a large...

I build a new Compare Tool, and there's a free version.

Feel free to try: DB Scripter

Tobias

hmm..now I'm a little disappointed from sqlserver.

Thanks for help.

Hi,

i tried to build the table with a nonclustered primary key, but it still doesn't work.

create table partitiontest(

test_id int identity(1,1) not null

, period datetime not null

...

Ok, i found out the solution:

alter TRIGGER [trig_deny_ddl]

ON database

for DDL_TABLE_EVENTS, DDL_VIEW_EVENTS, DDL_FUNCTION_EVENTS, DDL_PROCEDURE_EVENTS

AS

declare @command nvarchar(max)

SELECT @command = EVENTDATA().value('(/EVENT_INSTANCE/TSQLCommand/CommandText)[1]','nvarchar(max)')

if @command not like...

Hi,

I'm logging OnPreExecute now. That works fine.

Thank you,

Tobias

Hi,

partitioning and staging not necissarily goes hand in hand.

Please explain your requirements in more detail.

Staging is a way of loading data from sources and transform it.

The key of partitioning is...

Thank you. For my situation, disabling the foreign key worked fine

Hi,

that query was surely not optimized. I added one additional, combined index and suddenly the query uses a slightly different plan and is fast.

I just wonder, if (and i will)...

Thank you for that information. Actually a progress bar seems not to be the proper method. Perhaps we can use a animated gif..