It depends on how long the transaction from your insert will take.

If it is short, I think you'll not notice the blocking when a user that is in your list...

- a job can only run once at a time !

- if a job runs, you cannot start it again until in has ended.

- So what you see is normal...

you can write the job-step-output to a txt-file (edit jobstep-properties \ advanced). Maybe that already gives you the info you need.

- You should run sqlserver using an "own" sqlserver-domain account that serves only that sqlserver (or a group of sqlservers if you want to)

- Be carefull when changing the serviceaccount...

I guess not, because the .commandtimeout is available with the sqlclient.sqlcommand.

I would be estonished if that wasn't integrated in DAAB.

They've found it for the connection, so they 'll be...

With ado.net there is a sqlcommand.CommandTimeout that you can set.

also check out

http://msdn2.microsoft.com/en-us/library/aa479373.aspx#spoil_topic4

http://msdn2.microsoft.com/en-us/library/aa479373.aspx#spoil_topic5

Indeed, it's the dba's daily job to do miracles and salvations

Dev-teams are first of all afraid to admit flaws, and then to...

Good article.

Most articles only handle "local" SSB. That's the easy part !

There are many pitfalls when going remote.

I'll poste al litle script containing the dmv's,.. for SSB-problemsolving.

The way Santosh wrote it , you'd get two resultsets.

If you want to join both queries to get one resultset , just use :

SelectStatement = String.Format("

SELECT ....

FROM shows AS...

if you use a command-object, it has its own timeout (default at 30seconds)

can you also post the query ?

- start sql-profiler to capture a sample load and examine it for table and or index scans.

- do you have db-maintenance-jobs in place ? to reduce fragmentation

- for the data-part the is no difference for 32 or 64-bit OS / SQLServer

- however if you are using the CLR, I guess it would be nice to avoid...

- I wouldn't advise a trigger for this purpose ! (start job) because if the start job fails, your transaction fails !

- I woudn't advise a trigger for this purpose...

this could be your test-script ....

print '00 Creating dbo.test';

go

create table dbo.Test (col1 int not null )

go

print '01 inserting rows into dbo.test';

go

insert into test values(1);

go

print '02 Selecting from unqualified table test';

go

select...