| Thread | Last Post | Replies |
|
| Replication | 12 Jul 2006 05:52 GMT | 2 |
i have to merge data to sql server via gprs in my application developed in vb 6.0. can any one help me how can i send data to sl server via gprs Thx a lot
|
| 2 NIC's and SQL | 11 Jul 2006 22:36 GMT | 6 |
I have 2 NIC's on the SQL servers. Once I enable the 2nd NIC on a seperate network, the SQL admin's can not connect to the SQL databases via Enterprise Manager. I have checked the do not propagate/create a DNS entry, but the server is a DNS server. Any ideas?
|
| SQLConnect domain user | 11 Jul 2006 22:35 GMT | 4 |
I have database, I created a db_owner and linked it to an AD Domain user. But I cannot connect from my C# program. It fails to login every time. I've tried with connectstring: .. uid=MyDOM\MyUser.. and .. uid=MyDOM\\MyUser..
|
| Create SQL 2000 user accounts with a script | 11 Jul 2006 22:02 GMT | 3 |
Is it possible to create multiple user accounts within SQL 2000 via a script? We have a database on a development server that is overwritten every night. I would like to be able to create a script to create the user accounts needed. Any help or guidance would be appreciated. ...
|
| Connect to MSDE Instance via Internet. | 11 Jul 2006 22:00 GMT | 1 |
I am trying to connect to a MSDE instance across the internet. I installed it at my house and can connect from work no problem. Installed it at a customers and I can not connect to it. I can access their Linksys router and have the correct ports forwarded (I
|
| Unattended installation for SQL Server 2000 | 10 Jul 2006 22:46 GMT | 6 |
I'd like to perform several unattended installations of the JDBC driver for SQL Server 2000 (Personal Edition). Is there a simple way of doing this, perhaps similar to the manner in which SQL Server itself can be installed by tweaking a default script file?
|
| SQL 2000, Named Pipes and Windows 2003 Standard | 10 Jul 2006 21:55 GMT | 3 |
We had a problem in the past where changing from TCP/IP to Named Pipes fixed a SQL Connection timeout that happened every so often. Well, now we seperated the Web server and SQL Server onto our new Dell Blade systems which are pretty fast (faster than what it used to be on). ...
|
| Sql 2000 connect fine in Win 2000, but not in Win server 2003 | 10 Jul 2006 02:20 GMT | 2 |
I have a web application which uses SQLOLEDB for connecting SQL server 2000 database (sp4). The application server and database server both runs on Win 2000. strConn = "Provider=SQLOLEDB; "
|
| Problem connecting AS400/DB2 with SSIS | 09 Jul 2006 22:36 GMT | 2 |
Hi, I am trying to connect a MS SSIS package to an AS400/DB2 database, and I experience problem when I hit the "Create Package" button in the "Data Link properties window". I have understood that the packages need to be created, before I can
|
| Sql Server 2005 JDBC driver requires Java 1.4 | 09 Jul 2006 12:48 GMT | 1 |
But apparently only for the logging classes which strikes me as not a strong enough resons to require 1.4. Any plans to make it run on 1.3? thanks - dave
|
| SQL Server 2000 is not listening on 1433 | 07 Jul 2006 17:49 GMT | 3 |
Hi group, I'll briefly explain the situation. I installed a new SQL Server 2000 SP4 on a windows 2003 SP1 server and I have a database in a named instance running. The client where I installed this server has 2
|
| Integrated Security problem | 07 Jul 2006 04:04 GMT | 2 |
I am using 6/26 JDBC driver on win 2000 to connect sql server 2000. My url is "jdbc:sqlserver://odysseus;integratedSecurity=true;", and I was getting errors "Invalid integratedSecurity property value:true". Any suggestions. Thanks.
|
| Microsoft SQL Server JDBC performance issue | 07 Jul 2006 03:45 GMT | 1 |
We are in the process of migrating the application that runs our business from Sybase ASE 12.5.3 to MS SQL Server 2005 SP x64 Our application is a large java application which runs on Redhat Enterprise Linux 4, Tomcat, etc.
|
| DTC Hell | 06 Jul 2006 04:32 GMT | 2 |
What's the best group in which to ask about DTC issues?
|
| Upsizing problem | 05 Jul 2006 23:43 GMT | 2 |
I have just upsized my backend mdb file. It has created the new SQL server database, added the linked tables in the old mdb file and changed old tables to "oldname-local". All as expected. I can double click on either the old or new linked tables in the backend mdb file and see ...
|