SQL Server PDW Test Emulator ?

Hi All,
I work on IBM Netezza in my work place now want to try out SQL Server PDW to test its performance and new polybase functionality.
Is there any SQL Server PDW emulator for developers to test or learn new techniques same as IBM Netezza ?
https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=266888e9-4b4b-44cd-bd51-e32d05da9143
Sri.Tummala

Not that I know of... If you're serious about testing PDW's capabilities speak to Microsoft who would be more than happy to help setup an appliance.

Similar Messages

Using SQLCMD variables in SQL Server Unit Test Project

Is it possible to use SQLCMD variables in my SQL Server Unit Test Project? In my test initialize script I'd like to set a database name variable, something like this:
:SETVAR MyDatabase "mydatabase"
SELECT * FROM [$(MyDatabase)].[mytable]
but I get syntax errors when I run the test. Any suggestions how I can get this to work.
Result Message: Initialization method
myTest.TestInitialize threw exception. System.Data.SqlClient.SqlException: System.Data.SqlClient.SqlException:
Incorrect syntax near ':'..

Hi Kevin,
What is the error?
This should work only thing i could see is no scheme specified.
SQL Server uses dbo as default schema.
In your case:
:SETVAR MyDatabase "mydatabase"
SELECT * FROM [$(MyDatabase)].dbo.[mytable]
Also check your instance collation if its Case sensitive then specify database and table name as exact case.
Example:
:SETVAR MyDatabase "[mydatabase]"
:setvar schemavar "[dbo]"
:setvar tablevar "[mytable]"
SELECT * FROM $(MyDatabase).$(schemavar).$(tablevar)

SQL Server Unit Tests

