Non-support for SQL LIKE command

I understand from poking around in this forum that the rowset visual Query Editor does not suppor the LIKE command. I also discovered that if I just put it in anyway, then tell the editor to "continue" when it complains, that it works fine at runtime. My question is how exactly, using the other editors/designers in Creator, should I put my hand-entered SQL code if I want to skip using the Query Editor? I am new to the Creator world and cannot find where the SQL statement actually resides. Thanks for the info. I would also like to bind the output of a dropdown list to the query so I can allow the user to pick a starting point for a query from A-Z. Using the dropdown list for the letters, but need to connect that to the query itself.

If you select the RowSet icon - this icon appears just below
the designer (after dropping a database table onto the page)
There's a property, Command
Just copy/paste your SQL here then save all.
Check the Page bean constructor to make sure the
SQL was pasted correctly
John
JSC QA

Similar Messages

  • Support for  Operators like [Between] in ADF QP for String Attributes

    All,
    In the ADF Query Panel there is no support provided for operators like BETEWEEN, NOT BETWEEN, >= and <= etc for attributes of type String. On the Oracle Database we can execute queries like
    SQL> select ename from emp where ename between 'A' and 'C';
    ENAME
    ALLEN
    BLAKE
    ADAMS
    SQL> select ename from emp where ename <= 'B';
    ENAME
    ALLEN
    ADAMS
    The reason I am asking this question is for fusion we expose KeyFlexfields in an ADF Query Panel. Teams like GL store numeric values as Strings/Varchar2 type in the database and would like to perform operations like BETWEEN on strings. Is there a way this can be accomplished.
    Tom
    Edited by: tbenjami on May 27, 2009 11:12 AM

    Lucas,
    Thanks for the suggestion.
    We will look into it.
    Steven davelaar,
    JHeadstart Team.

  • Support for SQL Developer Versions

    Can someone post the Lifetime Support Policy for the different versions of SQL Developer? It seems like you can still be version 1.1 for the archive, but I don't know the cutoff points of support for each version. I looked in the" Lifetime Support Policy: Coverage for Technology Products" document but SQL Developer was not listed. Is there another document that does?
    Thank you -
    ket

    Hi Tomi,
    You cannot directly save the TestStand 3.0 sequences to 1.0. TestStand can save formats upto two versions previous to the current version. So TestStand 3.0 will the sequence into either 2.0.1 or 2.0 version.
    However if you have TestStand 2.0 on your machine, then you can open this TestStand 2.0 sequence and save it as TestStand 1.0 sequence.
    I hope this helps
    SijinK
    National Instruments

  • Simple java class for SQL like table?

    Dear Experts,
    I'm hoping that the java people here at the Oracle forums will be able to help me.
    I've worked with Oracle and SQL since the 90s.
    Lately, I'm learning java and doing a little project in my spare time. 
    It's stand alone on the desktop.
    The program does not connect to any database 
    (and a database is not an option).
    Currently, I'm working on a module for AI and decision making.
    I like the idea of a table in memory.
    Table/data structure with Row and columns.
    And the functionality of:
    Select, insert, update, delete.
    I've been looking at the AbstractTableModel.
    Some of the best examples I've found online (they actually compile and work) are:
    http://www.java2s.com/Code/Java/Swing-JFC/extendsAbstractTableModeltocreatecustommodel.htm
    http://tutiez.com/simple-jtable-example-using-abstracttablemodel.html
    Although they are rather confusing.
    In all the examples I find, there always seems to be
    at least three layers of objects:
    Data object (full of get/set methods)
    AbstractTableModel
    GUI (JFrame, JTable) (GUI aspect I don't need or want)
    In all the cases I've seen online, I have yet to see an example
    that has the equivalent of Delete or Insert.
    Just like in SQL, I want to define a table with columns.
    Insert some rows. Update. Select. Delete.
    Question:
    Is there a better java class to work with?
    Better, in terms of simpler.
    And, being able to do all the basic SQL like functions.
    Thanks a lot!

    Hi Timo,
    Thanks. yes I had gone thru the java doc already and  they have mentioned to use java.sql.Struct, but the code which got generated calls constructor of oracle.jpub.runtime.MutableStruct where it expects oracle.sql.STRUCT and not the java.sql.STRUCT and no other constructor available to call the new implementation and that is the reason i sought for some clues.
      protected ORAData create(CmnAxnRecT o, Datum d, int sqlType) throws SQLException
        if (d == null) return null;
        if (o == null) o = new CmnAxnRecT();
        o._struct = new MutableStruct((STRUCT) d, _sqlType, _factory);
        return o;
    here CmnAxnRecT is the class name of the generated java class for sqlType.
    Thanks again. Please let me know if you have any more clues.
    Regards,
    Vinothgan AS

  • Microsoft Project Server Support for SQL Server 2014

    Does anyone know the timeline for Microsoft Project Server to support deployment on SQL Server 2014?   Also, has anyone tried this yet as an unsupported deployment, and if so, have they found any issues?

    "SQL Server 2014 is not yet supported for Project Server 2013", as per the article Hardware
    and software requirements for Project Server 2013: https://technet.microsoft.com/en-us/library/ee683978(v=office.15).aspx updated as on Dec
    09, 2014.
    Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading
    the thread.

  • Support for SQL Server 2014 for CMS + Audit Repository?

    We are currently on BusinessObjects 4.1 SP01 Patch 6 on Windows Server 2008 using SQL Server 2008 R2 for our CMS and Audit repository databases.  Is there any information out in regard to when SQL Server 2014 will be supported for the CMS and Audit repositories?
    According to the Product Availability Matrix shown in the screenshot below SQL Server 2012 is supported, right?  One of our DBAs claims there isn't that much of a difference between SQL Server 2012 and 2014, but I am not willing to try it if it isn't officially supported.
    Thanks,
    Noel

    Denis Konovalov  Henry Banks   James Rapp  Toby Johnston
    Need your attention here.

  • Any support for OneDrive like DropBox has for file link storage?

    Trying to add OneDrive to my File Link servers but no support for OneDrive yet. Any plans to add it to ThunderBird?

    Perhaps Microsoft will write an add-on as the community has done for dropbox.

  • Web Services support for collection like ArrayList

    Getting this error message:
    "<Info> Did not find property empty in java.util.ArrayList:
    java.lang.NullPointerException"
    Are collections like ArrayList supported or am I trying to do something that
    can't be done? Any suggestions?
    Thanks
    Danny

    Hi Danny,
    Betcha thought I forgot 'bout cha, huh?
    I didn't ;-)
    The short answer to your question is no; WLS 6.1 does not support using any of
    the classes in java.util.*. However, it does support Object arrays as an element
    of an Object array, which means you can have code in you service implementation
    that looks like this:
    public Object[] getNestedObjects()
         Object[] objects = new Object[2];
         objects[0] = new Object[]{
              new String("23.76"),
              new Float((float)23.76)
         // Here, WorkOrder is a JavaBean or an object
         // that implements weblogic.soap.xml.XMLizable
         WorkOrder[] workOrders = new WorkOrder[]{
                        new WorkOrder(),
                        new WorkOrder(),
                        new WorkOrder()
         objects[1] = new Object[]{
              new String("My name is"),
              new String("Slim Shady"),
              workOrders
         return objects;
    The main issue I see with doing this is again, interoperability ;-)
    If the SOAP toolkit consuming the WSDL for the web service with the above method
    cannot handle the "xsd:anyType" XML Schema data type, you're in trouble. In general,
    SOAP toolkits want to know what type an element is so they can process it correctly.
    When you use a Variant data type (in Visual Basic) or java.lang.Object (in Java),
    you are basically promoting the use of weak data typing (or late binding). From
    what I've read about SOAP (well, actually what Don Box said he had in mind), XML
    Schema and namespaces were adopted to combat this very thing- weak or no data
    typing. Personally, I agree ;-) I think strong data typing makes processing a
    SOAP request much easier and faster, for everyone. Don't get me wrong, I don't
    have anything against object casting, but SOAP parameters (and return values)
    are not objects. They are XML elements, just like the other parts of the SOAP
    message. There is no behavior, just state. This being the case, isn't it safer
    to stick with the data types (e.g. arrays, structures, primitives, etc.) defined
    in the SOAP spec and "XML Schema Part 2: Datatypes" document? Enough SOAP boxing
    (pun intended). If you are interested in the "complexTypes" object graphs (using
    developer defined classes that implement weblogic.soap.xml.XMLizable) lab results,
    I can send you a zip. The biggest difference between using JavaBeans and objects
    that implement weblogic.soap.xml.XMLizable, is that you have much more control
    over which Java objects the later gets serialized/deserialized to/from. With classes
    that implement weblogic.soap.xml.XMLizable, the SOAP processor passes you the
    actual XML stream for the SOAP parameter (which in this case, is your developer
    defined class). It (the SOAP processor) also calls your developer defined class
    to get an XML representation for it's data types. It works great with Java clients
    (using the client.jar, of course), and I'm trying it out with .NET and MS SOAP
    clients this weekend. The most interesting revelation was figuring out how wsgen
    (well, actually the WSDL processor) generates the information in the <types> element
    of the WSDL ;-) I actually even know how to code an XMLizable so that it produces
    the exact element and attribute names I want. I also figure out how to get it
    to produce an <element ...>, as opposed to a <attribute ...>, and visa versa.
    Of course, WLS 7.0 (and WebLogic Workshop) make all of this a moot point, but
    it was fun to get the SOAP/WSDL processors in WLS 6.1 to "do my bidding" for a
    short while ;-)
    Regards,
    Mike Wooten
    "Danny Ngo" <[email protected]> wrote:
    >
    Hi Mike,
    Thank you for your response. Do you know if WLS 6.1 Web Services support
    the
    return of nested object array (object that contains other object arrays).
    Thanks
    -Danny
    "Michael Wooten" <[email protected]> wrote:
    Hi Danny,
    For interoperability (with non-Java SOAP implementations)reasons, the
    Java collections
    are not supported in WLS 6.1 ;-) You should consider using an arrayin
    place of
    this.
    Regards,
    Mike Wooten
    Danny Ngo <[email protected]> wrote:
    Getting this error message:
    "<Info> Did not find property empty in java.util.ArrayList:
    java.lang.NullPointerException"
    Are collections like ArrayList supported or am I trying to do something
    that
    can't be done? Any suggestions?
    Thanks
    Danny

  • (BUG??) Team Foundation Server 2013 Update 4 Support for SQL 2014

    Scenario: On Windows 2012 R2 x64 I have installed SQL, Reporting Services & AS 2014 (applied all updates through Windows Update), SharePoint 2013 Foundation, and installed Team Foundation Server 2013 RTM (did not configure).
    Before configuring TFS, I applied Update 4 to the server (not update 1,2 or 3 directly). When trying to configure I get the following error:
    ==========================
    TF255146: Team Foundation Server requires SQL Server 2012 SP1 (11.00.3000) or greater. The SQL Server instance you supplied is version 12.0.2254.0.
    TF400403: The Report Server instance specified is version 12.0.2254.0, the minimum supported version is 11.0.3000.
    TF400070: A required version of a component is not installed on the application tier. You must exit the Team Foundation Administration Console and install a supported version of either SQL Server Analysis Services of the SQL Server Client Tools on the application
    tier to ensure that the Analysis Services object model is present for warehouse processing.
    ====================================
    My understanding is that as of Update 2 (or was it 3) that SQL 2014 was supported. However it appears if that particular update is not installed directly it bypasses the check. Can someone verify I am seeing the intended result or is this a bug?

    Hi Jazzy,  
    Thanks for your post.
    And thank you for sharing your experience here. It will be very beneficial for other community members having the similar questions.
    All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • TFS 2010 Support for SQL 2008 R2 SP3

    Does TFS 2010 support SP3 on SQL 2008 R2?
    Based on this link only SP2 is supported.
    http://msdn.microsoft.com/en-us/library/vstudio/dd631889%28v=vs.110%29.aspx
    Thanks

    Hi Aravind100,  
    Thanks for your post.
    As far as I know SQL Server 2008 R2 SP3 support TFS 2010. I think that document has not been updated after SQL Server 2008 R2 SP3 released.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Toplink support for SQL Server 2005 on Websphere 6.1

    Hi,
    We are using toplink in our application, it works fine when we use it with weblogic & SQL server or WAS 6.1 with Oracle or DB2. But when we use it with WAS 6.1 and SQL Server 2k5, it just does not work. It takes up all the connections in the pool and never returns it and starts giving connection time out errors.
    Internal Exception: com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 100005Error Code: 0
    Thanks

    This sounds like a WebSphere connection pool issue, I'm not sure why WebSphere would not work with SQL Server.
    You could try using TopLink's internal connection pooling instead.
    EclipseLink : http://www.eclipselink.org

  • Attunity SSIS connector support for Sql Server 2014?

    Hello,
    We've been successfully using Attunity SSIS connector 2.0 for a couple of years with SQL SERVER 2012.
    We developed some Visual Studio projects and deployed them on our SSISDB. Then launch them with scheduled jobs. Everything worked fine.
    After we upgraded the server to Sql Server 2014 the connector failed with the following error:
    The connection type "MSORA" specified for connection manager "XXX" is not recognized as a valid connection manager type.
    This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
    We tried uninstall/install but was no good. Also 32/64 bits combinations.
    We tried DTEXEC utility and worked fine on sqlserver 2012 folder ( \110\DTS\Binn) but didn't work on 2014's folder ( \120\DTS\Binn).
    We also tried a fresh 2014 installation but keep getting the same error.
    Does Attunity connector 2.0 support Sql Server 2014? If not, should I wait for a new version? Any workaround?
    For now, we are using the DTEXEC utility on 2012's folder, but since we have to use the /sql option (/ISSERVER is not working) we can't pass parameters to the .dtsx package.
    Any help would be much appreciated.
    Regards,
    Daniel

    I'm with Daniel - Microsoft should be taking the lead in resolving this. We downloaded the previous two versions from Microsoft Download (e.g. link below) with no indication that Microsoft would wash their hands of future support.
    http://www.microsoft.com/en-us/download/details.aspx?id=29283
    Attunity have replied on the thread on their forum - saying it is Microsoft's responsibility:
    http://www.attunity.com/forums/microsoft-ssis-oracle-connector/attunity-ssis-connector-support-sql-server-2963.html
    Trying to run, develop and support on parallel versions of SSIS is not a viable solution IMO.
    I will advise all my clients who use these connectors not to upgrade to SQL Server 2014 until this is resolved.

  • Support for SQL Server Compact 3.5

    Hello,
    we're using BI Publisher 10.1.3.4.1, some of our users need a connection to a SQL Server Compact 3.5.
    As I can't find this data source within the dropdown - is the Compact Edition of the SQL Server supported by the BI Publisher? Any experiences?
    Thank you,
    BR
    Lena

    Hi,
    I tried that, but I couldn't establish the connection...
    So I'm wondering whether this is due to the Server or the connection string.
    Any suggestions about how I can get more information about this?
    BR
    Lena

  • Support for DbXml specific functionality in XQuery vs. Shell or API

    Is / will there be any support for doing common commands in pure XQuery rather than just programmatically or through the shell? For example, in the shell I can create / list / delete indexes on a container, output query plans, etc. Are the same functions that are called through the shell available as XQuery functions? possibly in a dbxml function namespace?
    In a related question, but possibly deserving of a new thread if it doesn't already have one - I know XQuilla has the ability to call registered external functions from parsed XQuery, is there a way to tell DbXml to register a function with XQuilla's static context before using it? that would make it possible for me to add the functionality described above myself without disturbing your distributed code.

    Not so handy with C++ (my everday languages are PHP and Java), but if you say it can be done then I'll take a hack at it. If you happen to have examples of how other people have done it and you could point me at them it would be marvelous.
    To answer your second question: "bingo." It mostly means less interface work and brings it closer to what SQL can do in relational databases.
    The project allows the end user to define their own document structures (schema definitions more or less) and then create instances of these documents in a XML editing interface. For each document type, the end user is also able to define a set of named queries (abstracted function declarations) which lets us captures business rules without customizing our PHP code. Because the structure and queries that will be used against the documents are user defined its fairly impossible for me to automatically setup adequate indexes for the container of each set of documents. So I need an interface to allow the user to create / review / delete the indexes themselves.
    We've already created an interface that allows the user to execute arbitrary queries against a selected document. In the future we'd also like this same interface to do result set based content updates (through the XmlModify class) and whole document addition / replacement. So inclusion of index control makes sense as well. We can find ways to use the APIs, it just seems like this could benefit more than just our project.
    Placing the functionality from the shell into xquery extension functions seems analogous to having the UPDATE, DELETE and CREATE syntaxes of SQL.

  • Increase Performance and ROI for SQL Server Environments

    May 2015
    Explore
    The Buzz from Microsoft Ignite 2015
    NetApp was in full force at the recent Microsoft Ignite show in Chicago, talking about solutions for hybrid cloud, and our proven solutions for Microsoft SQL Server and other Microsoft applications.
    Hot topics at the NetApp booth included:
    OnCommand® Shift. A revolutionary technology that lets you move virtual machines back and forth between VMware and Hyper-V environments in minutes.
    Azure Site Recovery to NetApp Private Storage. Replicate on-premises SAN-based applications to NPS for disaster recovery in the Azure cloud.
    These tools give you greater flexibility for managing and protecting important business applications.
    Chris Lemmons
    Director, EIS Technical Marketing, NetApp
    If your organization runs databases such as Microsoft SQL Server and Oracle DB, you probably know that these vendors primarily license their products on a "per-core" basis. Microsoft recently switched to "per-core" rather than "per-socket" licensing for SQL Server 2012 and 2014. This change can have a big impact on the total cost of operating a database, especially as core counts on new servers continue to climb. It turns out that the right storage infrastructure can drive down database costs, increase productivity, and put your infrastructure back in balance.
    In many customer environments, NetApp has noticed that server CPU utilization is low—often on the order of just 20%. This is usually the result of I/O bottlenecks. Server cores have to sit and wait for I/O from hard disk drives (HDDs). We've been closely studying the impact of all-flash storage on SQL Server environments that use HDD-based storage systems. NetApp® All Flash FAS platform delivers world-class performance for SQL Server plus the storage efficiency, application integration, nondisruptive operations, and data protection of clustered Data ONTAP®, making it ideal for SQL Server environments.
    Tests show that All Flash FAS can drive up IOPS and database server CPU utilization by as much as 4x. And with a 95% reduction in latency, you can achieve this level of performance with half as many servers. This reduces the number of servers you need and the number of cores you have to license, driving down costs by 50% or more and paying back your investment in flash in as little as six months.
    Figure 1) NetApp All Flash FAS increases CPU utilization on your SQL Server database servers, lowering costs.
    Source: NetApp, 2015
    Whether you're running one of the newer versions of SQL Server or facing an upgrade of an earlier version, you can't afford not to take a second look at your storage environment.
    End of Support for Microsoft SQL Server 2005 is Rapidly Approaching
    Microsoft has set the end of extended support for SQL Server 2005 for April 2016—less than a year away. With support for Microsoft Windows 2003 ending in July 2015, time may already be running short.
    If you're running Windows Server 2003, new server hardware is almost certainly needed when you upgrade SQL Server. Evaluate your server and storage options now to get costs under control.
    Test Methodology
    To test the impact of flash on SQL Server performance, we replaced a legacy HDD-based storage system with an All Flash FAS AFF8080 EX. The legacy system was configured with almost 150 HDDs, a typical configuration for HDD storage supporting SQL Server. The AFF8080 EX used just 48 SSDs.
    Table 1) Components used in testing.
    Test Configuration Components
    Details
    SQL Server 2014 servers
    Fujitsu RX300
    Server operating system
    Microsoft Windows 2012 R2 Standard Edition
    SQL Server database version
    Microsoft SQL Server 2014 Enterprise Edition
    Processors per server
    2 6-core Xeon E5-2630 at 2.30 GHz
    Fibre channel network
    8Gb FC with multipathing
    Storage controller
    AFF8080 EX
    Data ONTAP version
    Clustered Data ONTAP® 8.3.1
    Drive number and type
    48 SSD
    Source: NetApp, 2015
    The test configuration consisted of 10 database servers connected through fibre channel to both the legacy storage system and the AFF8080 EX. Each of the 10 servers ran SQL Server 2014 Enterprise Edition.
    The publicly available HammerDB workload generator was used to drive an OLTP-like workload simultaneously from each of the 10 database servers to storage. We first directed the workload to the legacy storage array to establish a baseline, increasing the load to the point where read latency consistently exceeded 20ms.
    That workload was then directed at the AFF8080 EX. The change in storage resulted in an overall 20x reduction in read latency, a greater than 4x improvement in IOPS, and a greater than 4x improvement in database server CPU utilization.
    Figure 2) NetApp All Flash FAS increases IOPS and server CPU utilization and lowers latency.
    Source: NetApp, 2015
    In other words, the database servers are able to process four times as many IOPS with dramatically lower latency. CPU utilization goes up accordingly because the servers are processing 4x the work per unit time.
    The All Flash FAS system still had additional headroom under this load.
    Calculating the Savings
    Let's look at what this performance improvement means for the total cost of running SQL Server 2014 over a 3-year period. To do the analysis we used NetApp Realize, a storage modeling and financial analysis tool designed to help quantify the value of NetApp solutions and products. NetApp sales teams and partners use this tool to assist with return on investment (ROI) calculations.
    The calculation includes the cost of the AFF8080 EX, eliminates the costs associated with the existing storage system, and cuts the total number of database servers from 10 to five. This reduces SQL Server licensing costs by 50%. The same workload was run with five servers and achieved the same results. ROI analysis is summarized in Table 2.
    Table 2) ROI from replacing an HDD-based storage system with All Flash FAS, thereby cutting server and licensing costs in half.
    Value
    Analysis Results
    ROI
    65%
    Net present value (NPV)
    $950,000
    Payback period
    six months
    Total cost reduction
    More than $1 million saved over a 3-year analysis period compared to the legacy storage system
    Savings on power, space, and administration
    $40,000
    Additional savings due to nondisruptive operations benefits (not included in ROI)
    $90,000
    Source: NetApp, 2015
    The takeaway here is that you can replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs, with the majority of the savings derived from the reduction in SQL Server licensing costs.
    Replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs.
    Maximum SQL Server 2014 Performance
    In addition to the ROI analysis, we also measured the maximum performance of the AFF8080 EX with SQL Server 2014. A load-generation tool was used to simulate an industry-standard TPC-E OLTP workload against an SQL Server 2014 test configuration.
    A two-node AFF8080 EX achieved a maximum throughput of 322K IOPS at just over 1ms latency. For all points other than the maximum load point, latency was consistently under 1ms and remained under 0.8ms up to 180K IOPS.
    Data Reduction and Storage Efficiency
    In addition to performance testing, we looked at the overall storage efficiency savings of our SQL Server database implementation. The degree of compression that can be achieved is dependent on the actual data that is written and stored in the database. For this environment, inline compression was effective. Deduplication, as is often the case in database environments, provided little additional storage savings and was not enabled.
    For the test data used in the maximum performance test, we measured a compression ratio of 1.5:1. We also tested inline compression on a production SQL Server 2014 data set to further validate these results and saw a 1.8:1 compression ratio.
    Space-efficient NetApp Snapshot® copies provide additional storage efficiency benefits for database environments. Unlike snapshot methods that use copy-on-write, there is no performance penalty; unlike full mirror copies, NetApp Snapshot copies use storage space sparingly. Snapshot copies only consume a small amount of storage space for metadata and additional incremental space is consumed as block-level changes occur. In a typical real-world SQL Server deployment on NetApp storage, database volume Snapshot copies are made every two hours.
    First introduced more than 10 years ago, NetApp FlexClone® technology also plays an important role in SQL Server environments. Clones are fully writable, and, similar to Snapshot copies, only consume incremental storage capacity. With FlexClone, you can create as many copies of production data as you need for development and test, reporting, and so on. Cloning is a great way to support the development and test work needed when upgrading from an earlier version of SQL Server. You'll sometimes see these types of capabilities referred to as "copy data management."
    A Better Way to Run Enterprise Applications
    The performance benefits that all-flash storage can deliver for database environments are significant: more IOPS, lower latency, and an end to near-constant performance tuning.
    If you think the performance acceleration that comes with all-flash storage is cost prohibitive, think again. All Flash FAS doesn't just deliver a performance boost, it changes the economics of your operations, paying for itself with thousands in savings on licensing and server costs. In terms of dollars per IOPS, All Flash FAS is extremely economical relative to HDD.
    And, because All Flash FAS runs NetApp clustered Data ONTAP, it delivers the most complete environment to support SQL Server and all your enterprise applications with capabilities that include comprehensive storage efficiency, integrated data protection, and deep integration for your applications.
    For complete details on this testing look for NetApp TR-4303, which will be available in a few weeks. Stay tuned to Tech OnTap for more information as NetApp continues to run benchmarks with important server workloads including Oracle DB and server virtualization.
    Learn more about NetApp solutions for SQL Server and NetApp All-flash solutions.
    Quick Links
    Tech OnTap Community
    Archive
    PDF

    May 2015
    Explore
    The Buzz from Microsoft Ignite 2015
    NetApp was in full force at the recent Microsoft Ignite show in Chicago, talking about solutions for hybrid cloud, and our proven solutions for Microsoft SQL Server and other Microsoft applications.
    Hot topics at the NetApp booth included:
    OnCommand® Shift. A revolutionary technology that lets you move virtual machines back and forth between VMware and Hyper-V environments in minutes.
    Azure Site Recovery to NetApp Private Storage. Replicate on-premises SAN-based applications to NPS for disaster recovery in the Azure cloud.
    These tools give you greater flexibility for managing and protecting important business applications.
    Chris Lemmons
    Director, EIS Technical Marketing, NetApp
    If your organization runs databases such as Microsoft SQL Server and Oracle DB, you probably know that these vendors primarily license their products on a "per-core" basis. Microsoft recently switched to "per-core" rather than "per-socket" licensing for SQL Server 2012 and 2014. This change can have a big impact on the total cost of operating a database, especially as core counts on new servers continue to climb. It turns out that the right storage infrastructure can drive down database costs, increase productivity, and put your infrastructure back in balance.
    In many customer environments, NetApp has noticed that server CPU utilization is low—often on the order of just 20%. This is usually the result of I/O bottlenecks. Server cores have to sit and wait for I/O from hard disk drives (HDDs). We've been closely studying the impact of all-flash storage on SQL Server environments that use HDD-based storage systems. NetApp® All Flash FAS platform delivers world-class performance for SQL Server plus the storage efficiency, application integration, nondisruptive operations, and data protection of clustered Data ONTAP®, making it ideal for SQL Server environments.
    Tests show that All Flash FAS can drive up IOPS and database server CPU utilization by as much as 4x. And with a 95% reduction in latency, you can achieve this level of performance with half as many servers. This reduces the number of servers you need and the number of cores you have to license, driving down costs by 50% or more and paying back your investment in flash in as little as six months.
    Figure 1) NetApp All Flash FAS increases CPU utilization on your SQL Server database servers, lowering costs.
    Source: NetApp, 2015
    Whether you're running one of the newer versions of SQL Server or facing an upgrade of an earlier version, you can't afford not to take a second look at your storage environment.
    End of Support for Microsoft SQL Server 2005 is Rapidly Approaching
    Microsoft has set the end of extended support for SQL Server 2005 for April 2016—less than a year away. With support for Microsoft Windows 2003 ending in July 2015, time may already be running short.
    If you're running Windows Server 2003, new server hardware is almost certainly needed when you upgrade SQL Server. Evaluate your server and storage options now to get costs under control.
    Test Methodology
    To test the impact of flash on SQL Server performance, we replaced a legacy HDD-based storage system with an All Flash FAS AFF8080 EX. The legacy system was configured with almost 150 HDDs, a typical configuration for HDD storage supporting SQL Server. The AFF8080 EX used just 48 SSDs.
    Table 1) Components used in testing.
    Test Configuration Components
    Details
    SQL Server 2014 servers
    Fujitsu RX300
    Server operating system
    Microsoft Windows 2012 R2 Standard Edition
    SQL Server database version
    Microsoft SQL Server 2014 Enterprise Edition
    Processors per server
    2 6-core Xeon E5-2630 at 2.30 GHz
    Fibre channel network
    8Gb FC with multipathing
    Storage controller
    AFF8080 EX
    Data ONTAP version
    Clustered Data ONTAP® 8.3.1
    Drive number and type
    48 SSD
    Source: NetApp, 2015
    The test configuration consisted of 10 database servers connected through fibre channel to both the legacy storage system and the AFF8080 EX. Each of the 10 servers ran SQL Server 2014 Enterprise Edition.
    The publicly available HammerDB workload generator was used to drive an OLTP-like workload simultaneously from each of the 10 database servers to storage. We first directed the workload to the legacy storage array to establish a baseline, increasing the load to the point where read latency consistently exceeded 20ms.
    That workload was then directed at the AFF8080 EX. The change in storage resulted in an overall 20x reduction in read latency, a greater than 4x improvement in IOPS, and a greater than 4x improvement in database server CPU utilization.
    Figure 2) NetApp All Flash FAS increases IOPS and server CPU utilization and lowers latency.
    Source: NetApp, 2015
    In other words, the database servers are able to process four times as many IOPS with dramatically lower latency. CPU utilization goes up accordingly because the servers are processing 4x the work per unit time.
    The All Flash FAS system still had additional headroom under this load.
    Calculating the Savings
    Let's look at what this performance improvement means for the total cost of running SQL Server 2014 over a 3-year period. To do the analysis we used NetApp Realize, a storage modeling and financial analysis tool designed to help quantify the value of NetApp solutions and products. NetApp sales teams and partners use this tool to assist with return on investment (ROI) calculations.
    The calculation includes the cost of the AFF8080 EX, eliminates the costs associated with the existing storage system, and cuts the total number of database servers from 10 to five. This reduces SQL Server licensing costs by 50%. The same workload was run with five servers and achieved the same results. ROI analysis is summarized in Table 2.
    Table 2) ROI from replacing an HDD-based storage system with All Flash FAS, thereby cutting server and licensing costs in half.
    Value
    Analysis Results
    ROI
    65%
    Net present value (NPV)
    $950,000
    Payback period
    six months
    Total cost reduction
    More than $1 million saved over a 3-year analysis period compared to the legacy storage system
    Savings on power, space, and administration
    $40,000
    Additional savings due to nondisruptive operations benefits (not included in ROI)
    $90,000
    Source: NetApp, 2015
    The takeaway here is that you can replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs, with the majority of the savings derived from the reduction in SQL Server licensing costs.
    Replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs.
    Maximum SQL Server 2014 Performance
    In addition to the ROI analysis, we also measured the maximum performance of the AFF8080 EX with SQL Server 2014. A load-generation tool was used to simulate an industry-standard TPC-E OLTP workload against an SQL Server 2014 test configuration.
    A two-node AFF8080 EX achieved a maximum throughput of 322K IOPS at just over 1ms latency. For all points other than the maximum load point, latency was consistently under 1ms and remained under 0.8ms up to 180K IOPS.
    Data Reduction and Storage Efficiency
    In addition to performance testing, we looked at the overall storage efficiency savings of our SQL Server database implementation. The degree of compression that can be achieved is dependent on the actual data that is written and stored in the database. For this environment, inline compression was effective. Deduplication, as is often the case in database environments, provided little additional storage savings and was not enabled.
    For the test data used in the maximum performance test, we measured a compression ratio of 1.5:1. We also tested inline compression on a production SQL Server 2014 data set to further validate these results and saw a 1.8:1 compression ratio.
    Space-efficient NetApp Snapshot® copies provide additional storage efficiency benefits for database environments. Unlike snapshot methods that use copy-on-write, there is no performance penalty; unlike full mirror copies, NetApp Snapshot copies use storage space sparingly. Snapshot copies only consume a small amount of storage space for metadata and additional incremental space is consumed as block-level changes occur. In a typical real-world SQL Server deployment on NetApp storage, database volume Snapshot copies are made every two hours.
    First introduced more than 10 years ago, NetApp FlexClone® technology also plays an important role in SQL Server environments. Clones are fully writable, and, similar to Snapshot copies, only consume incremental storage capacity. With FlexClone, you can create as many copies of production data as you need for development and test, reporting, and so on. Cloning is a great way to support the development and test work needed when upgrading from an earlier version of SQL Server. You'll sometimes see these types of capabilities referred to as "copy data management."
    A Better Way to Run Enterprise Applications
    The performance benefits that all-flash storage can deliver for database environments are significant: more IOPS, lower latency, and an end to near-constant performance tuning.
    If you think the performance acceleration that comes with all-flash storage is cost prohibitive, think again. All Flash FAS doesn't just deliver a performance boost, it changes the economics of your operations, paying for itself with thousands in savings on licensing and server costs. In terms of dollars per IOPS, All Flash FAS is extremely economical relative to HDD.
    And, because All Flash FAS runs NetApp clustered Data ONTAP, it delivers the most complete environment to support SQL Server and all your enterprise applications with capabilities that include comprehensive storage efficiency, integrated data protection, and deep integration for your applications.
    For complete details on this testing look for NetApp TR-4303, which will be available in a few weeks. Stay tuned to Tech OnTap for more information as NetApp continues to run benchmarks with important server workloads including Oracle DB and server virtualization.
    Learn more about NetApp solutions for SQL Server and NetApp All-flash solutions.
    Quick Links
    Tech OnTap Community
    Archive
    PDF

Maybe you are looking for