SQL Server 2019 CT 2.2 and External Tables

%3CLINGO-SUB%20id%3D%22lingo-sub-331942%22%20slang%3D%22en-US%22%3ESQL%20Server%202019%20CT%202.2%20and%20External%20Tables%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331942%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20set%20up%20two%20instances%20of%20SQL%20Server%202019%20CTP%202.2%20--%20I%20have%20installed%20Polybase%20in%20standalone%20mode%20on%20a%20local%20instance%20and%20activated%20it%20(I%20can%20see%20it%20running%20as%20part%20of%20SQL%20Services).%26nbsp%3B%20Additionally%20--%20I%20can%20use%20SQL%20Server%20Management%20Studio%20on%20the%20instance%20and%20connect%20to%20both%20the%20local%20instance%20and%20the%20remote%20instance.%26nbsp%3B%20Now%20I%20want%20to%20create%20an%20External%20Table%20instance%20in%20the%20local%20instance%20with%20the%20table%20residing%20in%20the%20remote%20instance.%26nbsp%3B%20Using%20Azure%20Data%20Studio%20(with%20the%202019%20Extensions%20activated)%20--%20I%20attempt%20to%20create%20the%20External%20Table%20--%20when%20I%20indicate%20the%20server%20and%20database%20and%20credential%20information%20for%20the%20remote%20server%20-%20I%20get%20the%20error%20%22%3CA%20href%3D%22https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3DExternal%2Btable%2BTCP%2BProvider%3A%2BNo%2Bconnection%2Bcould%2Bbe%2Bmade%2Bbecause%2Bthe%2Btarget%2Bmachine%2Bactively%2Brefused%2Bit%26amp%3Bspell%3D1%26amp%3Bsa%3DX%26amp%3Bved%3D0ahUKEwj98ZDB66fgAhWtiOAKHX5vAgIQkeECCCkoAA%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETCP%20Provider%3A%20No%20connection%20could%20be%20made%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E%3CI%3Ebecause%3C%2FI%3E%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ethe%20target%20machine%20actively%20refused%20it%3C%2FA%3E%22%20I%20have%20attached%20a%20screen%20shot.%20--%20I%20can%20ping%20the%20instance%20--%20I%20can%20telnet%20to%20it%20--%20I%20can%20connect%20to%20the%20remote%20instance%20via%20Azure%20Data%20Studio%20and%20SSMS%20.......%20BTW%20documentation%20in%20this%20area%20is%20pretty%20ugly%20--%20and%20inconsistent.%26nbsp%3B%20In%20any%20case%20--%20any%20ideas%3F%26nbsp%3B%20I%20do%20NOT%20have%20Polybase%20installed%20on%20the%20remote%20instance.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-427353%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20CT%202.2%20and%20External%20Tables%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-427353%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F279529%22%20target%3D%22_blank%22%3E%40architectscott1%3C%2FA%3E%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECoul%20you%20please%20explain%20me%20how%20you%20fixed%20the%20TCP%20error.I%20am%20having%20the%20same%20issue.Not%20able%20to%20create%20external%20table%20for%20sql%20server%20or%20Oracle.Your%20help%20will%20be%20much%20apprecuated.Thanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356367%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20CT%202.2%20and%20External%20Tables%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356367%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20playing%20about%20with%20it%20now%20Polybase%20doesn't%20seem%20to%20cope%20well%20with%20not%20having%20the%20same%20number%20of%20fields%20in%20each%20document%20within%20a%20collection.%20(Which%20is%20kinda%20the%20point%20of%20a%20NoSQL%20database)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECommenting%20here%20as%20would%20like%20to%20know%20if%20this%20is%20something%20that%20will%20be%20resolved%20before%20RTM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331999%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20CT%202.2%20and%20External%20Tables%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331999%22%20slang%3D%22en-US%22%3E%3CP%3EOK%20--%20so%20now%20I%20made%20it%20a%20bit%20further%20--%20the%20documentation%20is%20awful!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20now%20getting%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E105075%3BThe%20user%20specified%20schema%20column%20count%20is%2078%2C%20which%20varies%20from%20the%20external%20table%20schema%20column%20count%20of%2081.%20The%20detected%20external%20table%20schema%20is%3A%20(%5Bname%5D%20NVARCHAR(128)%20COLLATE%20SQL_Latin1_General_CP1_CI_AS%2C%20%5Bdatabase_id%5D%20INT%20NOT%20NULL%2C%20%5Bsource_database_id%5D%20INT%2C%20%5Bowner_sid%5D%20VARBINARY(85)%2C%20%5Bcreate_date%5D%20DATETIME2(3)%20NOT%20NULL%2C%20%5Bcompatibility_level%5D%20TINYINT%20NOT%20NULL%2C%20%5Bcollation_name%5D%20NVARCHAR(128)%20COLLATE%20SQL_Latin1_General_CP1_CI_AS%2C%20%5Buser_access%5D%20TINYINT%2C%20%5Buser_access_desc%5D%20NVARCHAR(60)%20COLLATE%20SQL_Latin1_General_CP1_CI_AS%2C%20%5Bis_read_only%5D%20BIT%2C%20%5Bis_auto_close_on%5D%20BIT%20NOT%20NULL%2C%20%5Bis_auto_shrink_on%5D%20BIT%2C%20%5Bstate%5D%20TINYINT%2C%20%5Bstate_desc%5D%20NVARCHAR(60)%20COLLATE%20SQL_Latin1_General_CP1_CI_AS%2C%20%5Bis_in_standby%5D%20BIT%2C%20%5Bis_cleanly_shutdown%5D%20BIT%2C%20%5Bis_supplemental_logging_enabled%5D%20BIT%2C%20%5Bsnapshot_isolation_state%5D%20TINYINT%2C%20%5Bsnapshot_isolation_state_desc%5D%20NVARCHAR(60)%20COLLATE%20SQL_Latin1_General_CP1_CI_AS%2C%20%5Bis_read_committed_snapshot_on%5D%20BIT%2C%20%5Brecovery_model%5D%20TINYINT%2C%20%5Brecovery_model_desc%5D%20NVARCHAR(60)%20COLLATE%20SQL_Latin1_General_CP1_CI_AS%2C%20%5Bpage_verify_option%5D%20TINYINT%2C%20%5Bpage_verify_option_desc%5D%20NVARCHAR(60)%20COLLATE%20SQL_Latin1_General_CP1_CI_AS%2C%20%5Bis_auto_create_stats_on%5D%20BIT%2C%20%5Bis_auto_create_stats_incremental_on%5D%20BIT%2C%20%5Bis_auto_update_stats_on%5D%20BIT%2C%20%5Bis_auto_update_stats_async_on%5D%20BIT%2C%20%5Bis_ansi_null_default_on%5D%20BIT%2C%20%5Bis_ansi_nulls_on%5D%20BIT%2C%20%5Bis_ansi_padding_on%5D%20BIT%2C%20%5Bis_ansi_warnings_on%5D%20BIT%2C%20%5Bis_arithabort_on%5D%20BIT%2C%20%5Bis_concat_null_yields_null_on%5D%20BIT%2C%20%5Bis_numeric_roundabort_on%5D%20BIT%2C%20%5Bis_quoted_identifier_on%5D%20BIT%2C%20%5Bis_recursive_triggers_on%5D%20BIT%2C%20%5Bis_cursor_close_on_commit_on%5D%20BIT%2C%20%5Bis_local_cursor_default%5D%20BIT%2C%20%5Bis_fulltext_enabled%5D%20BIT%2C%20%5Bis_trustworthy_on%5D%20BIT%2C%20%5Bis_db_chaining_on%5D%20BIT%2C%20%5Bis_parameterization_forced%5D%20BIT%2C%20%5Bis_master_key_encrypted_by_server%5D%20BIT%20NOT%20NULL%2C%20%5Bis_query_store_on%5D%20BIT%2C%20%5Bis_published%5D%20BIT%20NOT%20NULL%2C%20%5Bis_subscribed%5D%20BIT%20NOT%20NULL%2C%20%5Bis_merge_published%5D%20BIT%20NOT%20NULL%2C%20%5Bis_distributor%5D%20BIT%20NOT%20NULL%2C%20%5Bis_sync_with_backup%5D%20BIT%20NOT%20NULL%2C%20%5Bservice_broker_guid%5D%20UNIQUEIDENTIFIER%20NOT%20NULL%2C%20%5Bis_broker_enabled%5D%20BIT%20NOT%20NUL...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20do%20you%20guys%20make%20this%20such%20a%20painful%20process%3F%3F%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Escott%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-445985%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20CT%202.2%20and%20External%20Tables%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-445985%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318487%22%20target%3D%22_blank%22%3E%40Mayil_V_Chandran%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20syntax%20that%20was%20causing%20me%20issues%20was%20in%20the%20CREATE%20EXTERNAL%20TABLE%20--%26nbsp%3BLOCATION%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3ELOCATION%20%3D%20'sqlserver%3A%2F%2Fss2019azure.database.windows.net'%2C%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20a%20more%20complete%20script%20--%20execute%20the%20following%20on%20your%20SS2019%20instance%20(based%20on%20the%20table%20you%20have%20in%20Azure%20SQL)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%20you%20need%20to%20create%20MASTER%20CREDENTIAL%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E--(CREATE%20MASTER%20CREDENTIAL%20not%20shown)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ECREATE%20DATABASE%20SCOPED%20CREDENTIAL%20acmeCred%20WITH%20IDENTITY%20%3D%20'remoteAdmin'%2C%20SECRET%20%3D%20'pty1234!'%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Ego%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ECREATE%20EXTERNAL%20DATA%20SOURCE%20AzureDB%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BWITH%20(%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BLOCATION%20%3D%20'sqlserver%3A%2F%2Fss2019azure.database.windows.net'%2C%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BCREDENTIAL%20%3D%20acmeCred%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B)%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Ego%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ECREATE%20EXTERNAL%20TABLE%20%5Bdbo%5D.%5BtblAcmeDataAzure%5D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E(%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BID%20varchar(10)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BFName%20varchar(40)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BLName%20varchar(40)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BAddress%20varchar(40)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BCity%20varchar(40)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BRegion%20varchar(40)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BCountry%20varchar(40)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BPCode%20varchar(15)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BPhone%20varchar(15)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BEmail%20varchar(64)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BCCN%20varchar(20)%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BNIN%20varchar(15)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWITH%20(%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3BLOCATION%3D'dbAcmeAzure.dbo.tblAcmeDataAzure'%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3BDATA_SOURCE%3DAzureDB%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E)%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Ego%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I have set up two instances of SQL Server 2019 CTP 2.2 -- I have installed Polybase in standalone mode on a local instance and activated it (I can see it running as part of SQL Services).  Additionally -- I can use SQL Server Management Studio on the instance and connect to both the local instance and the remote instance.  Now I want to create an External Table instance in the local instance with the table residing in the remote instance.  Using Azure Data Studio (with the 2019 Extensions activated) -- I attempt to create the External Table -- when I indicate the server and database and credential information for the remote server - I get the error "TCP Provider: No connection could be made because the target machine actively refused it" I have attached a screen shot. -- I can ping the instance -- I can telnet to it -- I can connect to the remote instance via Azure Data Studio and SSMS ....... BTW documentation in this area is pretty ugly -- and inconsistent.  In any case -- any ideas?  I do NOT have Polybase installed on the remote instance. 

