Win7 (x64) Build Sqlsever2008r,weka Environment

1. Answers to the questions that SQL Server encounters

1) sqlsever2008r Express Edition is one of the versions that has a control interface for SQL Server Management Studio (mixed up with sqlserver2008r and Sqlserver2008r Express with Advanced services, resulting in another half hour).

2) Start the service, change the server, set the port ah god horse in SQL Server Configuration Manager.

3) New instance name Remember, this may be used later in the setup.

4) SQL Server Management Studio can be logged in in two ways (Windows default user and database user) If you forget the password of SA, you can log in with the former and modify it inside. The specific methods are:

1. Enter the database Manager in Windows Authentication mode,-SA right click on security-Login name, select Properties. In the General tab, re-fill in the Password and Confirm password, remove the Enforce password policy check. Click the Status tab, tick Grant and enable, OK.
2. Right-click the instance name to select Properties. Click Security, and verify that SQL Server and Windows authentication are selected.
3. Restart the SQL Server service

5) SQL Server connection port is 1433, if TCP/IP connection is not on (for example, Weka connected to SQL Server), first ensure that: SQL Server Configuration Manager->sqlserver Network configuration->express/ The server's TCP/IP service is on, next to express TCP/IP double-click, IP Address entry in Ipall (last) dynamic port is 1433, after saving restart service can take effect

6) Remote Debugging firewall problem is not solved ...

2. Weka

1) Installing weka3.7 with JDK under Win7 always encounters a problem with JDK installation failure, so jdk1.7 is manually installed (weka3.7 requires jdk1.7,weka3.6 requirements 1.6), JDK contains JRE

After installing the JDK, configure environment variables, right-click on the computer, properties, advanced, new system java_home, content for JDK installation path. System variable path appended, $JAVA _home$/jdk1.7.0_67\bin; $JAVA _home$/jdk1.7.0_67\jre\bin; new classpath system variable, content is.; %java_home%\lib;%java_home%\lib\tool.jar; (. No less, this is the address that instructs the program to find Lib)

2) connect to sqlserver2008r, download Sqljdbc4.jar (can download Sqljdbc_4.0.2206.100_chs.exe install unzip on official website). Originally have Sqljdbc.jar and Sqljdbc4.jar two kinds, because the former only support jdk1.6 before the low version, all choose Sqljdbc4.jar, behind also appeared Sqljdbc4_1.jar seemingly. For the convenience of unified management, Put Sqljdbc4.jar in the weka-3-7 installation directory in the new Lib folder, similarly, in order to apply to find the library, you need to add its path to the CLASSPATH system variables, I tried to append to the CLASSPATH variable after the result failed, so changed to.; D:\Program Files\weka-3-7\lib\sqljdbc4.jar;%java_home%\lib;%java_home%\lib\tool.jar; this way.

Start configuring the Databaseutils.props file. Go to the Weka installation directory and the Weka.jar will be backed up offsite. After decompression into Weka.jar/weka/experiment, databaseutils.props back to DatabaseUtils.props.sample, edit databaseutils.props content. For SQL Server:

1. # JDBC Driver (comma-separated list)
2. Jdbcdriver=com.microsoft.sqlserver.jdbc.sqlserverdriver
3. # database URL
4. Jdbcurl=jdbc:sqlserver://localhost;databasename=db_prophet

There are data types in the corresponding relationship, I did not modify, and then solve the problem later. Replace the modified Weka jar file with the original jar to run the Weka software.

1. Enter%weka_home%/weka from the cmd command line
2. Execute Jar CVF Weka.jar weka/*.* (Some people say that when packaging, Java_cup folder always can not pack in, resulting in an error, he solved the way is to drag Java_cup into the jar package)

To try to connect, in the Open DB tab of Weka, enter "Jdbcurl=jdbc:sqlserver://localhost;databasename=db_prophet", click on the head, enter the username, password, Click on the socket to connect, if info hint .... =true, which means that the connection is successful, you can execute it in query. Here is a reference to two articles, the first one followed by the author to share the various databaseutils.props files http://blog.csdn.net/xuxurui007/article/details/ 17448491, the second post has a tutorial to share Weka http://blog.csdn.net/popozhu/article/details/5650246

Win7 (x64) Build Sqlsever2008r,weka Environment