i had the same issue too, sometime access locks table if user were running a big query on it. to avoid be blocked, i use a stored procedure to check if table is...

or, you can have a table to collect user's "run" request, then set up a job running to start other jobs that user has requested by lookup request status.

look up here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dtsprog/dtspscrprop_58ft.asp

DestinationRowsComplete Property

DTSTransformPhaseInfo.DestinationRowsComplet

hope it will help.

all job related codes must have a sa level login to execute.

but, i suggest you should not give sa's login away for security.

you need call xp_cmdshell in QA to run the bcp.

declare @strCMD varchar(100)

select @strCMD = 'bcp db..table out ..... '

exec master..xp_cmdshell @strCMD

check out http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=44073

, and nr's posts are good resource.

i'm copying one link from nr's post here just in case,

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp

i never had so little free space, but i'm thinking if you set database to simple model, will it work?

Hi Sean,

Sorry, I did not directly involve into the firmware upgrading process. I reported the issues to our system administrator; he found some useful...

We had same error before. After upgrading the firmware, it fixed the problem.

ftp://ftp.compaq.com/pub/products/storageworks/techdoc/msa1000/MSA10004.32_ReleaseNotes.pdf

it's not a matter if you can't see your view, as long as your view existing and you can query it.

if it's a matter,...

try this way:

execute [remoteservername].[databasename].[dbo].[spStoredProc]

query your view:

select *

from [servername].[databasename].[dbo].[viewname]

your view does not appear, because it's not in the default database for linked server login.

schduling a job to run the ftp later.

The BOL states "SQL Server issues a warning and ignores the duplicate row."

Unfortunately, the sql server issues an error with level 16.

I saw you have three same posts there.

quote:

---

Is there any article on the physical space needed to shrink a database