Showing posts with label SQL Server 2005. Show all posts
Showing posts with label SQL Server 2005. Show all posts

SQL Server 2005 Jdbc connection|MSSQL 2005 -JDBC Connection

Connecting to a version of MS SQL post 2000 requires a few extra pieces of knowledge these days.
  • By default MS SQL does not listen on anyTCP/IP socket. You have to go to MS SQL configuration manager console and enable tcp/ip for the instance under Network Configuration. You need to restart SQL for this to take effect. It also appears that enabling TCP/IP does not enable it on a specific ip address. I had to set the specific ip address under "SQL Server 2005 Network Configuration"=>TCP/IP Protocol=>(right click) Properties=>IP Addresses to enabled = yes.
  • Instances do not run on port 1433 anymore. They use dynamic ports. If you right click on the tcp/ip protocol for your instance under "SQL Server 2005 Network Configuration" you should be able to force this to change by changing the setting on the "IP Addresses "tab but this didn't work for me.You can pick up the dynamic port it is using with netstat or from the "IP Addesses" tab. Since it is a dev environment I didn't care much as long as I could connect.
  • Don't foget to allow the windows firewall to let external request to the port through.

Differences between SQL Server 2005 and SQL Server Express

Question:
VS 2005 Professional comes with SQL Server 2005 Developer Edition, I'm wondering if I install the Developer Edition, does that mean I don't need to install the Express Edition?

What is the difference between SQL Server 2005 Express Edition and SQL Server 2005 Developer Edition?

Answer:
Developer edition is basiclly Enterprise which can be installed on XP Pro SP2 (has a few limits like memory and CPU.  and of course limited on the license to development / test environments).

Express is a cut down version of SQL Server. Like MSDB was for 2000.

If you install Developer you don't need Express,  on my machine at work I have 2000, Express and 2005 but thats because VS 2005 installed express for me.  Should really turn off the service, but i keep forgetting.

Even tho Developer edition isn't listed on the site, keep in mine it is closer to Enterprise than any of the others.


http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx


Answer 2:
I work with a firm that has a product that runs on Access FE (forms/reports) and SQL 2000/2005 BE (sp's, views, tables), and am still in the learning process on the SQL side.  I don't dare ask if they will let me install their license on my machine, but considering to ask if I can install their Developer 2005 version.  They are a "Microsoft Partner". 

I think Express is out of the question, as it doesn't contain the bells and whistles that are in Standard+ editions.  As I understand it, the Developer's version is just like Enterprise with the limitation of only 1 CAL.  Does that mean only 1 concurrent user or only 1 user -- can it have multiple user IDs in the user list, and allows only 1 user to be connected to the server at a time?  The BE databases I wish to learn from and troubleshoot-while-learning will have 1 to many users defined.  Perhaps 1-CPU is another limitation? Which is no biggy, as I am not looking for "production server" speed.

In short, I'm looking for the edition that will be as close of match to the Enterprise Edition, but for use by me alone.  Still having the ability to generate objects as in Enterprise, and execute same on the Enterprise edition. 

If the Developer Edition meets my requirements, the price is so good I'll buy it myself if my firm won't let me install it - they should, as I would only be using it for their product.

Connecting SQL Server 2005 JDBC to JBOSS

We have seen some questions on how to connect a SQL Server in the Windows environment to  jBoss. So I wrote a little how-to that describes just that.
It turns out that it is actually very simple.
Essentially, all that’s involved with installing the driver is:
  1. Download the jdbc driver from here; http://www.microsoft.com/downloads/details.aspx?familyid=e22bc83b-32ff-4474-a44a-22b6ae2c4e17&displaylang=en#filelist  (Scroll to the bottom of the screen)
  2. You can either download the Windows or Unix version. It does not really matter which one you use. For this example I use the Windows version.
  3. Run the downloaded exe file; this will create a directory called Microsoft SQL Server 2005 JDBC Driver in the directory you downloaded the file to.
  4. Copy the file Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.0\enu\sqljdbc.jar to your $JBOSS_HOME/server/default/lib
  5. Set your data source of your application to use the driver;

   
        DATASOURCENAME
        jdbc:sqlserver://DATABASE URL;databaseName=jboss;
        com.microsoft.sqlserver.jdbc.SQLServerDriver
        DATABASE USERNAME
        DATABASE PASSWORD
  
NOTE: Substitute DATASOURCE NAME, DATABASE-URL, DATABASE USERNAME and DATABASE PASSWORD for your local values.
And that is all there is to it. jBoss now should be able to connect to the SQL Server

What is difference between oracle and sqlserver ?

Oracle:
1. Oracle runs on many platforms
2. Oracle includes IFS (Internet File System), Java integration
3. Oracle requires client install and setup (Not difficult, but very UNIX-like for Windows users)
4. Oracle is well rich with Index Options.
5. Oracle provides Materialized Views for performance improvements of Stored Data with multiple Tables.
6. Failover support in SQL is much, much easier
7.Oracle provides password complexity enforcement rule..
8.Connect with one Schema and can work with other schema.

SQl Server:
1.All DDL operations that are currently running on tables belong to database "Snapshot Isolation". "Snapshot Isolation" queries are prohibited.
2.SQL requires a complex setup of ROLLBACK Segments and Transaction Level use on it.
3.SQL has just BTREE Index while compare to Oracle.
4.SQL has limitations using Materialized Views.
5.SQL Analysis Services is included (A very powerful OLAP server)
6.SQL is ANSI-SQL '92 compliant, making it easier to convert to another ANSI compliant database, theoretically anyway (truth is every database has proprietary extensions). Oracle is generally more proprietary and their main goal is to keep their customers locked-in.