Not to worry happy to help

The best solution would be to give the account full control on the disks as this would then follow the best practice of lowest access...

i'm not all that clued up on XML as most of the XML work is done in the apps, not in the DB, so if you could provide a solution...

just done a quick google and it brought back a few results, but i think the social section of MS is offline as I cant connect,

dont know if you want...

=iif(Fields!isYO.Value=0,"not YO","YO")

SSIS/SSRS/SSAS is a cobble together of different development teams using VB.Net and C# (from what I was told in various Microsoft instructor lead courses), so you need to change...

hit the nail on the head, I looked at it and thought, that syntax is right, then thought, doh its not T-SQL its SSRS so gotta use " (speach marks)...

Would want to do something like this

CREATE PROC ............ (@Office CHAR(5),.................)

AS

IF @Office NOT IN ('12','13','14')

BEGIN

SELECT

'Office is not 12,13 or 14'

END

ELSE

BEGIN

SELECT

'Office is either...

this should do the trick

create table #temp (a int, b int, c int, d int, e int, f int)

insert #temp values (21, 45, 11, 16, 567, 1256)

select

convert(varchar,a)+

','+

convert(varchar,b)+

','+

convert(varchar,c)+

','+

convert(varchar,d)+

','+

convert(varchar,e)+

','+

convert(varchar,f)

from

#temp

right, just tried this on our prod server as its externally hosted and we can only use SQL logins as its not tied to the domain

created new DB AntDetachTest

sp_detach_db AntDetachTest

RDP'd...

I have never tried it using a SQL login, to see what actually happens with the file locking, but thats always been the case with Windows logins.

Saying that I will...

this is an hilarious link

http://gizmodo.com/5498412/sql-injection-license-plate-hopes-to-foil-euro-traffic-cameras

someone trying to foil a euro country's speed camera sytem using SQL injection

you cant, you just need to make sure that you have a very tight server, logins are check for any permissions they shouldnt have, parameters being passed in to procedures...

most attacks come from the internal network, so saying your end users go no where near the table is great, but what about your internal users. you might have...

that links with what the article was saying

the db was detached by user1, SQL then gives only user1 access to the files of the database anyone else including administrators are...

i would uncheck everything on the settings tab to be on the safe side.

other than that, I cant think of anything else which would send a break to the command...

the task isnt set to stop after X amount of time is it, usually the default is 72 hours