4 Replies
Highlighted

OK -- so now I made it a bit further -- the documentation is awful!!

 

I am now getting the following error:

 

105075;The user specified schema column count is 78, which varies from the external table schema column count of 81. The detected external table schema is: ([name] NVARCHAR(128) COLLATE SQL_Latin1_General_CP1_CI_AS, [database_id] INT NOT NULL, [source_database_id] INT, [owner_sid] VARBINARY(85), [create_date] DATETIME2(3) NOT NULL, [compatibility_level] TINYINT NOT NULL, [collation_name] NVARCHAR(128) COLLATE SQL_Latin1_General_CP1_CI_AS, [user_access] TINYINT, [user_access_desc] NVARCHAR(60) COLLATE SQL_Latin1_General_CP1_CI_AS, [is_read_only] BIT, [is_auto_close_on] BIT NOT NULL, [is_auto_shrink_on] BIT, [state] TINYINT, [state_desc] NVARCHAR(60) COLLATE SQL_Latin1_General_CP1_CI_AS, [is_in_standby] BIT, [is_cleanly_shutdown] BIT, [is_supplemental_logging_enabled] BIT, [snapshot_isolation_state] TINYINT, [snapshot_isolation_state_desc] NVARCHAR(60) COLLATE SQL_Latin1_General_CP1_CI_AS, [is_read_committed_snapshot_on] BIT, [recovery_model] TINYINT, [recovery_model_desc] NVARCHAR(60) COLLATE SQL_Latin1_General_CP1_CI_AS, [page_verify_option] TINYINT, [page_verify_option_desc] NVARCHAR(60) COLLATE SQL_Latin1_General_CP1_CI_AS, [is_auto_create_stats_on] BIT, [is_auto_create_stats_incremental_on] BIT, [is_auto_update_stats_on] BIT, [is_auto_update_stats_async_on] BIT, [is_ansi_null_default_on] BIT, [is_ansi_nulls_on] BIT, [is_ansi_padding_on] BIT, [is_ansi_warnings_on] BIT, [is_arithabort_on] BIT, [is_concat_null_yields_null_on] BIT, [is_numeric_roundabort_on] BIT, [is_quoted_identifier_on] BIT, [is_recursive_triggers_on] BIT, [is_cursor_close_on_commit_on] BIT, [is_local_cursor_default] BIT, [is_fulltext_enabled] BIT, [is_trustworthy_on] BIT, [is_db_chaining_on] BIT, [is_parameterization_forced] BIT, [is_master_key_encrypted_by_server] BIT NOT NULL, [is_query_store_on] BIT, [is_published] BIT NOT NULL, [is_subscribed] BIT NOT NULL, [is_merge_published] BIT NOT NULL, [is_distributor] BIT NOT NULL, [is_sync_with_backup] BIT NOT NULL, [service_broker_guid] UNIQUEIDENTIFIER NOT NULL, [is_broker_enabled] BIT NOT NUL...

 

Why do you guys make this such a painful process?????

 

scott

Highlighted

Just playing about with it now Polybase doesn't seem to cope well with not having the same number of fields in each document within a collection. (Which is kinda the point of a NoSQL database)

 

Commenting here as would like to know if this is something that will be resolved before RTM.

 

Highlighted

@architectscott1   

 

Coul you please explain me how you fixed the TCP error.I am having the same issue.Not able to create external table for sql server or Oracle.Your help will be much apprecuated.Thanks.

 

Highlighted

@Mayil_V_Chandran 

 

The syntax that was causing me issues was in the CREATE EXTERNAL TABLE -- LOCATION:

 

        LOCATION = 'sqlserver://ss2019azure.database.windows.net', 

 

Here is a more complete script -- execute the following on your SS2019 instance (based on the table you have in Azure SQL)

 

First you need to create MASTER CREDENTIAL

 

 

 

--(CREATE MASTER CREDENTIAL not shown)

CREATE DATABASE SCOPED CREDENTIAL acmeCred WITH IDENTITY = 'remoteAdmin', SECRET = 'pty1234!';

go

CREATE EXTERNAL DATA SOURCE AzureDB

    WITH (  

        LOCATION = 'sqlserver://ss2019azure.database.windows.net', 

        CREDENTIAL = acmeCred

                                    );

go

CREATE EXTERNAL TABLE [dbo].[tblAcmeDataAzure]

(

    ID varchar(10),

    FName varchar(40),

    LName varchar(40),

    Address varchar(40),

    City varchar(40),

    Region varchar(40),

    Country varchar(40),

    PCode varchar(15),

    Phone varchar(15),

    Email varchar(64),

    CCN varchar(20),

    NIN varchar(15)

)

WITH (

 LOCATION='dbAcmeAzure.dbo.tblAcmeDataAzure',

 DATA_SOURCE=AzureDB

);

go