Test it - easy enough for you to create a table with normal compression and...

you didn't tell us what you mean by "the data returns instantaneously" - if by this you mean it returns to your SSMS grid then do not use this as...

can you give the output of these please.

select containment_desc
from sys.databases 
where name = db_name()

select  type_desc
, is_disabled
, default_database_name

from sys.server_principals
where name =  'xxxx' -- replace with login...

try the following code - without changes other than the login name and give us the output

if (original_login() <> suser_name())
begin
    print 'revert'
  ...

potentially something similar to this

select customerid
     , max(case when [Data Entry] = 'entry' then [Data Entry] else null end) as [Data Entry]
 ...

you will most likely need to get your network/windows admins involved - there could be many reasons and none associated with SQL Server itself.

have a look at this google...

go to tools -> options - > Environment -> international settings.

probably set to "same as Microsoft Windows"

but this should not affect your code - unless you are copying/pasting from SSMS...

If you are sysadmin you can't give permissions to yourself - neither do you need it on this case so remove that from your script.

regarding setuser - do not use...

well.. first link I got when I searched was the one that Oracle themselves supply - so I wonder if you did find it on your googling and did you...

did you bother googling? there are a few tools (mostly commercial) including one from Oracle that can either put them on a format you can read or that will...

yup.. you do need to go and learn the basics of T-SQL.

remove all "GO" statements that are after the create procedure.

But as Brian mentioned why this? once created the indexes...

if I understand what you are trying to say it seems that you don't know how to create a stored procedure

so instead of putting a few snippets from your code...

and what is your issue?

what you said does not give us any detail other than what you intend on doing.

Visual Studio is 32 bit - you need to install ACE x32 in order to be able to create new SSIS packages using it.

We just discovered another process that is having a similar issue. It appears to be where the field size in the "source" table (which contains the non-clustered columnstore index)...