2 step in a sql

is there any way to do two passes?
The first sql will retrieve the date value from the some xyz function and store it in a variable.
The second sql is the 'select statement' sql with reference to the value derived from the previous step.
thanks.

Hi,
If you declare your function to be DETERMINISTIC, the optimizer won't need to call it every time it is referenced.
Just add the keyword DETERMINISTIC after the return type abd before AS or IS:
CREATE OR REPLACE FUNCTION instancesysdate
RETURN DATE
DETERMINISTIC
AS
    ...Other, less desireable alternatives include:
You can call the function once in a sub-query, and then join to the sub-query in your main query, which would probably be much faster than calling a user-defined function on every row. Depeneding on your verswion, you might need some trick, like adding "WHERE ROWNUM = 1" in the siub-query, to make sure it is only executed once.
You can also store the DATE variable in a regular table, or a Global Temporary Table, and join to that.
As someone already mentioned, there are no DATE bind variables, but storing a string representation of the DATE in a VARCHAR2 variable (or a substitution variable) would probably be faster than what you have now.

Similar Messages

  • Steps to connect SQL Server to Oracle works but WHY ??

    The following steps is what I have to do in order to get SQL Server to talk to an Oracle database.
    These steps, for me, work 100% of the time. Any deviation from the following steps will result in failure.
    Rebooting the machine didn't make any difference between each of the steps.
    My question is why I have to install the client a second time?
    All the documentation that I have found at Oracle, Microsoft, or elsewhere state that I only need the InstantClient.
    =========================================
    Some server I don't have access to
    with Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit installed
    Windows XP SP3 - 32bit
    with Microsoft SQL Server 2005 SP3 installed
    The following steps are done on the Windows XP machine.
    1) install win32_11gR2_client
    Select: InstantClient (174.0MB)
    Path: C:\Oracle
    2) install ODTwithODAC112021
    Select: Oracle Data Access Components for Oracle Client
    Oracle Base: C:\Oracle
    Name: OraClient11g_home1
    Path: C:\Oracle\product\11.2.0\client_1
    3) Add entries for tnsnames.ora and sqlnet.ora
    4) Ensure environmental variable ORACLE_HOME is set to C:\Oracle\product\11.2.0\client_1
    5) SQL Server Management Studio
    Check "Allow Inprocess" for Oracle Provider OraOLEDB.Oracle
    Restart SQL Server
    Try to add link to Oracle - fails to connect
    "The test connection to the linked server failed."
    Additional information:
    An exception occurred while executing a Transact-SQL statement or batch.
    (Microsoft.SqlServer.ConnectionInfo)
    Cannot initialize the data source object of OLE DB Provider "OraOLEDB.Oracle" for linked server "ORACLEDB".
    OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLEDB" returned message "".
    (Microsoft SQL Server, Error: 7303)
    6) install win32_11gR2_client
    Select: Administrator (1.02GB)
    Oracle Base: C:\Oracle
    Software Location: C:\Oracle\product\11.2.0\client_1
    7) Ensure environmental variable ORACLE_HOME is set to C:\Oracle\product\11.2.0\client_1
    8) Ensure tnsnames.ora and sqlnet.ora still exist and are unchanged.
    9) SQL Server Management Studio
    Restart SQL Server
    Add link to Oracle - Successful

    You actually installed the client *3* times there.
    I'm fairly sure install Instant client via win32_11gR2_client will not give you oraoledb. ODAC and administrator/runtime will though.
    You should only need install ODTwithODAC112021 OR win32_11gR2_client (with runtime or administrator option) and be able to connect using SQLServer.
    Greg

  • Step by step debugging pl/sql procedure

    How can we debug a pl/sql procedure step by step

    We know about this, for a workaround you can try editing jdev-Darwin.conf and adding a line like the following:
    # Add our debug classes to the bootclasspath
    AddVMOption -Xbootclasspath/a:../../rdbms/jlib/ojdi.jar
    In short, ojdi.jar needs to be on the bootclasspath on the mac. I'm not sure how well this will work, but it's one of the changes we're planning for our 10.1.2 release of JDeveloper
    Rob
    Team JDev

  • Steps after learning SQL*PLUS

    hi alll.....
    i know sql*plus with good, now i want the next steps that i have to learn to become a DBA please.
    regards..
    Ali

    user13721099 wrote:
    hi alll.....
    i know sql*plus with good, now i want the next steps that i have to learn to become a DBA please.
    regards..
    Ali=================================================
    Learning how to look things up in the documentation is time well spent investing in your career. To that end, you should drop everything else you are doing and do the following:
    Go to tahiti.oracle.com.
    Drill down to your product and version.
    <b><i><u>BOOKMARK THAT LOCATION</u></i></b>
    Spend a few minutes just getting familiar with what is available here. Take special note of the "books" and "search" tabs. Under the "books" tab you will find the complete documentation library.
    Spend a few minutes just getting familiar with what <b><i><u>kind</u></i></b> of documentation is available there by simply browsing the titles under the "Books" tab.
    Open the Reference Manual and spend a few minutes looking through the table of contents to get familiar with what <b><i><u>kind</u></i></b> of information is available there.
    Do the same with the SQL Reference Manual.
    Do the same with the Utilities manual.
    You don't have to read the above in depth. They are <b><i><u>reference</b></i></u> manuals. Just get familiar with <b><i><u>what</b></i></u> is there to <b><i><u>be</b></i></u> referenced. Ninety percent of the questions asked on this forum can be answered in less than 5 minutes by simply searching one of the above manuals.
    Then set yourself a plan to dig deeper.
    - Read a chapter a day from the Concepts Manual.
    - Take a look in your alert log. One of the first things listed at startup is the initialization parms with non-default values. Read up on each one of them (listed in your alert log) in the Reference Manual.
    - Take a look at your listener.ora, tnsnames.ora, and sqlnet.ora files. Go to the Network Administrators manual and read up on everything you see in those files.
    - When you have finished reading the Concepts Manual, do it again.
    Give a man a fish and he eats for a day. Teach a man to fish and he eats for a lifetime.

  • Steps to migrate SQL Database to Windows/Oracle

    hi
    We have an SQL database in our client network and client wants to migrate it to Windows/Oracle. Currently they have multiple databases on the same SQL server.
    So I am curious to know if oracle also allows the same in Windows.
    I read that we can indeed install one oracle home and use DBCA to create multiple oracle databases on the same host. Any pointers to any documents relevant? I also want to understood this setup and what it means for performance, backup/restore/recovery, patching/upgrade etc.
    Request your valuable inputs on this topic please.
    Regards,
    Raja

    936639 wrote:
    Basically i'm an oracle DBA and never worked in SQL Server. So could you please explain me in detail the below points alone
    " Currently they have multiple databases on the same SQL server (SQL allows it) . So I am curious to know if oracle also allows the same in Windows. I read that we can indeed install one oracle home and use DBCA to create multiple oracle databases on the same host"
    As you said you are an Oracle dba so you should know that within one Oracle home, we can create as many database as we want based on the hardware specs of that machine, though its not a good idea. You can create multiple database definitely under one home on Windows as well.
    Aman....

  • Combine RMAN step and an SQL step in Same Job ?

    Hi experts,
    This is 10.2.0.4 on Windows.
    I want to add an email as the last part of my RMAN backup job (Scheduler job).
    Because Database Control gui requires you to specify a Job Type - RMAN, SQL Script etc will I be able to do both things within a single job? Can I run a "Backup Database plus archivelog" in a SQL Script job type?
    I am a SQL Server DBA still struggling with the simple tasks in the few Oracle databases I support.
    Thank you.
    John

    It may not be possible to do it with Oracle's default job which is, to many of us, something to be avoided.
    Write your own and you will find that you can chain jobs
    http://www.morganslibrary.org/reference/dbms_scheduler.html
    Look at the demo for CREATE_CHAIN.

  • Step-By-Step creation of SQL Server Geo-Clusters?

    Hi All,
    Can anyone provide me a link of nice articles related to Geo-Clusters for SQL Server
    aa

    Hello,
    Please read the following series of articles:
    http://www.mssqltips.com/sqlservertip/2728/sql-server-2012-multisubnet-cluster-part-1/
    http://www.mssqltips.com/sqlservertip/2533/sql-server-2012-multisubnet-cluster-part-2/
    http://www.mssqltips.com/sqlservertip/2746/sql-server-2012-multisubnet-cluster-part-3/
    http://www.mssqltips.com/sqlservertip/2762/sql-server-2012-multisubnet-cluster-part-4/
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • How to do High Avilability Group Configuration steps without SAN or ISCSI storage in sql 2012

    Hi I want to know how to configure HAG Always on in sql 2012 that uses
    WSFC on windows 2008 R2 without ISCSI storage???
    srm_2010

    Hi I want to know how to configure HAG Always on in sql 2012 that uses
    WSFC on windows 2008 R2 without ISCSI storage???
    srm_2010
    Please give a try to these URLs:
    Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group
    http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
    How to deploy SQL Server AlwaysOn in a failover cluster without shared storage to achieve high availability SQL
    http://www.techrepublic.com/blog/the-enterprise-cloud/sql-server-2012-alwayson-high-availability-database-for-cloud-data-centers/
    AlwaysOn Architecture
    http://msdn.microsoft.com/en-us/library/jj191711.aspx
    In general it's a good idea to ask SQL Server HA and DR questions here:
    SQL Server HA and DR
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqldisasterrecovery
    Good luck :)
    StarWind Virtual SAN clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • Run 2 SQL Agent Steps In Parallel

    Hello,
    Is it possible to execute 2 STEPS within a SQL Agent Job to run in parallel?
    Right now the option for each step is go to Next Step or Go To Step zzz.  Is it possible to go to multiple steps so steps can be fired off in parallel instead of sequential?  Is this limitation of the SQL Agent Job?  Sequential would waste
    a lot of valuable time as each step imports into different tables so no conflict.
    Your help is appreciated!

    Step x will be execute Transact SQL type with multiple start job t-sql commands (sp_start_job).  But each t-sql command is running sequential, not parallel, right? 
    Yes it will run sequential,but each step can use parallelism ( where same request ,which is broken into different tasks run in parallel) to get it completed if you have made necessary changes.By default things will be sequential.
    Also, Step x will wait until all jobs are completed before the next step right?
    Yes 
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Crystal report/SQL SP/DTSRUN

    Post Author: slk35psu
    CA Forum: Other
    Hi.
    &#91;Crystal Reports version 11.5.9.1076&#93;
    &#91;SQL Server 2000&#93;
    I have a SQL Server stored procedure that runs perfectly
    when I execute it in the database but it does not work in Crystal Report.
    The stored procedure executes two SQL scripts: drop table
    indexes and truncate tables.  After that,
    it calls a DTS package to transfer data from an Oracle database to the SQL
    database.  After the DTS package call, it
    executes two more SQL scripts to put back the table indexes and updates table
    statistics.  I can run the stored
    procedure in the SQL database (on both my computer and on its server).  The problem occurs when the stored procedure
    is called in the Crystal Report.  In
    Crystal Report, the stored procedure runs the drop table indexes and truncate
    tables scripts and the DTS package.  It
    seems to me that Crystal
    thinks the job is done at the completion of the DTS package and reports a
    success status.  It fails to continue to
    run the table indexes creation script and the table statistics update
    script.  What causes this?
    To summarize, the steps in the SQL database stored procedure
    are:
    Truncate
         tablesDrop
         indexesRun
         DTS package to transfer data from Oracle DB to SQL DBCreate
         indexesUpdate
         statistics
    The stored procedure works find when executed in the SQL database.  When executed in the Crystal Report, it stops
    (and thinks) it is done at the end of the DTS package run (step 3).
    I have pasted my stored procedure code below for your
    review.  Sincerely, Susan Kolonay.
    create proc dbo.WH_DATA_LOAD
    as
    SET NOCOUNT ON
    DECLARE @rc int
    DECLARE @WH_UNAME varchar(30)
    SET @WH_UNAME = 'whu1'
    DECLARE @WH_PWD varchar(30)
    SET @WH_PWD = 'K*e689f(k'
    DECLARE @WH_DB_SERVER_NAME varchar(30)
    SET @WH_DB_SERVER_NAME = 'ddasAA.psu.edu'
    DECLARE @SCRIPTS_LOC varchar(50)
    SET @SCRIPTS_LOC = 'E:\Scripts\cnv\TEST\'
    DECLARE @DTS_PKG_NAME varchar(30)
    SET @DTS_PKG_NAME = 'whse_build_routine'
    DECLARE @TRUNCATE_TBL varchar(200)
    DECLARE @DROP_INDEXES varchar(200)
    DECLARE @DTS_PKG varchar(200)
    DECLARE @CREATE_INDEXES varchar(200)
    DECLARE @UPDATE_TBL_STATS varchar(200)
    /CHECKING TABLE/
    if not exists (select 1 from sysobjects where type='U' and
    name='WH_DATA_LOAD_STATS' and uid=1)
    BEGIN
      PRINT
    'WH_DATA_LOAD_STATS does not exist.'
      RETURN
    END
    /TRUNCATE TEMPORARY TABLE/
    truncate table WH_DATA_LOAD_STATS
    /TRUNCATE TABLES/
    insert into WH_DATA_LOAD_STATS (time_started, process)
    values (getdate(), 'truncate table')
    SET @TRUNCATE_TBL = 'isql -U '@WH_UNAME' -P '@WH_PWD' -n
    -i '@SCRIPTS_LOC'trunc_whse_tables.sql 2>&1'
    EXEC @rc = master.dbo.xp_cmdshell @TRUNCATE_TBL
    IF @rc <> 0
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='failed' where
    process='truncate table'
    END
    ELSE
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='success' where
    process='truncate table'
    END
    /DROP INDEXES/
    insert into WH_DATA_LOAD_STATS (time_started, process)
    values (getdate(), 'drop indexes')
    SET @DROP_INDEXES = 'isql -U '@WH_UNAME' -P '@WH_PWD' -n
    -i '@SCRIPTS_LOC'drop_whse_indexes.sql 2>&1'
    EXEC @rc = master.dbo.xp_cmdshell @DROP_INDEXES
    IF @rc <> 0
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='failed' where
    process='drop indexes'
    END
    ELSE
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='success' where
    process='drop indexes'
    END
    /DTS PKG/
    insert into WH_DATA_LOAD_STATS (time_started, process)
    values (getdate(), 'DTS pkg')
    SET @DTS_PKG = 'dtsrun /S '@WH_DB_SERVER_NAME' /U sa /P
    abcdefg123 /N '@DTS_PKG_NAME' 2>&1'
    EXEC @rc = master.dbo.xp_cmdshell @DTS_PKG
    IF @rc <> 0
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='failed' where process='DTS
    pkg'
    END
    ELSE
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='success' where
    process='DTS pkg'
    END
    /CREATE INDEXES/
    insert into WH_DATA_LOAD_STATS (time_started, process)
    values (getdate(), 'create indexes')
    SET @CREATE_INDEXES = 'isql -U '@WH_UNAME' -P '@WH_PWD'
    -n -i '@SCRIPTS_LOC'create_whse_indexes.sql 2>&1'
    EXEC @rc = master.dbo.xp_cmdshell @CREATE_INDEXES
    IF @rc <> 0
    BEGIN
      update WH_DATA_LOAD_STATS
    set time_ended=getdate(), status='failed' where process='create indexes'
    END
    ELSE
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='success' where
    process='create indexes'
    END
    /UPDATE STATISTICS/
    insert into WH_DATA_LOAD_STATS (time_started, process)
    values (getdate(), 'update statistics')
    SET @UPDATE_TBL_STATS = 'isql -U '@WH_UNAME' -P
    '@WH_PWD' -n -i '@SCRIPTS_LOC'update_whse_stats.sql 2>&1'
    EXEC @rc = master.dbo.xp_cmdshell @UPDATE_TBL_STATS
    IF @rc <> 0
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='failed' where
    process='update statistics'
    END
    ELSE
    BEGIN
      update
    WH_DATA_LOAD_STATS set time_ended=getdate(), status='success' where
    process='update statistics'
    END
    /*select upper(process)'('status')'char(10)
    char(9)'Started on '+convert(varchar(8), time_started, 114)
                  +' ended
    on '+convert(varchar(8), time_ended, 114)
                  '   DURATION:'convert(varchar,datediff(mi,
    time_started, time_ended))+' minutes.'
          AS "REPORT"
    from WH_DATA_LOAD_STATS
    /*select process
         , status
    convert(varchar(8), time_started, 114) as "START_TIME"
    convert(varchar(8), time_ended, 114) as "END_TIME"
    convert(varchar,datediff(mi, time_started, time_ended)) as
    "DURATION_in_MIN"
    from WH_DATA_LOAD_STATS
    /*select '('status') 'upper(process)'Started on
    'convert(varchar(8), time_started, 114)' ended on '+convert(varchar(8),
    time_ended, 114)+' 
    DURATION:'convert(varchar,datediff(mi, time_started, time_ended))'
    minutes.' AS "REPORT"
    from WH_DATA_LOAD_STATS
    RETURN
    go

    Post Author: yangster
    CA Forum: Crystal Reports
    you are over thinking the problemsimply create a parameter within crystal for your state and change it to allow multiple valuesthen in the select expert put in state = ?stateif you do show sql query you will see that the values are pushed down to the sql level thus no performance hit vs putting the parameter directly in the command itself

  • UUT Result log in SQL database?

    Hello All
    I am facing a requirement where i want to log results of sequence execution[only the complete seq result and NOT step results] to SQL database BUT as and when the UUT_ID varies the entry should be made into a new column with the same name as UUT_ID. As of now whenever i execute a sequence with different UUT_ID, a new row gets added as a result.
    Please reply back with your suggestions asap, as this very urgent for me :-)
    Regards
    Nitin Goel

    But in my opinion, that's just a way to display the results - not a way to store the data. I also have thousands of test cases and tens of thousands of different UUT each month. Each UUT has a separate record (a unique row) and yet if I design a proper query and report format, I can show the results exactly like you have. The design of a relational database should not be the same as a report design, imho.
    A database is designed to have unlimited rows (dependent only on storage space). I'm not sure a db can have unlimited columns. That would be something you could check with your dba. Dynamically adding a new column and doing an update to an existing row would probaby be much slower than just doing an insert.

  • SQL 2012 AlwaysON High Availability for SharePoint 2013

    Our Company have 2 Webfront Servers for Sharepoint 2013 and one Database SQL 2012 Server.
    We got one more Server & we don't have Storage so need to configure Always On.
    There are Some Confusions:
    1- Database Server is in production, so how much down time required to Achieve the AlwaysOn?
    2- What are the Changes need to be done on Production Server?
    3- What are the Steps to be followed While Configuring new Database Server?
    Regards,

    Hi Genius1985,
    According to your description, you want to configure a SQL Server 2012 AlwaysOn Availability Group for your database, right?
    Question 1: Database Server is in production, so how much down time required to achieve the AlwaysOn?
    There is no a certain downtime for AlwaysOn, it depends on the configuration of our AlwaysOn Availability Group, normally it can be several seconds or minutes. In order to understand why there is downtime for SQL Server with Microsoft Clustering, please refer
    to the following article:
    http://www.mssqltips.com/sqlservertip/1882/understanding-why-there-is-still-downtime-for-sql-server-with-microsoft-clustering/
    Question 2 and 3: What are the Changes need to be done on Production Server? What are the Steps to be followed While Configuring new Database Server?
    Since AlwaysOn Availability Groups require a Windows Server Failover Cluster, we first need to add the Windows Failover Cluster Feature to all the machines running the SQL Server instances that we will configure as replicas.
    Once the Windows Server Failover Cluster has been created, we need to proceed with enabling the AlwaysOn Availability Groups feature in SQL Server 2012.  This needs to be done on all of the SQL Server instances that we will configure as replicas in our
    Availability Group.
    For more details about Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group, please refer to the following article:
    http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
    If you have any question, please feel free to let me know.
    Regards,
    Jerry Li

  • Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)

    Hi ALl,
    I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
    Contents of summary log:
    Overall summary:
       Final result:                  Failed: see details below
       Exit code (Decimal):           -2068578304
       Exit facility code:            1204
       Exit error code:               0
       Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
    exist.
       Start time:                    2015-01-09 10:19:12
       End time:                      2015-01-09 10:20:07
       Requested action:              Install
    Setup completed with required actions for features.
     Troubleshooting information for those features:
       Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
     Machine Properties:
       Machine name:                  IDCSQLTST11
       Machine processor count:       2
       OS version:                    Future Windows Version
       OS service pack:              
       OS region:                     United States
       OS language:                   English (United States)
       OS architecture:               x64
       Process architecture:          64 Bit
       OS clustered:                  No
    Product features discovered:
       Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
    Package properties:
       Description:                   Microsoft SQL Server 2012
       ProductName:                   SQL Server 2012
       Type:                          RTM
       Version:                       11
       SPLevel:                       0
       Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
       Installation edition:          Standard
    Product Update Status:
       None discovered.
    User Input Settings:
       ACTION:                        Install
       ADDCURRENTUSERASSQLADMIN:      false
       AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
       AGTSVCPASSWORD:                <empty>
       AGTSVCSTARTUPTYPE:             Automatic
       ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
       ASCOLLATION:                   Latin1_General_CI_AS
       ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
       ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
       ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
       ASPROVIDERMSOLAP:              1
       ASSERVERMODE:                  MULTIDIMENSIONAL
       ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
       ASSVCPASSWORD:                 <empty>
       ASSVCSTARTUPTYPE:              Manual
       ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
       ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
       BROWSERSVCSTARTUPTYPE:         Disabled
       CLTCTLRNAME:                  
       CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
       CLTSTARTUPTYPE:                Manual
       CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
       CLTSVCPASSWORD:                <empty>
       CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
       COMMFABRICENCRYPTION:          0
       COMMFABRICNETWORKLEVEL:        0
       COMMFABRICPORT:                0
       CONFIGURATIONFILE:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
       CTLRSTARTUPTYPE:               Manual
       CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
       CTLRSVCPASSWORD:               <empty>
       CTLRUSERS:                     DOMAINAA\user12345
       ENABLERANU:                    false
       ENU:                           true
       ERRORREPORTING:                false
       FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
    DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
       FILESTREAMLEVEL:               0
       FILESTREAMSHARENAME:           <empty>
       FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
       FTSVCPASSWORD:                 <empty>
       HELP:                          false
       INDICATEPROGRESS:              false
       INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server
       INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server
       INSTALLSQLDATADIR:             <empty>
       INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
       INSTANCEID:                    MSSQLSERVER
       INSTANCENAME:                  MSSQLSERVER
       ISSVCACCOUNT:                  NT Service\MsDtsServer110
       ISSVCPASSWORD:                 <empty>
       ISSVCSTARTUPTYPE:              Automatic
       MATRIXCMBRICKCOMMPORT:         0
       MATRIXCMSERVERNAME:            <empty>
       MATRIXNAME:                    <empty>
       NPENABLED:                     0
       PID:                           *****
       QUIET:                         true
       QUIETSIMPLE:                   false
       ROLE:                         
       RSINSTALLMODE:                 DefaultNativeMode
       RSSHPINSTALLMODE:              SharePointFilesOnlyMode
       RSSVCACCOUNT:                  NT Service\ReportServer
       RSSVCPASSWORD:                 <empty>
       RSSVCSTARTUPTYPE:              Manual
       SAPWD:                         <empty>
       SECURITYMODE:                  SQL
       SQLBACKUPDIR:                  <empty>
       SQLCOLLATION:                  Latin1_General_CI_AS
       SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
       SQLSVCPASSWORD:                <empty>
       SQLSVCSTARTUPTYPE:             Automatic
       SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
       SQLTEMPDBDIR:                  F:\TempDB
       SQLTEMPDBLOGDIR:               <empty>
       SQLUSERDBDIR:                  E:\SQLData
       SQLUSERDBLOGDIR:               D:\SQLLog
       SQMREPORTING:                  false
       TCPENABLED:                    1
       UIMODE:                        Normal
       UpdateEnabled:                 true
       UpdateSource:                  MU
       X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
    Detailed results:
       Feature:                       Database Engine Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Server Replication
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Full-Text and Semantic Extractions for Search
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Data Quality Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Analysis Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services - Native
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services - SharePoint
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services Add-in for SharePoint Products
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Data Quality Client
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Integration Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools Connectivity
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Management Tools - Complete
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools SDK
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools Backwards Compatibility
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Distributed Replay Controller
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Distributed Replay Client
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Server Data Tools
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Management Tools - Basic
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Client Connectivity
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Client Connectivity SDK
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Writer
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Documentation Components
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Browser
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
    Exception summary:
     The following is an exception stack listing the exceptions in outermost to innermost order
     Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
         Message:
             The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x84b40000
             FacilityCode : 1204 (4b4)
             ErrorCode : 0 (0000)
         Data:
           SQL.Setup.FailureCategory = InputSettingValidationFailure
           DisableWatson = true
         Stack:
             at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
             at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
             at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
             at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
         Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
             Message:
                     The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
             HResult : 0x87d00006
                     FacilityCode : 2000 (7d0)
                     ErrorCode : 6 (0006)
             Data:
               DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
               SettingName = CLTRESULTDIR
               WatsonData = 
    Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

    Hello,
    Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
    means each parameter:
    http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
    You will also find the list of features supported by each edition on the following article:
    http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
    For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com
    Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
    would Microsoft tease you like that? Frustrating since I spent hours on this ..

  • SSIS package fails under SQL Server Agent job

    Hi All
    I have designed a SSIS package to encrypt a file using Cipher (EFS) it works fine from BIDS & Package Execution Utility.
    But SQL Server Agent job is failing to do this. I am getting the error as
    " In executing C:\Windows\System32\Cipher.exe /e /a C:\Test.txt at "",The Process Exit code was 1 while the expected was 0." 
    Please help me.
    Thanks

    Two things that usually come to mind when this happens from BIDS locally to the SQL Agent are
    1. Security is not
    adequate under the SQL Agent Service Account
    Rule the security problem out by setting up a proxy account that you know ahs security to run the needed tasks in the package.  Either that or give the service account the permissions needed.
    2. 32bit BIDS development and running under a 64bit Platform in your SSIS installation
    This can be fixed by selecting run in 32bit more or running the package with the 32bit installed version of DTEXEC found in the Program Files (x86) folder where you installed tools.
    Next, setup logging in the package so you get a more detailed error message.  Event handlers on the tasks will be much more detailed using the OnError event.  you can write that to either a flat file with a data flow in the event handler or simply
    insert the event into a table using the ? as the parms.  If you need assistance setting that up, here are basic steps for a SQL Server table
    1) Select the task and click the event handler tab in BIDS
    2) Select OnError event handler in the list
    3) Click the enable link and drag a Execute TSQL Task over to the window
    4) Create a table in your SQL Server database (create one so you don't litter your user DBs if needed)
    5) Open the task and add the connection as needed.  Then add this statement
    INSERT INTO dbo.TableYouCreated
    (PackageName, SourceName, EventInfo)
    VALUES (?,?,?)
     6) Go to parameter mappings and add 4 new mappings as following
    System::PackageName
    Input
    nvarchar
    0
    System::SourceName
    Input
    nvarchar
    1
    System::ErrorDescription
    Input
    nvarchar
    2
    Save and reimport the package and then the event of the errors should insert into the table in detail 
    Ted Krueger
    Blog on lessthandot.com @onpnt on twitter

  • SSIS Package Runs OK Manually But Not From SQL Server Agent...Permissions?

    I have a problem where I have an SSIS package (SQL Server 2005) that won't run properly from SQL Server Agent, but it runs fine when kicked off manually from Integration Services -> Run Package or when run in debug from Visual Studio.
    The first step in the package checks for the existance of a file via a script task.  The script looks like this...
    Code Block
    Public Sub Main()
    Dim TaskResult As Integer
    Dim ImportFile As String = CStr(Dts.Variables("BaseDirectory").Value) + CStr(Dts.Variables("ImportDirectory").Value) + CStr(Dts.Variables("ImportFile").Value)
    If Dir(ImportFile) = "" Then
    Dts.TaskResult = Dts.Results.Failure
    Else
    Dts.TaskResult = Dts.Results.Success
    End If
    Return
    End Sub
    This script runs fine and the file is seen as expected when I run the package manually.  But as a step in a SQL Server Agent job, it doesn't see the file.
    The SQL Server Agent service is set to start up / log on as a Local System Account.  I've also tried setting up a credential / proxy (using an account that I know can see and even move / rename the file) to run the job as but that didn't seem to help.
    The package is being run from SQL Server (stored in MSDB) and is set to rely on SQL Server for sensitive information, so I don't think that's an issue; other packages are set up like this in terms of sensitive data and run fine.
    Any ideas why my script can't "see" the file I'm looking at when it's kicked off by SQL Server agent?  I've looked and looked...I can't seem to figure this out.  I would really appreciate any help you might be able to offer up.

    If the variables are fine, then I think it is very likely that this is security related. Since the Agent is running under the local system account, have you verified that the local account can access the file? When you tried the proxy account, are you positive that it was set up properly, and that the account had the permissions to read the file?
    Another thing to check - is this a local file or is on another computer? If it is on another computer, make sure you are using a UNC path and not a mapped drive.

Maybe you are looking for

  • I keep receiving a message, everytime I open iTunes, asking me if I want to accept incoming network connections.

    After trying to delete the .plist I realised my iTunes had become corrupted and needed to be reinstalled. This may not be a fix for everyone, but here is how I uninstalled and reinstalled. iTunes comes preinstalled as part of OS X, and is considered

  • Could my months-old kernel panic be related to overheating/fan troubles?

    Greetings, all. At a certain point last year my computer's only functionality was a kernel panic. Startup and restart would yield either a crash in the middle of booting, or a KP after the computer was up and running for only a minute. All checks hav

  • How do I add a PDF to a combined file

    I'm having difficulty combining files and keep getting an error message that doesn't save my combined file once complete ... are the pdfs to large?

  • General workflow between FCS and FCP question....

    Hey all. I'm totally new to FCS, and while in a few hours I've figured out a lot about how it works, what is totally eluding me is how to establish an efficient work flow back and forth between FCS and FCP...it's really driving me crazy. Yeah, I know

  • Do I need tsafsgw?

    We have just upgraded to GW 12.02. We use Back Express as a backup solution. I;ve checked and: smsconfig -t Shows: loaded TSAs are: tsafs --EnableGW When I go to my Backup Express Console I can no longer see the DOm,ain adn PO's and Syncsort have adv