InstantForum.NET v4.1.4SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 12 Mar 2010 09:17:04 GMT20http://www.sqlservercentral.com/Forums/Topic503823-148-1.aspx@Dinesh AsankaI have experimented your setting, and ran my package with "SQL Server Destination" created for a remote server.But my package failed again with the same error.Here is what I did-1). I have added my domain account in :Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Create global objects2). Executed the pkg that used the "SQL Server Destination" component in the "Data Flow Task". The Result :: FailedError Message:[SQL Server Destination [1978]] Error: Unable to prepare the SSIS bulk insert for data insertion. [DTS.Pipeline] Error: component "SQL Server Destination" (1978) failed the pre-execute phase and returned error code 0xC0202071. 3). Replaced "SQL Server Destination" with "OLE DB Destination" and Package succeded.Is there any correction needed, in making my "SQL Server Destination" work as you have explained.[i]Barely 'Alive',[/i][font="Comic Sans MS"][b]Vampire[/b][/font]Thu, 25 Feb 2010 02:31:43 GMTLonely Vampirehttp://www.sqlservercentral.com/Forums/Topic503823-148-1.aspxUsers who execute packages that include the SQL Server destination require the "Create global objects" permission. You can grant this permission to users by using the Local Security Policy tool opened from the Administrative Tools menu. If you receive an error message when executing a package that uses the SQL Server destination, make sure that the account running the package has the "Create global objects" permission.Tue, 16 Feb 2010 23:27:21 GMTDinesh Asankahttp://www.sqlservercentral.com/Forums/Topic503823-148-1.aspx@ James Connor.Thanks for the input. I too have solved the same issue by replacing " SQL Server Destination " with " OLE DB Destination ".This behaviour has been explained well @ [url] http://consultingblogs.emc.com/jamiethomson/archive/2006/08/14/4344.aspx [/url]In 'Dead' Memories,[font="Comic Sans MS"][b]Vampire[/b][/font]Mon, 26 Oct 2009 09:21:34 GMTLonely Vampirehttp://www.sqlservercentral.com/Forums/Topic503823-148-1.aspxYou are very right. Oledb Destination should be used for OLEDB connection.ThanksAvinashWed, 16 Sep 2009 05:53:23 GMTAvinash Barnwalhttp://www.sqlservercentral.com/Forums/Topic503823-148-1.aspxI resolved this issue ..solution for this issue is ..instead of taking the sqlserver destination use oledb destination for oledb connection...regards mallikTue, 16 Dec 2008 01:54:23 GMTmail4mallihttp://www.sqlservercentral.com/Forums/Topic503823-148-1.aspxHi There,The issue I've picked up is that if you accidentally use a SQL Server Destination in your Data Flow Tasks and you have to change your Destination to an OLE DB one, you have to sit and re-map your columns from scratch - Which is an extremely huge pain if you have hundreds of columns to map.What you can try to do is the following:* Right Click on your SQL Server Destination and click on Properties* Change your MaxInsertCommitSize from 0 to X amount of rows.In my mind this sort of defeats the use of the SQL Server Destination because it now would commit rows to your Database every time it hits the X amount of rows you have specified, but at least you wouldn't have to go and re-map all of your columns from scratch.I'm not sure what the Maximum amount of rows are that you can change this to - So have a look on Google and see if it helps.Kind Regards,Colin MacguireThu, 18 Sep 2008 05:29:33 GMTIgnacio-326487http://www.sqlservercentral.com/Forums/Topic503823-148-1.aspxIf using SSIS and the package will be running on the sql server itself then you can use SQL Server destination but if the sql server is on a remote server, you'll have to use an Ole DB destination.Tue, 10 Jun 2008 14:15:30 GMTJames Connorhttp://www.sqlservercentral.com/Forums/Topic503823-148-1.aspxI've created a set of SSIS packages which run fine in our test environment. The packages access a SQL server database on the local server. I can change the data source to use Windows or SQL Server authentication and both work.We've transferred the packages to another server, and again are running them against a local sql server database. Using Windows authentication they work fine, but when I change them to use SQL Server authentication they fail with :-An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Could not bulk load because SSIS file mapping object 'Global\DTSQLIMPORT ' could not be opened. Operating system error code 5(Access is denied.). Make sure you are accessing a local server via Windows security.".From the documentation I understand that the SQL Server Data Flow Destination needs permission to create Global Objects - but what needs that permission assigned? Or any other ideas how to cure the problem?Tue, 20 May 2008 09:37:15 GMTEdward Welti