
Data Masker is the easiest to use and most cost effective SQL Server data masking tool available.
KEY FEATURESA summary of the Data Masker software. DATA MASKING: WHAT YOU NEED TO KNOWA comprehensive survey of the techniques and issues you need to know about before you begin data masking. DOWNLOAD DATA MASKERA 30 day, fully functional, evaluation copy of the Data Masker software. QUICK STARTA Quick start to the Data Masker software. DATA MASKER FAQAnswers to frequently asked questions about the Data Masker software. SYSTEM REQUIREMENTSThe hardware & software supported by Data Masker. |
Errors connecting to SQL Server Express 2005Are you getting errors connecting to SQL Server Express 2005 via remote client software and yet have no problem connecting to it on the local machine? Some of the errors you might be seeing are:
If yes, then read on, because SQL Server Express 2005 is not automatically configured for remote access during installation. It can be enabled however, so the problems you are having are more of a “feature” than a bug. Why this page? Well, we too ran into this problem – just as you have now. In recognition of all of the kind help we received from the Internet newsgroups we thought it might be useful to collect the information here so as to provide assistance to others in the same position. If you have any suggestions for updates to this page please ] Make sure the SQL Server browser is started. Note this step is optional. It is possible to set the SQL Server instance to use a fixed IP address – but this is non-standard for named instances. See sqlexpress’s WebLog for details.
Client software for testing remote connectivity to SQL Server Express 2005Need some software to test out remote connectivity to SQL Server Express 2005? Probably there are lots of ways. Here are four to try out:
To install SSMSE you will need the following (note the 2.0 Beta version of the .NET framework is not acceptable. Uninstall it first if you have it.). It is probably best to install them in the order below Microsoft .NET Framework Version 2.0 Redistributable Package Microsoft Core XML Services (MSXML) 6.0 Microsoft SQL Server Management Studio Express – Community Technology Preview (CTP) November 2005
osql -S SERVERNAMESQLEXPRESS -U To use OSQL, start up a Windows command session (Start:Run…:cmd) and type in the above command. On our test machine the OSQL binaries are located in the C:Program FilesMicrosoft SQL Server90ToolsBinn directory. If you do not have this directory somewhere it probably means you did not install the client side tools. So of course now the question is how to install the OSQL tool (and others) on the client” Well fortunately it is not too difficult as they are co-located in the same installation package as the SQL Server Express 2005 software. To install them just go back to the same installer you used to create the SQL Server Express 2005 instance on the remote system and run it on your client system. Instead of accepting the default install (which installs the server engine) choose to install only the client side utilities. This will create the above directory and install the tools without installing the database on your client machine. For further testing you can also dig around a bit and find out how to use the SQLCMD.exe utility.
private void button1_Click(object sender, System.EventArgs e) { SqlDataReader rdr = null; // 1. Instantiate the connection // test by server name instance name // SqlConnection conn = new SqlConnection( // “Data Source=MYSERVERNAMESQLEXPRESS; // Initial Catalog=Northwind; // User ID=sa; // Password=sa”); // test by ip address, port and instance name SqlConnection conn = new SqlConnection( “Data Source=123.123.123.123, 1066; Network Library=DBMSSOCN; Initial Catalog=Northwind; User ID=sa;Password=sa;”); // 2. Open the connection conn.Open; // 3. Pass the connection to a command object SqlCommand cmd = new SqlCommand( “select * from Customers”, conn); // 4. Use the connection rdr = cmd.ExecuteReader; // print the CustomerID of each record while (rdr.Read) { Console.WriteLine(rdr[0]); } // close the reader if (rdr != null) { rdr.Close; // 5. Close the connection if (conn != null) { conn.Close; } MessageBox.Show(“Done”, “Done”, MessageBoxButtons.OK, MessageBoxIcon.Exclamation); } Other resourcesSQL Server 2005 Surface Configuration Tool article by Mike Gunderloy. |