Hi SQL Server Experts,
About SQL Server Unit Tests (vide
http://msdn.microsoft.com/en-us/library/jj851203(v=vs.103).aspx), please help with inputs on pros and cons of SQL Server Unit Tests. Any ideal recommendation?
Thanks

Blog on the topic: "Database unit testing is used for feature testing of your individual modules (stored procedures, triggers or user defined functions) that is to say your module performs as expected. Apart from that, it is also used to ensure that
subsequent changes to the module does not break any functionality.
At first glace, it looks like this would add overhead to create vs. doing adhoc testing, but Visual Studio lets you automatically generate T-SQL code stubs to test the database object which you can customize as per your need.
Visual Studio provides Database Unit Test Designer which you can write/define T-SQL scripts (also insert SQL assertion in this code) that calls your module and then evaluates the execution result against the different test conditions which indicates your
modules execution success or failure."
LINK:
SQL Server Unit Testing with Visual Studio 2010
>Please pardon my ignorance as I am coming back to SQL Server after a brief gap.
You may have to brush up with T-SQL prior to using a sophisticated tool like this:
http://www.sqlusa.com/bestpractices/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Server PDW(Parallel Data Warehouse)

Dear,
There are several features which are unsupported at SQL Server PDW(Parallel Data Warehouse) version.
Such as
UDF(User Defined Function) / Extended Stored Procedure, CLR / Cursor / Trigger /
@@SPID, @@SNAME_SUSER so on.
I'm wondering when these features will be supported.
Would you let me know approximate target date or road map?
Thanks, Jungwon

As far as I can tell , these features do not exist because the appliance purpose is to limit any components that can introduce a chance of performance degradation such as CLR and extended stored procedures beside also focusing on the core features for now.
The word in the street is you have have your own CLR code in a business layer while PDW is for mass data analytics.
for something like @@SPID , you should use the management web console & DMVs where they provides more rich information
HTH
Please click Vote As Helpful , Propose As Answer and/or Mark As Answer
if you think this post helps!

SSDT: Creation of localDB instances from project file - Sql Server Unit testing purposes

I have a SqlServer Database Project in my solution (VS2013 Professional) which has a corresponding test project with some stored procedure unit tests. Currently I am using a LocalDB and as far as I understand a local database instance is created in C:\Users\[User]\AppData\Local\Microsoft\Microsoft
SQL Server Local DB\Instances\Projects and the specific .mdf file referenced in the SQL Server Object Explorer is in C:\Users\[User]\AppData\Local\Microsoft\VisualStudio\SSDT\[ProjectName]. The unit tests run fine on my local machine which I have developed
the project on.
My issue is we have a box which is configured to check out the project file from our version control, build the project using ms build commands and then run the unit tests using VSTest.Console. Usually with C# Test projects we reference the test project
dll and the unit tests run fine. I have referenced the dll for the test project with the stored procedure unit tests in.
With the Stored Procedure unit tests however we get this exception:
Initialization method [project].[spTest].TestInitialize threw exception. System.Data.SqlClient.SqlException: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. The specified LocalDB instance does not exist.
After some digging I have realised that the localdb instance seems to be created when the project itself is created in VS not when it is built. Specifically when the localdb is first used and if you look into the appData folder of the test machine there
is no corresponding mdf file for the project.
The question is is there a way to set up a localDB instance on the new machine if all you have the project file? The only purpose of the project on the test machine is to run the unit tests, no other development purposes. VS2013 Professional is installed
on the test machine but a solution only using config file changes or MSBuild/VSTest commands would be preferable.
I realise you could change the connection string to an actual test database and run the unit tests of that but we quite like the localdb approach for the testing. I also realise that you could potentially transfer the mdf file (haven't tested this solution)
as well, though I would prefer if there is a solution to my initial question.
http://technet.microsoft.com/en-us/library/hh234692.aspx
http://msdn.microsoft.com/en-us/library/hh309441(v=vs.110).aspx
I have been reading up on LocalDB and I assume a automatic LocalDB is created when you create a sql server database project (ie on localdb first use). I have tried adding the database creation to the test project config file but do not really know where
to go from there. The second link does not really specify when the named localdb will be created if you add the config items and I am not even sure if that is an actual solution. Here's my test project config file for reference
<configSections>
<section name="system.data.localdb" type="System.Data.LocalDBConfigurationSection,System.Data,Version=4.0.0.0,Culture=neutral,PublicKeyToken=[PublicKeyToken]"/>
<section name="SqlUnitTesting_VS2013" type="Microsoft.Data.Tools.Schema.Sql.UnitTesting.Configuration.SqlUnitTestingSection, Microsoft.Data.Tools.Schema.Sql.UnitTesting, Version=12.0.0.0, Culture=neutral, PublicKeyToken=[PublicKeyToken]" />
</configSections>
<system.data.localdb>
<localdbinstances>
<add name="SimpleUnitTestingDB" version="11.0" />
</localdbinstances>
</system.data.localdb>
<SqlUnitTesting_VS2013>
<DatabaseDeployment DatabaseProjectFileName="..\..\..\SimpleUnitTestDB\SimpleUnitTestDB.sqlproj"
Configuration="Release" />
<DataGeneration ClearDatabase="true" />
<ExecutionContext Provider="System.Data.SqlClient" ConnectionString="Data Source=(localdb)\Projects;Initial Catalog=SimpleUnitTestDB;Integrated Security=True;Pooling=False;Connect Timeout=30"
CommandTimeout="30" />
<PrivilegedContext Provider="System.Data.SqlClient" ConnectionString="Data Source=(localdb)\Projects;Initial Catalog=SimpleUnitTestDB;Integrated Security=True;Pooling=False;Connect Timeout=30"
CommandTimeout="30" />
</SqlUnitTesting_VS2013>
Thanks in advance for any response. Sorry if there is any misunderstanding, while I have been using VS to develop from the start, this is the first time I have used a Sql Server Database Project.
Regards,
Christopher.

Yes, you can create a LocalDB instance manually. You use the SqlLocalDb utility, see here:
http://technet.microsoft.com/en-us/library/hh212961.aspx
Erland Sommarskog, SQL Server MVP, [email protected]

Sql server admin test 70-462

Hello, I was involved with SQL Server back in the SQL 7 days. I have received some good info about how to get back into it. I would like to study and take the sql 2012 admin test 70-462 (I have not seen a test for sql 2014). I was looking at the sample
tests on the Trancender web site and was shocked at the prices (download plus bonus online $139 for 118 practice questions). Is there anyway to get questions free? I would like to look at a good sample test so that I would know what to study.
Is there a good book or PDF that would cover the requisite material for the test?

Hello,
Try video resources available at Channel 9.
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/EXM16
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrating from SQL Server to Oracle - Emulating SQL Server databases

I want to offer Oracle connectivity from an ADO.NET application that was developed for SQL Server. The application accesses multiple databases, each having the same schema but each storing different data that is confidential to the users of each database. I’ve been reading up on Oracle but have not yet found a way to group tables, views, etc. in a way that would emulate the ‘databases’ of SQL Server.
The application currently uses the SQL ‘CREATE DATABASE’ command to generate each database and then populates each with the appropriate tables. However, CREATE DATABASE appears to work differently with Oracle, creating a new instance rather than a new ‘internal database’. I’m wondering if CREATE TABLESPACE would give me the functionality I’m looking for, if it were subsequently possible to refer to a specific table within a specific tablespace.
I guess it comes down to whether it’s possible to access specific groups of tables, views, etc. within Oracle (e.g. Groups A, B and C, each having relational tables T1, T2 and T3, and be able to access and update data within any specific table, say, B-T2), while also being able to limit access to any of the Groups.
Would ODP.Net offer advantages over the System.Data.OracleClient for this architectural problem?
Any thoughts on how best to proceed would be most welcome. Thanks in advance for any ideas you might have.

Sorry for the delay closing-out this thread but I work from a rural location and we lost our internet service for the two-weeks prior to the holidays. Now back on-line so let's wrap-up.
Oracle and SQLServer are now both being accessed from my ADO.Net application, so a big thanks to all who've helped me with this first use of the forum. Hopefully these final comments might help someone else in turn...
In migrating from SQLServer to Oracle I initially found it hard to stop thinking about accessing multiple databases on a single dataserver and start thinking more about a single instance of a database that supports muliple users, any one of which can be assigned the same schema. While I had used the SQL CREATE command to produce miltiple databases within SQLServer, it serves a completely different purpose for Oracle, creating an entirely new instance that I did not require.
Other differences that I ran in to included Oracle utilizing 'sequences' to autoincrement identities, whereas SQLServer lets you specify the identify while creating a table (here SQLServer may simplify declaration but Oracle's approach may be more powerful, e.g. if the same identity applies across multiple tables). Also ADO.NET command parameters use an '@' prefix in SQLServer but ':' for Oracle. But by-and-large few changes were required to my SQL to get up and running with Oracle (I found the 'Oracle Database SQL Reference' useful but no substitute for logging into Oracle and just trying each string in the 'SQL Commands' area).
Clearly I'm no database expert and I've barely scratched the surface with Oracle, but after logging in through the 'Database Home Page' I've found Oracle to offer a very 'clean' and logical interface that made it easy to move around the application and get a 'feel' for its organization and what it can do before digging furhter into the documentation. The 'Object Browser' is also a great way to quickly view and edit your various tables, views, sequences, triggers, etc., and ditto your data. In short, I think I'm going to like Oracle.
Thanks again and bye for now.

SQL SErver PDW on anything but HP?

When I go to the MS web site for PDW, it shows all kinds of partners. But if you go and Google search, HP seems to be the only one playing here? I went to Dell site, nothing. Called Dell, had no idea. They all talk about Fast Track, but we are looking
at pitting PDW H/W vendors against each other and seeing who offers the best value. Am I missing something?

Hi LearningDBA,
HP only at this stage
The Dell model is coming but will have a slightly different look to it, 8 servers per rack instead of 10 beasue their disk arrays are 3U, not 2U
Hope this helps.
Peter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/

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

SETUP ERROR WHILE INSTALLING SQL SERVER 2008 R2

Hi ,
I'm coming across the following error while installing Microsoft SQL Server 2008R2
SQL Server Setup has encountered the following error:
The required MSI package 'D:\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
Error code 0x84B20001.
I tried reinstalling the same. But results the same.
Please suggest. :)

Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068709375
Exit facility code:            1202
Exit error code:               1
Exit message:                  The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi'
doesn't exist.
Start time:                    2013-12-31 20:47:50
End time:                      2013-12-31 20:55:44
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xD2FD83B3%400xC2B0B50B%401202%401
Machine Properties:
Machine name:                  SAMPLE-PC
Machine processor count:       2
OS version:                    Windows 7
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x86
Process architecture:          32 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Sql Server 2005
Tools                                    1033
Express Edition      9.2.3042        No
Sql Server 2005
ToolsClient                              1033
Express Edition      9.2.3042        No
Sql Server 2005
ToolsClient\Connectivity                 1033                 Express Edition
9.2.3042        No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication
1033                 Express Edition      10.1.2531.0     No
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\
Installation edition:          DEVELOPER
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 TEST
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Config
ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  TEST
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            SAMPLE-PC\SAMPLE
ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Automatic
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    TEST
INSTANCENAME:                  TEST
ISSVCACCOUNT:                  TEST
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 DefaultNativeMode
RSSVCACCOUNT:                  SAMPLE-PC\TEST
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 TEST
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           SAMPLE-PC\SAMPLE
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Analysis Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException
    Message:
        The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
    Data:
      ChainerInvalidOperationExceptionData = InstallPackage
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
        at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
        at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)

Linking to SQL Server from Oracle 10g on 64bit Linux

I have this working, so I thought I would post my steps.
In versions 8 to 10 of Oracle, the software for making these connections was known as Heterogeneous Services. It was 32bit only software and the actual binary file that was executed when querying a non oracle database was $ORACLE_HOME/bin/hsodbc. When a query was made to the linked database, a process was started on the machine with the name of hsodbcXXX (where XXX is the name of the DSN).
In version 11g of Oracle this software is now referred to as Database Gateways and there is a 64bit version as well as a 32bit version. The binary file that is executed in this case is $ORACLE_HOME/bin/dg4odbc.
Fortunately the 64bit Database Gateway software can also be used with Oracle 10g databases as long as it is up to version 10.2.03 and has the odbc compatibility patch installed. (5965763).
To make use of this, we need to install the 11g ODBC Gateway into a separate ORACLE_HOME and start a listener from that environment. We can then make use of that listener from the 10g environment.
So here is what I did to get this working: (Note: DSN = MyDSN)
1.     Download and install 64bit ODBC driver with support for 64-bit ULEN from Easysoft. The file is named odbc-sqlserver-1.1.4-linux-x86-64-ul64.tar. You'll need to email Easysoft support for the URL. Create the DSN entry as part of the install. At the end of the process it can test the DSN. The query should come back with info about the SQL Server. Test the connection using isql from the /opt/easysoft/unixODBC/bin directory to verify that it works as well (/opt/easysoft/unixODBC/bin/isql –v MyDSN). Note, I installed easysoft driver under /opt rather than the /usr/local which is the default. /usr/local/easysoft is a symlink to /opt/easysoft.
2.     Install ODBC gateway via the 11g Gateways installer. You can do a custom install and deselect all but the ODBC Gateway component. (http://download.oracle.com/otn/linux/oracle11g/linux.x64_11gR1_gateways.zip)
3.     Create a /home/oracle/11g_environment.sh script that sets 11g ORACLE_HOME, PATH, and LD_LIBRARY_PATH variables. It should look something like this:
#set ORACLE ENV vars for 11g
ORACLE_HOME=/u01/app/oracle/product/11.1.0/tg_1 # (assuming that is where ODBC Gateway was installed)
PATH=/bin:/usr/bin:/u01/app/oracle/product/11.1.0/tg_1/bin:/opt/easysoft/bin:/opt/easysoft/unixODBC/bin
LD_LIBRARY_PATH=/opt/easysoft/lib:/opt/easysoft/unixODBC/lib:/u01/app/oracle/product/11.1.0/tg_1/lib
export ORACLE_HOME
export PATH
export LD_LIBRARY_PATH
4.     Create $ORACLE_HOME/hs/admin/initMyDSN.ora, $ORACLE_HOME/network/admin/listener.ora, and $ORACLE_HOME/network/admin/tnsnames.ora under 11g structure. They are as follows:
initMyDSN.ora:
# This is a sample agent init file that contains the HS parameters that are
# needed for an ODBC Agent.
# HS init parameters
HS_FDS_CONNECT_INFO=MyDSN
HS_FDS_TRACE_LEVEL=0
HS_FDS_TRACE_FILE_NAME=MyDSN.trc
HS_FDS_SHAREABLE_NAME=/opt/easysoft/unixODBC/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
# ODBC specific environment variables
#set ODBCINI=/etc/odbc.ini
#set ODBCINSTINI=/etc/odbcinst.ini
#set LD_LIBRARY_PATH=/opt/easysoft/lib:/opt/easysoft/unixODBC/lib:/u01/app/oracle/product/11.1.0/lib
#set PATH=$PATH:/opt/easysoft/unixODBC/bin:/opt/easysoft/bin/
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
listener.ora
MyDSN =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1522))
SID_LIST_MyDSN =
(SID_LIST =
(SID_DESC=
(SID_NAME=MyDSN)
(ORACLE_HOME = /u01/app/oracle/product/11.1.0/tg_1)
(PROGRAM=dg4odbc)
(ENVS=LD_LIBRARY_PATH=/opt/easysoft/lib:/opt/easysoft/unixODBC/lib:/u01/app/oracle/product/11.1.0/tg_1/lib)
tnsnames.ora
# tnsnames.ora Network Configuration File:
# Generated by Oracle configuration tools.
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
MyDSN =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST=localhost)(PORT=1522))
(CONNECT_DATA=(SID=MyDSN))
(HS=OK)
5.     Add another entry for MyDSN in /u01/app/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora so tnsping works in 10g environment as well.
MyDSN =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST=localhost)(PORT=1522))
(CONNECT_DATA=(SID=MyDSN))
(HS=OK)
*** Notice that the MyDSN listener runs on a different port (1522) as it is a separate listener.
6.     Login to machine as user oracle and source the 11g environment script. “source ~/11g_environment.sh”. Now start the listener. “cd $ORACLE_HOME/bin”. “./lsnrctl start MyDSN”.
7.     Login to a new shell as user oracle with a 10g environment.
8.     Run sqlplus and create the database link. “CREATE PUBLIC DATABASE LINK SQLSERVER connect to “<someuser>” IDENTIFIED BY “<somepass>” USING ‘MyDSN’;”
9.     test the link. “select * from information_schema.tables@SQLSERVER;”
If it is successfull, you should see a system process named "dg4odbcMyDSN".

