Minimum requirements for deploying a package on Sql Server 2008

I am trying to setup a restricted login to deploy packages. At the very least I need to avoid using the sysadmin server role however all of my testing seems to point to my restricted login requiring it which sort of defeats the purpose of a restricted
login. Without the sysadmin account I get the following error: Create failed for JobStep

Role
Read action
Write action
own package roles.
db_ssisoperator
Enumerate all packages.
View all packages.
Execute all packages.
Export all packages.
Execute all packages in SQL Server Agent.
None
Windows administrators
View execution details of all running packages.
Stop all currently running packages.
Sysssispackages Table
The sysssispackages table in msdb contains the packages that are saved to SQL Server. For more information, see sysssispackages
(Transact-SQL).
The sysssispackages table includes columns that contain information about the roles that are assigned to packages.
The readerrole column specifies the role that has read access to the package.
The writerrole column specifies the role that has write access to the package.
The ownersid column contains the unique security identifier of the user who created the package. This column defines the owner of the package.
Permissions
By default, the permissions of the db_ssisadmin and db_ssisoperator fixed database-level roles and the unique security identifier of the user who created the package apply to the reader role for packages,
and the permissions of the db_ssisadmin role and the unique security identifier of the user who created the package apply to the writer role. A user must be a member of the db_ssisadmin, db_ssisltduser,
or db_ssisoperator role to have read access to the package. A user must be a member of the db_ssisadmin role to have write access.
Please click "Mark as Answer" if the post solves your problem - Thanks

