Licensing question for AD enterprise with new SQL Server

Hi!
We have Server 2008 R2 STD where our AD is located and it has enough User CAL's. Additionally we have Terminal server with TS licenses.
Now we're purchasing a Server 2012 where we plan to install SQL Server 2012 STD where we will install our third party program and this program is going to be used through Terminal server. 
Now the question is do I only need SQL CAL's or will I have to get both SQL CAL's AND User CAL's for the new server? I'm thinking AD servers User CAL's is enough for the whole enterprise, but I'm not 100% sure and need help with this!
Thanks!

Licensing questions should be directed to trained Microsoft licensing specialists instead of a technical forum. 
www.microsoft.com/licensing. 
That said, SQL CALs and operating system CALs are sold separately.  Talk with the vendor from whom you are purchasing your licenses.  They should be able to help you sort out the CAL questions.
. : | : . : | : . tim

Similar Messages

  • Trouble Turneing on FileStream/Ad Hoc Query with new SQL Server 2014 64-BIt Version

    SQL Server Help,
    I have recently installed SQL SERVER 2014 on my Window 7 SP1 Acer laptop.
    I am trying to do a simple upload of an Excel file into SQL Server using the OPENROWSET command:
    Which I found requires some configuration change I attempted below.
    When I execute this:
    execute sp_configure 'show advanced options', 1;
    RECONFIGURE;
    execute sp_configure 'Ad Hoc Distributed Queries', 1;
    RECONFIGURE;
    GO
    I get this message
    Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
    Msg 5593, Level 16, State 1, Line 2
    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    Msg 15123, Level 16, State 1, Procedure sp_configure, Line 62
    The configuration option 'Ad Hoc Distributed Queries' does not exist, or it may be an advanced option.
    Msg 5593, Level 16, State 1, Line 4
    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    When I go to the SQL Server Services and Properties on the Server and try to change the FileStream options to be on..I get the error:
    "There was an unknown error applying the FILESTREAM settings.  Check the parameters are valid (0x80070002)."
    Perhaps my issue is with the Windows Share Name:  .  I have put in a local driver C:\A_Excel....also the computer name, my user ID.   Is there a special format or way to define a Share Name that I am unaware of?
    Is there a way to fix this?  Can I not load Excel files with a 64-Bit system?  Or what is the easiest way that I can do this with my configuration?
    Thanks for any help.

    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    By the error message it seems you have a 64 bit OS, but have installed a 32 bit SQL Server and here in WoW64 mode filestream seems to be not supported. Install a 64 bit SQL Server instead.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?

    What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
    Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
    In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
    So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
    Thanks for any indications.

    1. What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
    Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
    2. In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
    3. So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
    Thanks for any indications.
    I will answer your question point wise
    1. Keeping license key is good idea it helps you during audit and you have proof that you are using a valid Microsoft License. Plus in scenario of disaster where whole box gets damanged you might need to install SQL Server again in that case during
    reinstallation on setup page where you need to enter key you might need need it. If you are missing your paper then you are in trouble.
    2. Only on product key page license key is required and it is not required anywhere else during installation. Unless you enter valid product key installation will not proceed further.
    3 License makes you a valid owner of Microsoft product with restrictions on how much hardware resource you can use how much max connections you can make etc. Key lets you install it on Windows machine making sure that you are using valid Microsoft product.
    This was just a general idea please speak to your licensing specialist for more details. This is technical forum and we generally ask user to speak to licensing expert for such queries.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • Building New SQL Server To Migrate from Old one and need to figure out how I need to license it.

    So my head is spinning on setting up a New SQL Server.
    Current setup is Microsoft Server 2003 Standard and Microsoft SQL Server 2000 Standard. Nothing was maintained with Software assurance.
    Environment:
    Database is Limited to 2008 R2 Standard as Highest release I can use with it. So I know I need to do a Downgrade.
    New Server can Be either Microsoft Server standard 2008 or 2012 x64.
    The Domain Controller for right now is going to remain a Machine with Server 2003 Standard x86. It is Licensed with 30 Cals.
    The office Environment:
    The Office has any where from 5-7 employees.
    They have 3 Office locations and employees are in 1 of the three locations depending on the day.
    Between all 3 Offices they have 27 computers.
    Employees also can access multiple machines through out the day.
    Reception, Checkout and Third employee will be at their own machine.
    3 Employees will be accessing their main machine but also float to at the most 6 other machines located in the office these machines are logged in in the morning using their own user name Employees don't login or logout on them throughout the day.
    If they are in The Main Office they access the SQL server machine directly.
    If they are in one of the two satellite offices the Employees will access the SQL server through the front end running on Terminal Services running on the SQL server.
    My New Server will be Either a 4 or 6 core Xeon Processor.
    So the Questions.
    Lets say the scenario is I am buying Windows 2012 Server and Cals and Buying SQL 2012 Server and Cals and will be downgrading both to 2008.
    How do I need to license Windows Server? How many Cals do I need and what way should they be setup?
    How do I need to license SQL Server? By Server? By Core? How Many Cals do I need?
    Thank You.

    Hi,
    In addition, basically a downgrade is possible in case the SQL Server editions are the same. Downgrade is only supported in case a downgrade of e.g. SQL2012 Enterprise to SQL2008R2 Enterprise is done.
    I have attached a link to the SQL Server 2012 Licensing Reference Guide. Look at “Upgrades, Downgrades and Step-Ups” section of the document and check which version and editions are supported for the downgrade.
    SQL_Server_2012_Licensing_Reference_Guide
    Hope it helps.
    Tracy Cai
    TechNet Community Support

  • What is available on new Windows servers that allow you to write scripts that can work directly with Windows, SQL Server, and Exchange Server?

    What is available on new Windows servers that allow you to write scripts that can work directly with Windows, SQL Server, and Exchange Server?
    a. PowerShell
    b. isql
    c. osql
    d. sqlcmd

    All questions seem to be from the interview or a test. I think I even took this test once, it's KForce test.
    For every expert, there is an equal and opposite expert. - Becker's Law
    My blog
    My TechNet articles

  • Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

    Hi,
    how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
    I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
    This question has worried me for days.
    Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
    Or just an new solution instead of using the catalog.deploy_project?
    best wishes from Qingyuan Lee.

    Sorry, my description may be confusable.
    I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
    In fact,  I don't care about the authority.
    I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
    so, using EXECUTE AS to change the execution context is accaptable.
    The requirement for a Windows Authentication Account makes sense.
    I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
    Thanks very much for your help.

  • Problems configuring Platform Domain with MS Sql Server

    Hi,
    We are having problems configuring a Platform Domain with MS Sql Server 2000.
    We are using Weblogic version 7.0.0.2. These are the steps we followed
    1.We manually created a database called TestDB and created a user account called
    "system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
    the TestDB created.
    2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
    SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
    in this file.
    3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
    and modified the RDBMS realm properties to point to the database.
    4. ran the create_db script and it seemed to have run fine looking at the log
    file.
    5. I then tried to start the BEA Server instance and I get the following error.
    I am also attaching the config.xml file for reference.
    Appreciate any help/suggestions. Thanks in Advance.
    Vikram
    <Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
    ating a database connection for the realm.
    java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
    at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
    193)
    at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
    at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
    02)
    at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
    69)
    at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
    elegate.java:962)
    at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
    at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
    at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.security.acl.Realm.getRealm(Realm.java:87)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    <Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    in
    itialize the server: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    Reason: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    [config.xml]

    Try removing the server section from the SchemaProperties line.
    Preferrably do not use localhost or hostnames in the server
    configuration file.
    <RDBMSRealm
    Name="wlcsRealm"
    DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
    DatabasePassword="weblogic"
    DatabaseURL="jdbc:weblogic:mssqlserver4:yourIPAddress:1433"
    RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"
    SchemaProperties="user=system;password=weblogic"/>
    Also consider ...
    If you have a new Portal database created in SQL Server?
    Does the user system have the Portal database as his default database?
    -- Jim
    Vikram wrote:
    Hi,
    We are having problems configuring a Platform Domain with MS Sql Server 2000.
    We are using Weblogic version 7.0.0.2. These are the steps we followed
    1.We manually created a database called TestDB and created a user account called
    "system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
    the TestDB created.
    2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
    SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
    in this file.
    3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
    and modified the RDBMS realm properties to point to the database.
    4. ran the create_db script and it seemed to have run fine looking at the log
    file.
    5. I then tried to start the BEA Server instance and I get the following error.
    I am also attaching the config.xml file for reference.
    Appreciate any help/suggestions. Thanks in Advance.
    Vikram
    <Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
    ating a database connection for the realm.
    java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
    at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
    193)
    at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
    at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
    02)
    at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
    69)
    at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
    elegate.java:962)
    at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
    at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
    at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.security.acl.Realm.getRealm(Realm.java:87)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    in
    itialize the server: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    Reason: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <Domain Name="epmsDomain">
    <Log
    FileName="logs/wl-domain.log"
    Name="epmsDomain"
    />
    <!-- Configuration Wizard Cluster and Admin/Managed Node support -->
    <Server
    Name="platformServer"
         ListenAddress="localhost"
    ListenPort="7501"
    NativeIOEnabled="true"
    TransactionLogFilePrefix="logs/"
    >
    <SSL
    Name="platformServer"
    ListenPort="7502"
    Enabled="true"
    ServerCertificateChainFileName="ca.pem"
    ServerCertificateFileName="democert.pem"
    ServerKeyFileName="demokey.pem"
    />
    <Log
    FileName="logs/weblogic.log"
    />
    <WebServer
    DefaultWebApp="splashPage"
    LogFileName="./logs/access.log"
    LoggingEnabled="true"
    Name="platformServer"
    />
    </Server>
    <!-- WLP Pool -->
    <JDBCConnectionPool
    Name="commercePool"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="weblogic"
    InitialCapacity="20"
    MaxCapacity="20"
    CapacityIncrement="1"
    RefreshMinutes="0"
    ShrinkingEnabled="false"
    Targets="platformServer"
    TestConnectionsOnReserve="false"
    TestTableName="WEBLOGIC_IS_ALIVE"
    />
    <!-- WLI Pool -->
    <JDBCConnectionPool
    CapacityIncrement="2"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    InitialCapacity="8"
    LoginDelaySeconds="1"
    MaxCapacity="36"
    Name="wliPool"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="weblogic"
    RefreshMinutes="0"
    ShrinkPeriodMinutes="15"
    ShrinkingEnabled="true"
    Targets="platformServer"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="false"
    JNDIName="weblogic.jdbc.jts.commercePool"
    Name="commercePool"
    PoolName="commercePool"
    Targets="platformServer"
    />
    <JDBCDataSource
    JNDIName="weblogic.jdbc.pool.commercePool"
    Name="commercePool"
    PoolName="commercePool"
    Targets="platformServer"
    />
    <JDBCDataSource
    JNDIName="WLAI_DataSource"
    Name="WLAI_DataSource"
    PoolName="wliPool"
    Targets="platformServer"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="com.bea.wlpi.TXDataSource"
    Name="TXDataSource"
    PoolName="wliPool"
    Targets="platformServer"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="WLCHub.DS"
    Name="WLCHub.DS"
    PoolName="wliPool"
    Targets="platformServer"/>
    />
    <!-- Configure WebLogic Workshop to run in Platform domain -->
    <JDBCTxDataSource
         EnableTwoPhaseCommit="true"
    JNDIName="cgDataSource"
    Name="cgDataSource"
    PoolName="commercePool"
    Targets="platformServer"/>
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="cgSampleDataSource"
    Name="cgSampleDataSource"
    PoolName="commercePool"
    Targets="platformServer"/>
    <JMSConnectionFactory JNDIName="weblogic.jws.jms.QueueConnectionFactory"
    Name="cgQueue" Targets="platformServer"/>
    <JMSJDBCStore ConnectionPool="commercePool" Name="cgJDBCStore" PrefixName="WEBLOGIC"/>
    <JMSServer Name="cgJMSServer" Store="cgJDBCStore" Targets="platformServer">
    <JMSQueue JNDIName="jws.queue" Name="cgJWSQueue" StoreEnabled="default"/>
    </JMSServer>
    <JTA Name="epmsDomain" TimeoutSeconds="3600"/>
    <!-- End: Configure WebLogic Workshop to run in Platform domain -->
    <!-- WLP DATASYNC -->
    <JDBCConnectionPool
    Name="dataSyncPool"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="WEBLOGIC"
    InitialCapacity="1"
    MaxCapacity="5"
    CapacityIncrement="1"
    RefreshMinutes="0"
    ShrinkingEnabled="false"
    TestConnectionsOnReserve="false"
    TestTableName="WEBLOGIC_IS_ALIVE"
    Targets="platformServer"/>
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="false"
    JNDIName="weblogic.jdbc.jts.dataSyncPool"
    Name="dataSyncPool"
    PoolName="dataSyncPool"
    Targets="platformServer"/>
    />
    <!-- General Config -->
    <Security
    GuestDisabled="false"
    Name="epmsDomain"
    PasswordPolicy="wl_default_password_policy"
    Realm="wl_default_realm"
    CompatibilityMode="true"
    />
    <PasswordPolicy
    Name="wl_default_password_policy"
    />
    <Realm
    Name="wl_default_realm"
    CachingRealm="wlcsCachingRealm"
    FileRealm="wl_default_file_realm"
    />
    <CachingRealm
    BasicRealm="wlcsRealm"
    CacheCaseSensitive="true"
    Name="wlcsCachingRealm"
    />
    <RDBMSRealm DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
    DatabasePassword="weblogic"
    DatabaseURL="jdbc:weblogic:mssqlserver4:localhost:1433"
    SchemaProperties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Name="wlcsRealm"
    RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"/>
    <FileRealm
    Name="wl_default_file_realm"
    />
    <StartupClass
    ClassName="com.beasys.commerce.ebusiness.security.KeyBootstrap"
    FailureIsFatal="false"
    Name="KeyBootstrap"
    Targets="platformServer"
    />
    <!-- WLI configuraion for Platform -->
    <JMSConnectionFactory Name="WLI_B2B_TopicFactory"
    JNDIName="com.bea.wli.b2b.server.TopicConnectionFactory"
    AllowCloseInOnMessage="true"
    UserTransactionsEnabled="true"
    Targets="platformServer"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wli.b2b.rosettanet.QueueConnectionFactory"
    Name="RNQueueFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="false"
    DefaultDeliveryMode="Persistent"
    DefaultPriority="4"
    DefaultTimeToLive="0"
    JNDIName="com.bea.wlai.JMSConnectionFactory"
    MessagesMaximum="10"
    Name="WLAI_JMSConnectionFactory"
    OverrunPolicy="KeepOld"
    UserTransactionsEnabled="true"
    Targets="platformServer"/>
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wlpi.TopicConnectionFactory"
    Name="wlpiFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wlpi.QueueConnectionFactory"
    Name="wlpiQueueFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSJDBCStore
    ConnectionPool="wliPool"
    Name="JMSWLIStore"
    PrefixName="PBPUBLIC"
    />
    <JMSServer Name="WLIJMSServer"
    Targets="platformServer"
    TemporaryTemplate="TemporaryTemplate"
    Store="JMSWLIStore">
    <JMSTemplate Name="TemporaryTemplate"/>
    <!-- B2B -->
    <JMSQueue Name="WLI_B2B_RNEncoderQueue"
    JNDIName="com.bea.wli.b2b.rosettanet.EncoderQueue"/>
    <JMSTopic Name="WLI_B2B_Topic"
    JNDIName="com.bea.wli.b2b.server.B2BTopic"/>
    <JMSQueue Name="WLI_B2B_OutboundQueue"
    JNDIName="com.bea.b2b.OutboundQueue"/>
    <!-- BPM -->
    <JMSTopic Name="wlpiEvent"
    JNDIName="com.bea.wlpi.EventTopic"/>
    <JMSQueue Name="WLI_BPM_Timer"
    JNDIName="com.bea.wli.bpm.TimerQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSQueue Name="WLI_BPM_Event"
    JNDIName="com.bea.wli.bpm.EventQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSQueue Name="WLI_BPM_ValidatingEvent"
    JNDIName="com.bea.wli.bpm.ValidatingEventQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSTopic Name="WLI_BPM_Error"
    JNDIName="com.bea.wli.bpm.ErrorTopic"/>
    <JMSTopic Name="WLI_BPM_Audit"
    JNDIName="com.bea.wli.bpm.AuditTopic"/>
    <JMSTopic Name="WLI_BPM_Notify"
    JNDIName="com.bea.wli.bpm.NotifyTopic"/>
    <!-- AI -->
    <JMSQueue Name="WLAI_ASYNC_REQUEST_QUEUE"
    JNDIName="com.bea.wlai.ASYNC_REQUEST_QUEUE"/>
    <JMSQueue Name="WLAI_ASYNC_RESPONSE_QUEUE"
    JNDIName="com.bea.wlai.ASYNC_RESPONSE_QUEUE"/>
    <JMSQueue Name="WLAI_EVENT_QUEUE"
    JNDIName="com.bea.wlai.EVENT_QUEUE"/>
    <JMSTopic Name="WLAI_EVENT_TOPIC"
    JNDIName="com.bea.wlai.EVENT_TOPIC"/>
         <!-- App View control -->
         <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_ASYNC_RESPONSE_QUEUE" Name="WLAI_WORKSHOP_ASYNC_RESPONSE_QUEUE"/>
         <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_EVENT_QUEUE" Name="WLAI_WORKSHOP_EVENT_QUEUE"/>
    <!-- WLI -->
    <JMSQueue Name="WLI_FailedEvent"
    JNDIName="com.bea.wli.FailedEventQueue"
    StoreEnabled="true"/>
    <JMSTemplate Name="WLI_JMSTemplate"
    ErrorDestination="WLI_FailedEvent"
    RedeliveryDelayOverride="60000"
    RedeliveryLimit="10"/>
    </JMSServer>
    <JMSJDBCStore Name="JMSWLIStore"
    ConnectionPool="wliPool"
    PrefixName="platformServer"/>
    <!-- Distributed queue/topic configuration for WLI components -->
    <!-- End WLI configuraion for Platform -->
    <!--===========================================================================-->
    <!-- Configure the J2EE enterprise applications supporting the Platform -->
    <!--===========================================================================-->
    <!-- The enterprise application containing the WLS-based Tax and Payment WebService -->
    <Application
    Deployed="true"
    Name="taxWSApp"
    Path="C:/bea/user_projects/epmsDomain/beaApps/taxWSApp"
    TwoPhase="true"
    >
    <EJBComponent
    Name="tax"
    URI="tax.jar"
    Targets="platformServer"
    />
    <WebAppComponent
    Name="tax-webservice"
    URI="tax-ws"
    Targets="platformServer"
    />
    </Application>
    <Application
    Deployed="true"
    Name="paymentWSApp"
    Path="C:/bea/user_projects/epmsDomain/beaApps/paymentWSApp"
    TwoPhase="true"
    >
    <EJBComponent
    Name="payment"
    URI="payment.jar"
    Targets="platformServer"
    />
    <WebAppComponent
    Name="payment-edit webservice"
    URI="pay-ws"
    Targets="platformServer"
    />
    </Application>
    <!-- The enterprise application containing the installed/online links documentation -->
    <Application
    Deployed="true"
    Name="wlpDocsApp"
    Notes=""
    Path="C:/bea/weblogic700/portal/lib"
    TwoPhase="true"
    >
    <WebAppComponent
    IndexDirectoryEnabled="false"
    Name="wlpDocs"
    Targets="platformServer"
    URI="wlpDocs.war"
    ServletReloadCheckSecs="300"
    />
    </Application>
    <!-- The enterprise application containing the WLP components -->
    <Application
    Deployed="true"
    Name="portalApp"
    Notes=""
    Path="C:/bea/user_projects/epmsDomain/beaApps/portalApp"
    TwoPhase="true"
    >
    <ApplicationConfiguration
    Name="portalApp"
    Targets="platformServer"
    URI="META-INF/application-config.xml"
    />
    <EJBComponent
    Name="events"
    Targets="platformServer"
    URI="events.jar"
    />
    <EJBComponent
    Name="pipeline"
    Targets="platformServer"
    URI="pipeline.jar"
    />
    <EJBComponent
    Name="property"
    Targets="platformServer"
    URI="property.jar"
    />
    <EJBComponent
    Name="rules"
    Targets="platformServer"
    URI="rules.jar"
    />
    <EJBComponent
    Name="usermgmt"
    Targets="platformServer"
    URI="usermgmt.jar"
    />
    <EJBComponent
    Name="customer"
    Targets="platformServer"
    URI="customer.jar"
    />
    <EJBComponent
    Name="ebusiness"
    Targets="platformServer"
    URI="ebusiness.jar"
    />
    <EJBComponent
    Name="portal"
    Targets="platformServer"
    URI="portal.jar"
    />
    <EJBComponent
    Name="campaign"
    Targets="platformServer"
    URI="campaign.jar"
    />
    <EJBComponent
    Name="catalogws"
    Targets="platformServer"
    URI="catalogws.jar"
    />
    <EJBComponent
    Name="document"
    Targets="platformServer"
    URI="document.jar"
    />
    <EJBComponent
    Name="ejbadvisor"
    Targets="platformServer"
    URI="ejbadvisor.jar"
    />
    <EJBComponent
    Name="mail"
    Targets="platformServer"
    URI="mail.jar"
    />
    <EJBComponent
    Name="placeholder"
    Targets="platformServer"
    URI="placeholder.jar"
    />
    <WebAppComponent
    Name="toolSupport"
    Targets="platformServer"
    URI="toolSupport"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="tools"
    Targets="platformServer"
    URI="tools"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="datasync"
    Targets="platformServer"
    URI="datasync"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="splashPage"
    Targets="platformServer"
    URI="splashPage"
    ServletReloadCheckSecs="300"
    />
    <!-- The enterprise application containing the WLP P13N Console components -->
    </Application>
    <Application
    Deployed="true"
    TwoPhase="true"
    StagedTargets="platformServer"
    Name="p13nConsoleApp"
    Path="C:/bea/weblogic700/portal/lib"
    >
    <WebAppComponent
    Name="p13nConsole"
    ServletReloadCheckSecs="300"
    Targets="platformServer"
    URI="p13nConsole.war"
    />
    </Application>
    <!-- The enterprise application containing the WLI components -->
    <Application Deployed="true" LoadOrder="900" Name="EAI" Path="C:/bea/weblogic700/samples/workshop/wlai/ear/" TwoPhase="true">
    <EJBComponent
    DeploymentOrder="100"
    Name="repository-ejb.jar"
         Targets="platformServer"
    URI="repository-ejb.jar"/>
    <EJBComponent Name="WLI-B2B Startup"
    DeploymentOrder="200"
    Targets="platformServer"
    URI="b2b-startup.jar"/>
    <EJBComponent DeploymentOrder="300" Name="b2b-rosettanet.jar" Targets="platformServer" URI="b2b-rosettanet.jar"/>
    <WebAppComponent DeploymentOrder="400" Name="b2b.war" Targets="platformServer" URI="b2b.war"/>
    <WebAppComponent DeploymentOrder="500" Name="b2bconsole.war" Targets="platformServer" URI="b2bconsole.war"/>
    <EJBComponent DeploymentOrder="600" Name="WLI-AI Server" Targets="platformServer" URI="wlai-server-ejb.jar"/>
    <WebAppComponent DeploymentOrder="700" Name="wlai" Targets="platformServer" URI="wlai.war"/>
    <EJBComponent DeploymentOrder="800" Name="WLI-AI Async Processor" Targets="platformServer" URI="wlai-asyncprocessor-ejb.jar"/>
    <EJBComponent DeploymentOrder="900" Name="WLI-AI Event Processor" Targets="platformServer" URI="wlai-eventprocessor-ejb.jar"/>
    <EJBComponent DeploymentOrder="1000" Name="wlpi-ejb.jar" Targets="platformServer" URI="wlpi-ejb.jar"/>
    <EJBComponent DeploymentOrder="1100" Name="wlpi-master-ejb.jar" Targets="platformServer" URI="wlpi-master-ejb.jar"/>
    <EJBComponent DeploymentOrder="1200" Name="wlpi-mdb-ejb.jar" Targets="platformServer" URI="wlpi-mdb-ejb.jar"/>
    <EJBComponent DeploymentOrder="1300" Name="WLXTEJB.jar" Targets="platformServer" URI="WLXTEJB.jar"/>

  • Can i install new SQL server on my computer using service pack 2 or its just a patch

    I want to install new sql server on my computer and I have sql server 2012 enterprise core edition with service pack 2 .Can I use it create a new server ?

    If you have the same file which is avalable for download from the following link, it is just service pack: 
    Microsoft® SQL Server® 2012 Service Pack 2 (SP2)
    Cheers,
    Saeid Hasani
    Database Consultant
    Please feel free to contact me at [email protected] as well as on Twitter and Facebook.
    [My Writings on TechNet Wiki] [T-SQL Blog] [Curah!]
    [Twitter] [Facebook] [Email]

  • How to get JDev 10.1.2/ADF working with MS SQL Server Identity Column

    Hello JDevTeam & JDevelopers,
    I want to use JDev/ADF with a MS SQL Server 2005 database that contains tables employing IDENTITY Columns.
    Using JDev/ADF and DBSequence with an Oracle database employing before triggers/sequences accomplishes what I am trying to do except I want to accomplish the same thing using a MSSQL Server 2005 database. Unfortunately I cannot change the database.
    I have been able to select records but I am unable to insert records (due to my lack of knowledge) when using MS/SQL Server Identity Columns with JDev/ADF.
    The following are the steps taken thus far.
    Step1: Create table named test in the 2005 MSSQL Server (see script below).
    Step2: Register 3rd Party JDBC Driver with JDeveloper; Using use Tools/Manage Libraries. Create a new entry in User Libraries with the following;
         Library Name     = Ms2005Jdbc
         Class Path     = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu\sqljdbc.jar
         (note: Latest TYPE 4 JDBC driver for Microsoft SQL Server 2005 - free at http://msdn.microsoft.com/data/ref/jdbc/)
    Step3:Create New Database Connection;
         Connection Name = testconn1
         Type = Third Party JDBC Driver
         Authentication Username = sa, Password = password, Check Deploy Password
         Connection
              Driver Class = com.microsoft.sqlserver.jdbc.SQLServerDriver     
              Library = Ms2005Jdbc     
              Classpath = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu
              URL = jdbc:sqlserver://192.168.1.151:1433;instanceName=sqlexpress;databaseName=test
         Test Connection = Success!
    Step5: Create a new application workspace using Web Application default template
    Step6: In Model project, Create new Business Components Diagram.
    Step7: Create new Entity Object. Goto to connections/testconn1, open tables and drag table test onto the diagram.
    Step8: Generate Default Data Model Components by right-clicking on Entity Object. Except all the defaults.
    When I test the Appmodule I select the view object and can scroll through all the records without error. If I try to insert a record, I get JBO-27014: Attribute testid in test is required.
    Going back to the EntityObject I deselect the Mandatory attribute and re-run the test. Now when I try to insert it accepts the value for testname but it does not update the PK testid like it would using an "JDev/ADF/DBSequence/Oracle database/before trigger/sequence" solution.
    Going back to the EntityObject and selecting refresh on insert does not solve this problem either. Changing the URL connection string and adding "SelectMethod=cursor" did not help and changing the SQl Flavor to SQLServer produced errors in the Business Components Browser. I've tried overriding isAttributeChanged() and other things as well.
    I am totally stuck! Can anyone provide a solution?
    Thanks for you help,
    BG...
    Create table named test
    use [testdb]
    go
    set ansi_nulls on
    go
    set quoted_identifier on
    go
    create table [test](
         [testid] [int] identity(0,1) not null,
         [testname] [nvarchar](50) collate sql_latin1_general_cp1_ci_as not null,
    constraint [pk_test] primary key nonclustered
         [testid] asc
    )with (pad_index = off, ignore_dup_key = off) on [primary]
    ) on [primary]

    Figured it out!
    When using the MS SQL Server 2000 Database with the MS JDBC 2000 Driver you specify the SQL Flavor to SQLServer. However setting the SQL Flavor to SQLServer with MS SQL Server 2005 Database and the MS JDBC 2005 Driver will *** fail ***.
    When working with the MS SQL Server 2005 Database and the MS JDBC 2005 Driver you set the SQL Flavor to SQL92 and the Type Map to Java.
    If using a named instance like I am you would specify the URL = jdbc:sqlserver://<db host ip address>:<listening port>;instanceName=<your instance name>;selectMethod=cursor;databaseName=<your database name> (note: leave out the < >)
    The 2005 Driver Class is different then the 2000 and is specified as com.microsoft.sqlserver.jdbc.SQLServerDriver
    Note: In a default MS SQL Server 2005 installation the listening port will change *** everytime *** the host is restarted! You can override this though.
    For the primary key you need to deselect the Mandatory attribute in the EntityObject editor.
    Set Refresh on insert/update = no.
    Set Updateable = never.
    Now my Primary Keys which get their values from the Identity Column are working with ADF in a predictable way.
    Simple enough but I have been away from this stuff for awhile.
    BG...

  • Problem using DG4ODBC with named SQL Server instance

    I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].  {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
    ORA-02063: preceding 2 lines from DEVMISC
    odbc.ini
    [GENERALI_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = CLTDMJCWBYZ.eu.scor.local
    User                    = everest
    Password                = everest
    Database                = Everest_Generali
    [DEVMISC_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = [USVCLTDEVSQL02\DEVMISC]
    User                    = link_user
    Password                = password1
    Database                = DBA
    initDG4ODBC2.ora
    # HS init parameters
    HS_FDS_CONNECT_INFO = DEVMISC_DSN
    HS_FDS_TRACE_LEVEL = DEBUG
    HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
    # ODBC specific environment variables
    set ODBCINI=/home/oracle/.odbc.ini
    listener.ora
    SID_LIST_LISTENER_GW =
       (SID_LIST =
          (SID_DESC =
           (SID_NAME=DG4ODBC)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
    soft/sqlncli/lib)
          (PROGRAM=dg4odbc)
          (SID_DESC =
           (SID_NAME=DG4ODBC2)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
    osoft/sqlncli/lib)
          (PROGRAM=dg4odbc)
    LISTENER_GW =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
    tnsnames.ora
    DG4ODBC =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC))
          (HS=OK)
    DG4ODBC2 =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC2))
          (HS=OK)
    I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

    Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
    Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
    who states that named instance connections are not supported using that driver.
    - Klaus

  • MCTS 70-466 Implementing Data Models and Reports with Microsoft SQL Server 2012

    I am searching for training kit for Exam 70-466 (Implementing Data Models and Reports with Microsoft SQL Server 2012) but I think is not published yet. I was expecting its release in Jan or Feb 2014. Would any one can tell me its release date or any place
    where I can find this book.
    Thanks
     

    Hi Azhar lqbal Gondal,
    According to your description, since the issue regards training and certification,
     I suggest you post the question in the Learning forums at
    http://social.technet.microsoft.com/Forums/en-US/home?category=learning. It is appropriate and more experts will assist you. If you have a specific technical question about Microsoft SQL Server,
     you can visit and post your question on  the SQL Server Forum.
    There is some detail about Exam 70-466 Implementing Data Models and Reports with Microsoft SQL Server 2012, you can review the following articles.
    Exam content can be found here:
    http://www.microsoft.com/learning/en-us/exam-70-466.aspx
    http://borntolearn.mslearn.net/certification/database/w/wiki/525.466-implementing-data-models-and-reports-with-microsoft-sql-server-2012.aspx#fbid=Mn-t6aRhs-H
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Anyone successfully set up connection pool in s1as with ms sql server 2000?

    As subject. Since I have seen a lot of posts about the NoSuchMethodException issue with various dbms providers, and the only "official information" I found thru different forums, google, different sun/javasoft sites and forums are this:
    http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsunone%2F8172&zone_32=NoSuchMethodException&wholewords=on
    Which is wonderfully vague and provide not-so-much useful information...
    As for the information and suggestion posted by other forum members, most or all of them have experience with setting up Oracle, DB2, mySQL, etc., not aimed for MS SQL Server 2000 (you may think, I am just asking for it running MS SQL server with Java... oh well, not my choice)
    I still haven't seen any positive feedbacks on how this exception was caused and how to resolve it. I have literally exhausted all leads on how to fix this issue, so right now I'm only interested to know whether anyone in the forum actually have a successful connection pool set up with MS SQL server 2000.
    My platform:
    w2k sp3
    SunOne app server, update1, JDK 1.4.1
    latest MS SQL 2000 JDBC driver
    This fails with the NoSuchMethodException error:
    try {
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup("test_db");
    con = ds.getConnection();
    System.out.println( "con is created -> " + con );
    } catch (Exception ex) {
    System.out.println( "failed -> " + ex.getMessage() );
    This works just fine:
    try {
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = DriverManager.getConnection("jdbc:microsoft:sqlserver://xxx.xxx.xxx.xxx:1433;DatabaseName=testdb;SelectMethod=cursor", "username", "password");
    System.out.println( "con is created -> " + con );
    } catch (Exception ex) {
    System.out.println( "failed is fucked -> " + ex.getMessage() );
    thanks,
    --kuan

    Hi,
    Thanks for pointing out that article, I did not find it previously. After following the directions in the artile and your advise, now dbping seems to be able to connect to SQL server.
    Thank you very much.
    --kuan                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • SharePoint 2010 DB moved to new SQL server

    Hi All,
      Quick Question.. When we move SP 2010 DB to one SQL server to New One .. What are thing need to followed to make sure Sites are working fine 
    V Jean

    Hi.  I recently followed that guide (http://technet.microsoft.com/en-us/library/cc512723(v=office.14).aspx) and it went pretty well.  Before starting, I recommend
    you ensure the new SQL server is prepared by ensuring:
    1. It has enough disk space to hold the database(s) and allow for growth
    2. Firewall ports are opened to allow connections from the SharePoint server
    3. The hardware meets the requirements
    4. You have RBS enabled if required
    5. You have backups!
    Dave

  • 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.

  • New SQL Server Failover Cluster Installation - No disk is available to select in section "Cluster Disk Slection"

    Hello Everyone,
    I am in a deep need for your help regarding the problem I am facing.
    I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
    be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
    I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
    No roles were created, 2 nodes are available and 1 network is there in the cluster.
    If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
    Thanks in advance for your support and looking forward for your valuable feedbacks.
    Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

    Dear Ashwin,
    I have granted the privileges mentioned in the link you provided as below:
      Act as Part of the Operating Sywstem = SeTcbPrivileg
      Bypass Traverse Checking = SeChangeNotify
      Lock Pages In Memory = SeLockMemory
      Log on as a Batch Job = SeBatchLogonRight
      Log on as a Service = SeServiceLogonRight
      Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
    I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
    Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Maybe you are looking for