So what have you found out for yourself so far (considering the solution to this is easily found on the web)?
Have you looked up Heterogeneous Services?

SQL Server 2000 connectivity probs

hi frnds
i wanna do the database connectivity with Microsoft SQL Server 2000 and for this i got the driver from the site of Microsoft ,named Microsoft SQL Server 2000 JDBC Driver .
But on testing this driver i am getting the following errors which shows the compiler isnt getting the driver class for connectivity..please do guide me about this...what can be the possible solution.
Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at Main.main(Main.java:21)
please reply ASAP
thanks n regards
Melinda

no i am not calling the createStatement.
this is the code i am using to test the driver
import java.sql.*;
* Microsoft SQL Server JDBC test program
public class Main {
public static void main (String args[]) throws Exception {
// Get connection
//DriverManager.registerDriver(new
// com.microsoft.jdbc.sqlserver.SQLServerDriver());
Driver d = (Driver)Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver://local:1433","sa","sa");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
n this is the error that i m getting now
Exception in thread "main" java.lang.ClassNotFoundException: com.microsoft.jdbc.
sqlserver.SQLServerDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at Main.main(Main.java:18)

Java - SQL Server 2000 Connectivity

hi all. i m looking for help in Java - SQL Server 2000 Connectivity.i worked on Java- Oracle & Java - MS Access format.now i m looking to work on Java - SQL Server 2000. I m using JBuilder 2005. can any1 help me how to make any change(configuration) in my SQL Server.thanx in advance.

http://www.jguru.com/forums/JBuilder is hopeless. ihvn;t get good replies from them.i downloaded the JDBC driver from microsoft and added the JAR files (3 files) and tried the following code:
import java.sql.*;
* Microsoft SQL Server JDBC test program
public class Test {
public Test() throws Exception {
// Get connection
DriverManager.registerDriver(new com.microsoft.jdbc.sqlserver.SQLServerDriver());
//Connection connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://<Host>:1433",<"UID>","<PWD>");
// Connection connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://GMC01:1433;DatabaseName=MoonDB");
Connection connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://Moon:1433;DatabaseName=MoonDB");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
} // Test
public static void main (String args[]) throws Exception {
Test test = new Test();
it run without any error and then showed fatal exception as below:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
     at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
     at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:193)
     at Test.<init>(Test.java:11)
     at Test.main(Test.java:31)
Exception in thread "main"
where's the problem?can any1 try to solve this plz.

Custom adaptor error??? in SQL Server

When i work on Custom Adaptor for Ms. SQL Server, i am not able to configure sucess fully, i am giving the following parameter???
Host Name --- Server HostName --- my Windows 2003 Server Name or i used localhost because SQL Server is Installed on Same OS/Maschine
TCP-PORT --- 1433
User Name --- Windows Authentication User Name or id MS SQL Server is with out Authentication mode then no need to user name and password
Password --- *********
JDBC Driver --- com.microsoft.sqlserver.jdbc.SQLServerDriver ( I have all the three driver i.e msbase.jar / mssqlserver.jar / msutil.jar ( Because i am using MS SQL
Server 2000 on Service Pack 1 or 2003 Windows Server
JDBC URL Template ---- jdbc:sqlserver://imserver1:1433/master.mdf ( Host Name - IMSERVER1: Port Number / 1433 , Database Name ( currently i am using one test Databasein MS Sql Server for Test Purpose that i have created manually)
When i test the configuration it will show this error
Test connection failed for resource(s):
MSSQLServer: ==> java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
**ERRORS**
XPRESS <invoke> exception:
Can't call method listDatabaseNames on class com.waveset.ui.web.resources.wizard.SQLServerUtil ==> com.waveset.util.WavesetException: ==> java.sql.SQLException: No suitable driver found for jdbc:sqlserver://imserver1:1433/idmtest_Data.mdf
XPRESS <invoke> exception:
Can't call method listDatabaseNames on class com.waveset.ui.web.resources.wizard.SQLServerUtil ==> com.waveset.util.WavesetException: ==> java.sql.SQLException: No suitable driver found for jdbc:sqlserver://imserver1:1433/idmtest_Data.mdf
XPRESS <invoke> exception:
Can't call method listDatabaseNames on class com.waveset.ui.web.resources.wizard.SQLServerUtil ==> com.waveset.util.WavesetException: ==> java.sql.SQLException: No suitable driver found for jdbc:sqlserver://imserver1:1433/idmtest_Data.mdf
please reply if you have face the same solution and you have got the answer??????
will thankfull

Hi,
java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver that error means it does not find the classes for microsoft jdbc in the classpath of the idm webapp.
copy the microsoft jdbc driver jar (e.g. sqljdbc.jar) to the WEB-INF/lib folder of your application servers webapp directory. for example:
/tomcat/webapps/idm/WEB-INF/lib

JDBC Connection between Unix and SQL Server 2000

I have SQL Server 2000 installed in a pc as a data server and SQL Server 2000 JDBC Drive installed in a Unix machine. Both machines are connected and can ping each other. After setting up the environment data, I ran a test code to test the connection and got exceptions. ( I did the same process between a pc and the data server, it works well.)
Attached are the test code and error message. Hope someone can help me.
******* Test Code ********
import java.sql.*;
* Microsoft SQL Server JDBC test program
public class Test {
public Test() throws Exception {
// Get connection
DriverManager.registerDriver(new
com.microsoft.jdbc.sqlserver.SQLServerDriver());
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver://<hostname>","<username>","<password>");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
} // Test
public static void main (String args[]) throws Exception {
Test test = new Test();
******* error message ********
Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(SQLException.java:64)
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:137)
at Test.<init>(Test.java:10)
at Test.main(Test.java:32)
************ end of message ***********

If it works from a PC and not from the Unix box then you may have a network issue of some sort, I.E. firewall not letting it through etc.
Try using telnet on the Unix box to see if you can connect to the sql server on the port that the SQL server is listening.
E.G.
telnet server_name 1433
You may need to change the port number to the one that the SQL server is using.
Col

SQL Server PDW Test Emulator ?

Similar Messages

Maybe you are looking for