I'm trying to hit an informix box... I've found two software packages (both priced in the THOUSANDS of dollars)... Looking for a cheap...er, a FREE way to hit this informix box via DTS.
I'm trying to create a simple .dtsx package that imports data to SQL server 2005 from an informix 7.3 db using an ADO.net ODBC connection. I am first creating the groundwork for the dtsx package in SQL server using the wizard, and then editing the file later in visual studio.
My data source SQL in the dataflow task is simple and it works great until I hit a locked record on the Informix database.
select <coulmns>
from <table>
Where <condition>
The work around syntax for the locked row on the informix DB should be:
set isolation to dirty read
go
select <coulmns>
from <table>
where <condition>
This syntax will return the data correctly using a non-microsoft SQL editor, however it will will not parse corectly within visual studio. Interestingly enough, in visual studio I can parse the islolation and the select indenpendantly, just not in the same statement.
Has anyone come across this before? Any ideas on what I can do to resolve my problem?
I'm having trouble using Informix 2000 database as a source. I have an OpenLink v 5.2 driver installed and a System DSN set up. I can successfully test the connection.
I added the ADO.Net DSN to the connection manager and added it to a DataReader Source. I then added the SQLCommand property. I was able to map columns (took a long time for the columns to show up) and then I get an error: "Function sequence error:". Can not save the DataReader.
I am trying to read an Informix 9.3 blob field into a TSQL (SQL Server Stored Procedure) and the data type conversion is not supported thru the MS ODBC Driver installed with Win2000/SQL2000. Does anyone know of another method to retrieve this data, or of a vendor that provides an ODBC driver that supports the Informix blob data type. Thanks!
What can be the reason(s) why I can't get data from a linked server using an ODBC datasource that works fast & fine from MS Access?
I have an ODBC connection (System DSN) configured for an Informix ODBC driver. The Test button (belonging to this driver-setup) reports a successfull connection test. Getting data from this database by linking tables in MS Access works fast and easy. But I have tried for many days now to setup a linked server from SQL Server (2005) Creation goes fine, but as soon as I issue a query, (e.g. 'select * from infrem723...remotetable' or using 'openquery') I get the following error: ---
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "infrem723" reported an error. The provider did not give any information about the error.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "infrem723".
---
Why is Access able to read what "MSDASQL" cannot? I am desperate - can anybody help?Thanks a lot!
Basically, I am asking if it is possible to use SSMS (Query Analyzer window) with Informix. I am thinking linked server. If I have the ODBC driver installed on my workstation (win 7 pro VM workstation -- SSMS on same VM machine) is this doable? Do I just do the standard linked server routine or is there a special way (if it is even doable).
In a stored procedure I have, I need to make a call out to a DR server, I believe the named pipes protocol is causing errors for long running sql. Is there anyway I can change the call
exec svr_dr.msdb.go
to ensure that it uses the tcp protocol rather than named pipes?
I want to use TCP/IP network protocol on the server and have my clients using TCP/IP Net library. I have having some problems with this...The server will not register if I only have TCP/IP without Named Pipes using Standard Security in SQL Server. If I have TCP/IP and Named Pipes, the client can't register the server. Can someone explain in detail to me on using TCPIP on the server and client?
Has anyone ever seen TCP/IP become a disabled protocol without manual intervention from a user?
My websites just stopped talking to my MSSQL db and when I went into sql client config utility on the web boxes, tcp/ip was disabled. Any clues? Can't find anything to support this in the event or web logs.
If using sql server authentication between two SQL Server instances (firewalled and on different networks),how are the connection details transported, specifically, is the IP addess, username and password sent in clear or is their some internal obsfuscation/de-obsfuscation mechanism native to SQL Server in operation under the covers?
I am connection to a SQL server that has force protocol encryption checked. From my ASP.net application, specifically in my connection string, what parameter do I need to use to take advantage of this encryption?
I dont know if this is the right place to put in this question.
The problem is
I have an application developed using VB 6.0 and SQl Server 2000. It was working fine on my machine. I had MS XP installed on my system alongwith SP1. But when i installed MS XP SP2, i got the error while saving the record. the error is "Protocol Error in TDS Stream". I went to microsoft site searcing for the resolution of this error. They gave the solution of installing MDAC 2.8 SP1. But when i install MDAC 2.8, it gives me this error "MDAC 2.8 RTM is incompatible with this version of Windows. All of its features are currently part of Windows." And since MDAC 2.8 is not installed so i can not install MDAC 2.8 SP1 also.
I have MDAC 2.5 installed on the system.
How can i resolve it. Please give a solution as soon as possible. I am in great need of it.
I am using SQL Server 6.5. By default TCP/IP protocol is not enabled (1433 port is not opened by the server). How can I enable this so that I can use a JDBC driver to connect to it.
In SQL Server 2000, the "SQL Server Network Utility" helps us to enable the TCP/IP protocol. But not able to figure our how/where this can be done in 6.5.
Can anyone point to a reference which documents the pros and cons of the various connection protocols, such as Shared Memory vs. TCP/IP? I thought I saw something indicating that shared memory is fastest, which would explain why this protocol is tried first, but now I can't find it. This resource has information on creating connection strings, but not the advantages and disadvantages.
I cannot connect to a SQL Server that is in domain "x" from my client which is in domain "y" using Multi-Protocol. There is no trust between domains x and y. The SQL Server has Multi-Protocol installed and is working correctly ie. I can connect to it from other clients in the same domin via Multi-Protocol.
I have tried multiple things to make this work. Adding the SQL Server to my LMHOST file. Adding advanced settings for the SQL Server in my "SQL Client Configuration Utility".......All with no avail. I have received different error messages which I have found little about. "ConnectionOpen (RPC open())", "OS ERROR 1703", "OS ERROR 11".......
Has anyone had similar problems? If so, is there a fix or something that I could be missing?
Our client is trying to access the report builder from there machine via a proxy and it does not work, What would be all the ports and protocol (http,https,ftp) needed to be open for the report builder application to work normally behind a proxy? or does anyone know what are the ports and protocol used by report builder ? because we need to provide this information to our client so they can access our report server.
I have a 2 node SQL Server 2005 cluster with 2 named instances. Both appear to be working properly with no issues but I have the following warning message in the event viewer and I would like to know if it is something I should be worried about.
Source: SQL Browser Type: Warning Category: None User: N/A Description: The configuration of the AdminConnectionTCP protocol in the SQL instance XX is not valid.
The servers in the cluster are running with Windows Server 2003 X64 Enterprise Edition, SQL 2005 Enterprise Edition SP2 X64.
I have failed the cluster over and I continue to get the message when I start the instances in the cluster admin, but I don't appear to have any other symptons. Client machines can connect without any problem and transactional replication works no matter what node I bring the instance up on.
I changed default TCP/IP port and disable/enable Named pipes, but no luck so far. I see lots of postings about this message but it seems to be related to SQLExpress and I am not using that here.
Scenario: Private SQL server that has a v6 public facing address. How can I disable the interface over my public address only but keep functionality over the local address?
IP1: 192.0.0.1 Active: Yes
IP2: 2600::5 Active: Yes
IP3: fc2e::5 Active: Yes
When I try to change IP1 and IP2 to Active: No it tells me file is read only.
I am loading data from one server to another server using SSIS,After loading some rows i am getting the below mentioned Error.Each time i run i am getting the error in different Dataflow tasks in the package.
Error : " [OLE DB Source [199]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream".
The PrimeOutput method on OLE DB Source returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.There may be error messages posted before this with more information about the failure.".IS this SSIS package Error or Network related?
I have a green light on my Report Services Confuration, and can configure the server within sharepoint integrated mode. I have also assign the appropriate permission for aspnet etc..etc.
From within Business Intelligent studio when I tried to publish my reports I get the below error:
The server commited a protocol violation
Here is a copy of the report server services log file.
<Header> <Product>Microsoft SQL Server Reporting Services Version 9.00.3042.00</Product> <Locale>en-US</Locale> <TimeZone>GMT Daylight Time</TimeZone> <Path>C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesLogFilesReportServerService__main_06_21_2007_10_47_38.log</Path> <SystemName>DMTXDW01VM2</SystemName> <OSName>Microsoft Windows NT 5.2.3790 Service Pack 1</OSName> <OSVersion>5.2.3790.65536</OSVersion> </Header> ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing ConnectionType to '1' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file. ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file. ReportingServicesService!servicecontroller!9!21/06/2007-10:47:46:: i INFO: Total Physical memory: 1073094656 ReportingServicesService!servicecontroller!4!21/06/2007-10:47:47:: i INFO: RPC Server started. Endpoint name ='ReportingServices$MSSQL.3'
I am getting the following warning in the Application Event Log:
The configuration of the AdminConnectionTCP protocol in the SQL instance SQLEXPRESS is not valid.
The warning is logged by the SQLBrowser service.
This is happening on Windows 2003 server with SQL Server Express 2005. On the same machine SQL Server 2000 is installed.
I am currently unable to connect from remote clients to the instance of SQL Express and I believe it has to do with this warning (I've tried all the usual remote connection troubleshooting without success - enabled protocols, SQL Browser Service running, there is no firewall on the server, I disabled firewall on the client when trying to connect).
Does anyone know how to resolve this issue?
If you need additional information please let me know.
I am accessing a SQL2005 Express SP1 Server via TCP/IP (all machines fully up to date with windows update). For ease of configuration the Server IP is mapped to an Alias in Native Client Configuration Manager. On the Client Force Protocol Encryption is set to Yes and Trust Server Certificate is set to No. The clients are accessing the DB via SQL 2005 Management studio express and Ms Access 2003 (an access adp front end to the sql database).
As a test i turned off force encryption on the server. A Network trace shows no encryption! Turning on force encryption on the server corrects this.
As a further test I configured the server with a certificate the client doesn't trust. No error is generated by the un-trusted certificate! The only way to generate the certificate error is to enable encryption in the connection properties of each application. Why isn't the Native Client Configuration Manager utility enforcing this???
This brings me on to a second (off-topic problem). In my access adp file, if I enable €œuse encryption for data€? advanced option under the database connection dialog all works as expected (encryption + certificate verification). However, I am programmatically updating the connection in VBA
Application.CurrentProject.OpenConnection "Provider=SQLOLEDB.1;Data Source=AliasName;Use Encryption for Data=True;..."
If I do this no encryption is enabled!!! Access seems to just ignore the encryption statement.
Has anybody got any ideas as to why either of these issues are occurring or if there are any workarounds?
I've been reading about the protocols and i've been trying to connect to my SQL SERVER using each one of the protocols, but i think I'm missing something, i dont have any problems using Shared Memory and TCP protocols, but I'm not pretty sure how to connect to my remote SQL SERVER using NAMED PIPES protocols. The books On Line of Microsoft refer that you can connect using this protocol using the next syntax: Connecting to a default instance by specifying a named pipe name:
APPHOSTpipeunitapp
Connecting to a named instance by specifying a named pipe name:
APPHOSTpipeMSSQL$SQLEXPRESSSQLquery
Connecting to default instance by name, forcing a named pipes connection:
np:APPHOST
Connecting to named instance by name, forcing a named pipes connection:
np:APPHOSTSQLEXPRESS
But I can't connect to my remote SQL SERVER, if i try the same with my local SQL SERVER i don't have any problems. I've been reading the articles so many times searching something about Named Pipes is only for local connections, but Microsoft say that it's posible to connect to a remote SQL SERVER, but i don't know how to do that. The firewall is disabled, I changed the APPHOST in the above syntax for the IP address of my SQL SERVER but it didn't work..
Please help. I am trying to translate this to SQL 2005. This language is in Informix SQl. I do not know anything about informix. I am especaially confused with the "JOINS". Any help would be appreciated. THANKS.
FROM property, address, ppi, outer code_table state, outer code_table country, code_table prop_role WHERE property.id = ppi.property_id AND ppi.address_id = address.id {AND (property.eff_to_date IS NULL OR property.eff_to_date >= TODAY) AND (ppi.eff_to_date IS NULL OR ppi.eff_to_date >= TODAY) AND ppi.eff_from_date <= TODAY} AND state.id = address.province_state_cd AND country.id = address.country_cd AND prop_role.id = ppi.prop_role_cd AND prop_role.code_table_cd = "OWNER" AND property.pact_code <> 'PERS'
I have downloaded the datadirect ole db provider for informix 7.x and am need the correct sp_addlinkedserver syntax to get my sql server 7 and informix hooked up. Can anyone help?
I want to transfer data from an Informix database using DTS. What driver do I need to use for that? What are the settings for the Data Source Name? Has anyone of you accomplished DTS from Informix to SQL Server?
Let me know if you have any ideas that you can share.
My task is to convert this Informix SQl Script to SQL 2005, unfortunately I am not really familiar with Informix SQL. Below is an example script. I can figure out the "Select" statement and the "Where" statement, but the "From" statement is giving me a hard time. Any assistance would be appreciated.Thanks
WHERE property.id = prop_valuation.property_id AND property.id = legal_description.property_id AND property.eff_to_date <= TODAY AND legal_description.id = legal_lines.legal_id AND legal_lines.line_nr = 1 AND tax_code_area.id = prop_valuation.tca_id AND property.id = property_char.property_id AND property_char.prop_char_typ_code = "SIZE" AND property.id = usecd.property_id AND usecd.prop_char_typ_code = "USECD" AND usecd.value = ct.code_table_cd AND property.pact_code <> 'PERS'
I'm getting the below errors when using sql server's data import wizard. Please Note: My test connection was successful and the error occurs when I click the "Next" button after closing the properties window. For Security reasons I've filled the User Id and DataSource with a bogus account, database, and server i.e. xxxx. Notice the password is blank?... Is that normal? I'm in a jam and appreciate your help.
Thanks,
Matt
===================================
Cannot get the supported data types from the database connection "Provider=Ifxoledbc;Password=;Persist Security Info=True;User ID=xxx;Data Source=xxx@xxxx". (SQL Server Import and Export Wizard)
===================================
IErrorInfo.GetDescription failed with E_NOINTERFACE(0x80004002). IErrorInfo.GetDescription failed with E_NOINTERFACE(0x80004002). (System.Data)
------------------------------ Program Location:
at System.Data.OleDb.OleDbConnectionInternal.GetSchemaRowset(Guid schema, Object[] restrictions) at System.Data.OleDb.OleDbConnection.GetOleDbSchemaTable(Guid schema, Object[] restrictions) at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.LoadTypeData(OleDbConnection myDestConnection) at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.CacheDataSourceInfo(IDbConnection myConnection)
We are using Informx for our transactional DB and want to be using reporting services to provide reports. We have some using ODBC directly to Informix, but need to start extracting data from Infomix and aggregating it in SS 2005.
Is anybody else doing this?
Where can I find information of how to do this? We are totally new to SSIS.