Similar Messages

  • When Deploying SSIS Packages to SQL Server using SSMS Import feature, is the package configuration file deployed at the same time?

    Hello, everyone,
    I have an SSIS package with a XML package configuration file. I deployed it to the sql server using the import feature in SSMS (in Stored Packages, right click MSDB, select Import, select the package to deploy in file system). My question is 
    Is the XML package configuration file also deployed? If so, which folder is it stored so that I can change the values in it? If not, is setting up the Configuration tab when scheduling a agent job the way to go manually bring the configuration file in?
    Your help and information is much appreciated.
    Regards

    Thank you Arthur for your reply. I appreciate it.
    A followup questions:
    I used direct setting for the configuration file path on C:\. But it needs to be on D:\ on the remote server. I can't create the D:\ path because I don't have D:\ drive on my computer (I understand I could use indirect setting to change the path in the remote
    server. But that's not the concern here).
    My question is:  since the configuration is not deployed, can I make it up by setting up the Configurations in creating the agent job step? That is, copy the configuration file to the D:\ drive on the remote server, in Configurations tab, add the configuration
    file on D:\ to the configuration. Will it work? Will the package still look for the original config file on C:\?  and if it doesn't find it there, will it cause any error?
    Thank you in advance for your help.
    Regards

  • Trying to install Support for DTS packages in SQL server 2008

    Hi all
    I am trying to follow the instructions in the following link...
    technet.microsoft.com/en-us/library/ms143755(v=sql.105).aspx
    ...to install support for DTS packages - when it says on the Feature Selection page, select Integration Services - none of the installs I have tried show this as an option - what should I be installing in order to see this and get this feature installed?
    I just need to be able to view some DTS packages - help!
    Thank you! James

    Hello James,
    as can be read in the article:
    Microsoft SQL Server 2008 Service Pack 2 Feature Pack => SQLServer2005_BC.msi  (BC
    = backward compatibilty).
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Systemcopy issue for Netweaver 7.02 on SQL server 2008

    Hi colleagues,
    we do a system copy for ECC6.0 ehp5 DBexport, based on Netweaver 7.0 ehp2.
    system: windows server 2003R2 + MS SQL server 2008R2, everything seems ok until "import ABAP" stage, every import is failed!
    I do find some notes : 1339717 and 1480785, talk about update Kernel, but after I update kernel, also change the SQLfiles.lst, the issue still the same.
    this DBexport can install successfully on MaxDB database. is there anyone performe System copy successfully on Netweaver 7.0 ehp2 on SQL server 2008? what kind of update need to be done?
    thanks!
    zongyun

    Hi Markus,
    thanks for the reply, here I post the log files, please help me to analyze what is the real issue and how to solve it.
    import_monitor.log:
    INFO: 2011-08-24 11:25:35
    Import Monitor is started.
    CONFIG: 2011-08-24 11:25:35
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=C:\SAP\Export\ABAP
    installDir=C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP
    jobNum=3
    loadArgs=-loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2011-08-24 11:25:35
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2011-08-24 11:25:35
    List of packages with views: 'SAPVIEW'.
    TRACE: 2011-08-24 11:25:35 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL' template file is started.
    INFO: 2011-08-24 11:25:35 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2011-08-24 11:25:35
    Data codepage 4103 is determined using TOC file 'C:\SAP\Export\ABAP\DATA\DD03L.TOC' for package 'DD03L'.
    TRACE: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_5' import package is started.
    TRACE: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask run
    Loading of 'DOKCLU' import package is started.
    TRACE: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC_5' import package:
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\SAP\Export\ABAP\DATA\SAPSSEXC_5.STR "C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" SAPSSEXC_5.TSK MSS -l SAPSSEXC_5.log
    TRACE: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'DOKCLU' import package:
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\SAP\Export\ABAP\DATA\DOKCLU.STR "C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" DOKCLU.TSK MSS -l DOKCLU.log
    TRACE: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_2' import package is started.
    TRACE: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC_2' import package:
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\SAP\Export\ABAP\DATA\SAPSSEXC_2.STR "C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" SAPSSEXC_2.TSK MSS -l SAPSSEXC_2.log
    ERROR: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask run
    Loading of 'DOKCLU' import package is interrupted with R3load error.
    Process 'C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\SAP\Export\ABAP\DATA\DOKCLU.STR "C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" DOKCLU.TSK MSS -l DOKCLU.log' exited with return code 2.
    For mode details see 'DOKCLU.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_2' import package is interrupted with R3load error.
    Process 'C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\SAP\Export\ABAP\DATA\SAPSSEXC_2.STR "C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" SAPSSEXC_2.TSK MSS -l SAPSSEXC_2.log' exited with return code 2.
    For mode details see 'SAPSSEXC_2.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2011-08-24 11:25:35 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC_5' import package is interrupted with R3load error.
    Process 'C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\SAP\Export\ABAP\DATA\SAPSSEXC_5.STR "C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" SAPSSEXC_5.TSK MSS -l SAPSSEXC_5.log' exited with return code 2.
    For mode details see 'SAPSSEXC_5.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    DOKCLU.log
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110824112535
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#3 $ SAP
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
    Compiled May  7 2010 03:20:08
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\SAP\Export\ABAP\DATA\DOKCLU.STR C:\Program Files\sapinst_instdir\NW702\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL DOKCLU.TSK MSS -l DOKCLU.log
    (TPL) ERROR: unknown template variable "compression_page"
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
    C:\usr\sap\VE5\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20110824112535

  • Table design for an indicator field in SQL Server 2008 R2

    Hi, I am using SQL Server 2008 R2 and I have an existing table (Please see the below table definition).
    CREATE TABLE Code
    ID INT IDENTITY (1, 1) PRIMARY KEY,
    Code NVARCHAR(10) NOT NULL UNIQUE,
    [Description] NVARCHAR(100) NOT NULL,
    [Type] NVARCHAR(30) NULL,
    Program NVARCHAR(30) NOT NULL, --Adding this column as a filter for different programs
    ModifiedDate DATETIME NOT NULL DEFAULT (getdate()),
    ModifiedBy NVARCHAR(128) NOT NULL DEFAULT (suser_sname())
    This table has been in use for a while and I am adding a column [Program] to identify records for that program. Previously it used to be just one program and this [Code] table was working just fine now there are 5 different programs introduced in the organization
    and this could keep changing over time.
    For instance Program A uses Code A, Code B, Code C & Program B uses Code C, Code D, Code E & Program C uses Code C. I know of an option which works but creates maintenance overhead
    everytime these programs change by doing something like below.
    Code ProgramA ProgramB ProgramC ProgramD ProgramE
    A      Yes
    B      Yes
    C      Yes           Yes           Yes
    D                      Yes
    E                       Yes
    But, is there a better way to do this keeping 1 column for Program and users being able to manage their data without looking at other codes. I mean a user who manages Program A should be able
    to see codes A, B, C & user managing Program B should see codes C, D, E & for Program C just code C.
    Thanks in advance.....
    Ione

    I would add it as a seperate table with columns as
    ProgramName  CodeName
    the data would be like
    ProgramName CodeName
    ProgramA A
    ProgramA B
    ProgramA C
    ProgramB C
    ProgramB D
    ProgramB E
    ProgramC C
    then its just a matter of adding a join from your above table to this table on Code field to get associated Program info and filter on it.
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Need clear steps for doing performance tuning on SQL Server 2008 R2 (DB Engine, Reporting Services and Integration Services)

    We have to inverstigate about a reporting solution where things are getting slow (may be material, database design, network matters).
    I have red a lot in MSDN and some books about performance tuning on SQL Server 2008 R2 (or other) but frankly, I feel a little lost in all that stuff
    I'am looking for practical steps in order to do the tuning. Someone had like a recipe for that : a success story...
    My (brain storm) Methodology should follow these steps:
     Resource bottlenecks: CPU, memory, and I/O bottlenecks
     tempdb bottlenecks
     A slow-running user query : Missing indexes, statistics,...
     Use performance counters : there are many, can one give us the list of the most important
    how to do fine tuning about SQL Server configuration
    SSRS, SSIS configuration ? 
    And do the recommandations.
    Thanks
    "there is no Royal Road to Mathematics, in other words, that I have only a very small head and must live with it..."
    Edsger W. Dijkstra

    Hello,
    There is no clear defined step which can be categorized as step by step to performance tuning.Your first goal is to find out cause or drill down to factor causing slowness of SQL server it can be poorly written query ,missing indexes,outdated stats.RAM crunch
    CPU crunch so on and so forth.
    I generally refer to below doc for SQL server tuning
    http://technet.microsoft.com/en-us/library/dd672789(v=sql.100).aspx
    For SSIS tuning i refer below doc.
    http://technet.microsoft.com/library/Cc966529#ECAA
    http://msdn.microsoft.com/en-us/library/ms137622(v=sql.105).aspx
    When I face issue i generally look at wait stats ,wait stats give you idea about on what resource query was waiting.
    --By Jonathan KehayiasSELECT TOP 10
    wait_type ,
    max_wait_time_ms wait_time_ms ,
    signal_wait_time_ms ,
    wait_time_ms - signal_wait_time_ms AS resource_wait_time_ms ,
    100.0 * wait_time_ms / SUM(wait_time_ms) OVER ( )
    AS percent_total_waits ,
    100.0 * signal_wait_time_ms / SUM(signal_wait_time_ms) OVER ( )
    AS percent_total_signal_waits ,
    100.0 * ( wait_time_ms - signal_wait_time_ms )
    / SUM(wait_time_ms) OVER ( ) AS percent_total_resource_waits
    FROM sys.dm_os_wait_stats
    WHERE wait_time_ms > 0 -- remove zero wait_time
    AND wait_type NOT IN -- filter out additional irrelevant waits
    ( 'SLEEP_TASK', 'BROKER_TASK_STOP', 'BROKER_TO_FLUSH',
    'SQLTRACE_BUFFER_FLUSH','CLR_AUTO_EVENT', 'CLR_MANUAL_EVENT',
    'LAZYWRITER_SLEEP', 'SLEEP_SYSTEMTASK', 'SLEEP_BPOOL_FLUSH',
    'BROKER_EVENTHANDLER', 'XE_DISPATCHER_WAIT', 'FT_IFTSHC_MUTEX',
    'CHECKPOINT_QUEUE', 'FT_IFTS_SCHEDULER_IDLE_WAIT',
    'BROKER_TRANSMITTER', 'FT_IFTSHC_MUTEX', 'KSOURCE_WAKEUP',
    'LAZYWRITER_SLEEP', 'LOGMGR_QUEUE', 'ONDEMAND_TASK_QUEUE',
    'REQUEST_FOR_DEADLOCK_SEARCH', 'XE_TIMER_EVENT', 'BAD_PAGE_PROCESS',
    'DBMIRROR_EVENTS_QUEUE', 'BROKER_RECEIVE_WAITFOR',
    'PREEMPTIVE_OS_GETPROCADDRESS', 'PREEMPTIVE_OS_AUTHENTICATIONOPS',
    'WAITFOR', 'DISPATCHER_QUEUE_SEMAPHORE', 'XE_DISPATCHER_JOIN',
    'RESOURCE_QUEUE' )
    ORDER BY wait_time_ms DESC
    use below link to analyze wait stats
    http://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/
    HTH
    PS: for reporting services you can post in SSRS forum
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Which Laptop is good for VS 2012/2013 and SQL SERVER 2008 R2 /2012 ?

    Hi,
    I am planing to buy a laptop.
    I am gonna be using mostly for Visual sStudio 2013 and Sql Server 2012 .
    my budget is $1000.
    confuse between DELL/ HP / LENOVO..!!!
    please help.

    This is only a personal taste of mine:
    I prefer to work in Virtual Machines. In fact I did set up a VM just for my programming. This has the advantage that games and other stuff are not slowed down by SQL Server Services and similiar stuff.
    This also allows me to quickly make a small virtual networks with multiple clients if I need to test some client/server stuff.
    Plus I am also a bit of an adminstrator and prefer to test stuff in VM's before I try them in the real world.
    I prefer using Virtual Box for Virtual Machines, so one thing of big importance was support for VT-X/AMD-V. Without them Virtual Box cannot run x64 guests even on a x64 host system.
    Otherwise I wanted Windows 8 (so I could finally learn to live with it/learn programming for it's UI). And of big importance was an upgrade of gaming ability (my old one had difficulty/impossibility to run most current games).
    So I bought a x64, Win8 Gaming Laptop with 8 GiB RAM (so I can run 3-6 Windows 7 hosts in paralell) and looked that the CPU supported Hardware Virtualsiation.
    Otherwise pretty much every current laptop will work. x64 OS might be prefereable, as .NET has some limitations under x32/x86 OS (like the
    2 GiB limit). Multicore (2 or more) is pretty much the state of the art (are there still any single core CPU's out there?).
    It of course needs to be a Windows (7 or 8) to support VS. New Laptops should have UEFI (all that are sold with Windows 8 have).
    If you do not need a lot of storage, using a SSD instead of a HDD will propably speed up startups (Windows, Programms) and compilation times a lot (those are disk-heavy operations) - but I only know that it should and heard of people who have them.
    Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

  • How to Create a SQL Agent Job For A SSIS Package with Sql Server Authentication

    Hi ALl,
    I have a SSIS package which basically has a data flow task in which i pull the data from one server and copy it into another server and my source server is the one where i dont have windows authentication and i have to only use a sql server authentication
    . This package runs fine if i click the server connection properties type the password and save it.
    Now, my task is to set up a sql agent job which basically uses a proxy account and takes this package from the file system and runs it.But when i try to run this package, its failing with an error saying 
    "Login Failed For rpt5user" where rpt5user is the username for my sql server authentication of the source connection.
    Can someone please help me with any suggestions on how to do this?
    I have heard that we can achieve it by using xml config file which i have never used and i am trying to google around but for no luck.
    So, If someone can please throw any suggestions or ideas on this it would be great.
    Thanks

    You need to add password as a config item and set it from the file source or sql table
    see this as an example
    http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Error in SSIS Package in SQL Server 2008 R2

    Dear All,
    I am getting below error in SSIS Package.
    [OLE DB Destination [31]] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "The statement has been terminated.".
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >,
    >= or when the subquery is used as an expression.".
    The SSIS package reads .xml file from a folder and then mapped to insert values in SQL table from there one trigger writtern on table to update other tables.
    Pld guide me cause of the issue
    -- Kind Regards Sandeep

    Dear All,
    I am getting below error in SSIS Package.
    [OLE DB Destination [31]] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "The statement has been terminated.".
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when
    the subquery is used as an expression.".
    The SSIS package reads .xml file from a folder and then mapped to insert values in SQL table from there one trigger writtern on table to update other tables.
    Pld guide me cause of the issue
    -- Kind Regards Sandeep
    Query should return only one value. Instead it is returning more than one value. Check the query result in ssms.
    Thanks.
    - please mark correct answers

  • SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

    I am working in a Product based company.
    We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
    I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
    I have used "Script Component" in my package.
    We will take only DTSX package file to the customer places and run using SQL Agent Job daily. 
    Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
    Who are all(Customer Environments) using SQL 2012, I am facing the below issue 
    The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
    Still the same package is running fine for some of the customers having SQL 2012.
    I am getting the above error only for few customers.
    Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

    Hi Katherine,
    I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
    Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
    Here is my Simple .net code
    /* Microsoft SQL Server Integration Services Script Component
    *  Write scripts using Microsoft Visual C# 2008.
    *  ScriptMain is the entry point class of the script.*/
    using System;
    using System.Data;
    using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
    using Microsoft.SqlServer.Dts.Runtime.Wrapper;
    [Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
    public class ScriptMain : UserComponent
        public override void PreExecute()
            base.PreExecute();
              Add your code here for preprocessing or remove if not needed
        public override void PostExecute()
            base.PostExecute();
              Add your code here for postprocessing or remove if not needed
              You can set read/write variables here, for example:
              Variables.MyIntVar = 100
        int counter = 0;
        public override void Input0_ProcessInputRow(Input0Buffer Row)
            if (counter == 0)
                counter = Convert.ToInt32(Row.JurisCount);
            Row.JurisKey = counter;
            counter = counter + 1;
    PAVAN MSBI

  • Is it possible to have two or more virtual machines point to a shared instance of SQL Server 2008 R2 for systems administration?

    Hello All,
    I am the Systems Admin for a production box running SQL Server 2008 R2.  I have been ask to do the following and and trying to figure out if it's even possible.
    1. The Production Server is named ProductionA
    2. Create 3 Administrator accounts on ProductionA each with access to the SQL Server instance on ProductionA.  Use Standard SQL Server login for credentials. i.e. Username/Password and assign the role sysadmin.
    3. Install 3 Virtual Machines on ProductionA each with Windows 2008 R2 64 bit operating system.
    4. For each Virtual Machine, Install SQL Management Studio and write down the IP Address assigned to each VM.
    5. Using Remote Desktop Connection, connect to each virtual machine to be able to manage the SQL Server.
    Is this possible?  And, why am i doing it?  Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA.  Since I have to allow them to RDC into the box
    to manage the SQL Server, I figure why not create a separate VM for each one of them and they can RDC into those instead.
    Does this make any sense?
    Any tips are greatly appreciated.  The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
    Thanks for your help.
    M

      Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA.  Since I have to allow them to RDC into the box to manage the SQL Server, I figure why not create
    a separate VM for each one of them and they can RDC into those instead.
    Does this make any sense?
    Any tips are greatly appreciated.  The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
    Thanks for your help.
    M
    Hello M,
    Since you dont want the 3 guys to have access to Production machine A.You can install SQL Server client .By client i mean SQL server management studio(SSMS) on there local desktop and then create login for them in SQL Server.Open port on which your SQL server
    is running for three of the machines so that they can connct.Now with SSMS installed on each machine each can connect to SQL server from there own machine.
    I would also like you to be cautious with giving Sysadmin privilege to all three of them ,first please note down what task they would do and then decide what rights to be provided.
    Your option will also work but you need to create 3 VM for that .Which is more tedious task.
    Hope this helps
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Getting error code 1 when calling SSIS package from a stored procedure (SQL Server 2008 R2)

    Hello,
    I am trying to execute a SSIS package from SQL Server 2008 R2 stored procedure but getting error code 1 (as per my knowledge, error code description is as below:
    0 The package executed successfully.
    1 The package failed.
    3 The package was canceled by the user.
    4 The utility was unable to locate the requested package. The package could not be found.
    5 The utility was unable to load the requested package. The package could not be loaded.
    6 The utility encountered an internal error of syntactic or semantic errors in the command line.
    Details:
    I have a stored procedure named "Execute_SSIS_Package" (see below sp) which executes 'Import_EMS_Response' SSIS package (when I execute this package directly from SQL Server BID it works fine it means package itself is correct) and calling
    it from SQL as:- EXEC Execute_SSIS_Package 'Import_EMS_Response'.
    Here I receives error code 1.
    Can anyone help me to resolve this issue please?
    Thanks in advance!
    CREATE PROCEDURE [dbo].[Execute_SSIS_Package]
     @strPackage nvarchar(100)
    AS
    BEGIN
     -- SET NOCOUNT ON added to prevent extra result sets from
     -- interfering with SELECT statements.
     SET NOCOUNT ON;
     DECLARE @cmd VARCHAR(8000)
     DECLARE @Result int
     DECLARE @Environment VARCHAR(100)
        SELECT @Environment = Waarde
     FROM  Sys_Settings
     WHERE Optie = 'Omgeving'
     --print @Environment
     SET @strPackage = '"\W2250_NGSQLSERVER\BVT\' + @Environment + '\' + @strPackage + '"'
     SET @cmd = 'dtexec /SQL ' + @strPackage +  ' /SERVER "w2250\NGSQLSERVER"  /Decrypt "BVT_SSIS" /CHECKPOINTING OFF /REPORTING E'
     --print @cmd
     EXECUTE @Result = master..xp_cmdshell @cmd, NO_OUTPUT
     --print @Result
    END

    It has something to do with the security.
    E.g. cmdshell is not enabled or the caller has not rights over the package.
    There could be a syntax error, too.
    I suggest you make the package runnable off a SQL Agent job then trigger the job from the stored proc with
    sp_start_job <job name>
    Arthur
    MyBlog
    Twitter

  • SSIS 2012 package scheduling with SQL Server 2008 R2

    Hi, We have a ssis 2012 package with parameters & would like to schedule this package in SQL Server 2008 R2 agent. Is there a way to pass parameters to the ssis package from SQL Server 2008 R2 agent?
    Thanks in advance..........
    Ione

    You cant use SQL 2008 R2 to schedule it as dtexec 2008 cant execute package created using SSIS 2012. The inverse can be done though
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Run sql 2008 ssis package into sql server 2012 machine

    Hello,
    I have created a ssis package in sql server 2008 and use a job to execute it pointing to databaseA. works fine.
    Then, I place that package into a sql server 2012 machine and use a job to execute it in the same database, databaseA.
    The error I get is something like:
    can not use the old version in the new version machine.
    Is this really the case or am I doing something wrong please?

    Hi Arkiboys,
    Arthur is right that the error occurs because the SSIS 2008 package cannot be upgraded to SSIS 2012 package. When the SSIS 2008 package is called by SSIS 2012 dtexec utility tool, the package will be upgraded temporarily and the changes won’t be saved. Since
    your current SSIS 2008 package cannot be upgraded automatically, you can create the package from scratch in SSDT installed by SQL Server 2010. Another option isto open the SSIS 2008 package in SSDT or add the package to a SSIS 2012 project, then the upgrade
    will be performed automatically. Then, you can check the error message during the upgrade, which may help you to find the tasks/components that cause the upgrade failure. In this way, you can remove the tasks/components in question from the SSIS 2008 package
    and then upgrade the package, and then add the tasks/components in question in SSDT 2010.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here.
    Mike Yin
    TechNet Community Support

  • SQL Server 2008 R2: which version of Visual Studio do I need to keep database projects and SSIS projects in the same solution

    I need to build a solution containing a database project and an integration services project for SQL Server 2008R2.  Apparently, the subset of Visual Studio tools that comes with SQL Server 2008R2 does not include database projects and does not have
    Team Foundation Server support.  Because of those limitations, I am trying to determine which version of Visual Studio will allow me to:
    1. Build a single solution that includes both a database project and an Integration Services project
    2. For the database project, be able to import a database schema from an existing SQL Server 2008 R2 database, do schema compares and update the project from the database and vice versa
    3. For the Integration Services project, be able to deploy the packages to SQL Server Integration Services on SQL Server 2008 R2 (that is, to the msdb database).
    4. Use Team Foundation Server for source control of the whole solution, including both project types.

    Hi G Britton,
    To build a solution containing a database project and an integration services project for SQL Server 2008 R2 and use Team Foundation Server for source control.
     You can choose to install Visual Studio 2008.
    And as you want to utilize Schema compare and/or Data compare functionalities in Visual Studio, you will need to install the
    Visual Studio Team System 2008 Database Edition or Visual Studio Team System 2008 Team Suite.
    In addition, for Visual Studio issues, I would like to recommend you post the question in the
    Visual
    Studio forums to get better support.
    Reference:
    Team Foundation Version Control
    Compare and Synchronize Database Schemas
    Interoperability and Coexistence (Integration Services)
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

Maybe you are looking for