Where does the "Dynamically determine port" check box come from when creating a ODBC connection using TCP/IP in the client configuration? Only shows up in the control panel/adminstrative tools/Data Sources (ODBC) when it is installed. I have 3 computers here that have it (they are for development) but I am finding my users desktops do not have the box and so I am getting errors trying to connect from their desktops.
I am using Excel and Microsoft Access 2000 to connect to the server using the ODBC connection.
I need my users to connect to SQL Server 2005 so I need the "Dynamically determine port" box checked to find the port. Tried typing in the port but that isn't solving the problem or answering my question. So far I have tried MDAC and .NET 2.0 platform installs with no luck.
I have a named sql instance on SQL 2012. The issue is that the clients is having problem connecting to it when the firewall is on, this is not consistent. The connection is fine when I disabled the firewall. When I turned the Windows firewall back on, it will work for awhile and it fails. I checked the SQL configuration manager and saw that a dynamic port is assigned to the named instance. I did put that in the firewall rule and unblock it. I also put TCP 1433 and 1434 as well as the browser service port, TCPUDP 2382 and it still didn't work.What is the best way to determine what port does the named instance are listening?
In our system, we need to execute queries using linked servers. However, the linked server name is not well known, it is a value stored in the system. Is there a way this can be done?
CREATE FUNCTION dbo.stfGetSupervisorOrgUnitAssignments(@SupervisorID INT)
RETURNS @ReturnTable TABLE(Org_Unit INT PRIMARY KEY)
AS
BEGIN
DECLARE @Server VARCHAR(100)
SELECT @Server = dbo.stfGetLinkedServerName()
INSERT INTO @ReturnTable(Org_Unit)
SELECT ReplicationID FROM OPENQUERY(@Server, '....')
I want to dynamically determine which column I select data from. The table I want to select from looks like this:tblSexualitySexualityID int PKEN nvarchar(20)NL nvarchar(20)DE nvarchar(20)Based on the value of variable @LanguageColumnName I want to select the value from either column "EN", "NL" or "DE"In the sample below the value of @LanguageColumnName is "NL".Unfortunately the value of sexualityname is ALWAYS: "tblSexuality.NL" and not the value from that specific column...how can I alter my procedure so that it does the select the value from that column?ALTER PROCEDURE [dbo].[spFindUsers]@LanguageColumnName nvarchar(3),@startRowIndex int,@maximumRows intASBEGINSET NOCOUNT ON; declare @tblSexualityName nvarchar(40)set @tblSexualityName='tblSexuality.' + @LanguageColumnName SELECT UserName,UserCode,ThumbNailPicture,BirthDate,ShowAgeOnly,IsMale,NearestBigCity,DistanceToNearestBigCity,Description,IsDonator,IsVIP,SexualityName FROM(SELECT ROW_NUMBER() OVER (ORDER BY UserCode) as RowNum,tblUserData.UserName,UserCode,IsDonator,IsVIP,Description,BirthDate,IsMale,ShowAgeOnly,tblCountries.CountryPicture,@tblSexualityName as sexualityname,tblCountries.CountryName,ThumbNailPicture,LastActivityDate,UserRanking,NearestBigCity,DistanceToNearestBigCity FROM aspnet_Users INNER JOIN tblUserData ON aspnet_Users.UserId = tblUserData.UserID INNER JOIN tblCountries ON tblUserData.Country=tblCountries.CountryID INNER JOIN tblSexuality ON tblUserData.Sexuality=tblSexuality.SexualityID) as MemberInfoWHERE RowNum > @startRowIndex AND RowNum <= (@startRowIndex + @maximumRows)END
I m writing a stored procedure to query a table Population that has the following fields - CityId, CityName, Plus0, Plus10, Plus20, Plus30, Plus40, Plus50, Plus60, Plus70, Plus80. The field Plus0 contains the number of people of age > 0 living in the city, Plus10 contains the number of people of age > 10 living in the city and so on. Given the city id and age groups like 20To40, 50To60, 40Plus, etc., I should be able to query the number of people in the city corresponding to the requested age group. Note that if the requested age group was 20To60, I need to make use of only 2 fields Plus20 and Plus60 in the table to compute this value. And if the requested age group was 40Plus, then I need only the value in the field Plus40. The problem is that a wide variety of age groups can be requested like 0Plus, 10Plus, ... , 80Plus, 0To10, 0To20, 0To30, .... 70To80.
Which is the most effecient way to handle this ?
1. Have a stored procedure that returns all the fields even though only 1 or 2 of them would be actually used ?
In this case, if I returned data for a large number of cities then there would be a lot of unnecessary information that was returned by the query. Lots of data would be passed through the network though most of it would not be used.
2. Have a stored procedure that takes in parameters @Plus0, @Plus10, @Plus20, .. @Plus80 that are bits indicating whether the field was required or not and then using a CASE statement to return values for a field only if the corresponding bit parameter was set, and returning NULL if the corresponding bit paramter was not set ?
In this case, I would be returning NULL for all those fields that were not required for a particular age group. This would save some network bandwidth, wouldn't it ?
3. Pass in the age group itself (ex: 0To20) as a parameter to the stored procedure and have lots of IF statements, one for each age group, that return only the fields that are needed for that age group.
This leads to a lot of code repitition.
4. Use a similar approach as above but use dynamic SQL queries to avoid code repitition.
But using dynamic SQL queries can affect the performance of the stored procedure as they need to be compiled each time.
I'm using SSAS2005 SP2 as a data source, and RS2005 SP2 for reporting.
With the upgrade to sp2, users assigned to an area in a sales location tree no longer get a value returned for AGGREGATE(MyValue.Value) when looking at a region higher than they are assigned.
My MATRIX reports now look like:
_______________________________|___|___| Region____Sub Region____Area1__|_5___3_| Sub Region Total_______________|_______| Region Total___________________|_______| Grand Total____________________|_______|
Before sp2, they had the 5 and 3 values repeated in all total rows.
My thought was to hopefully dynamically hide the sub region and region groupings and their related subtotals - but when trying to do this, only the grand total shows, and its values are blank.
When a person can only see Area1, I'd like the report to look like this:
but if they could see everything from the cube, I would like those sections to show, because they have values in them:
_______________________________|___|___| Region____Sub Region____Area1__|_5___3_| Sub Region Total_______________|_10__5_| Region Total___________________|_20_11_| Grand Total____________________|_42_13_|
We have ODBC connection problems with some client installation. Some of them need to have the port number given in the client connect part of the ODBC setup while other (with the same client version) can use the "dynamically determine port" option, even when the port number is not SqlServer default (1433).
Has someone an idee why this happens and what to change so every connecition can use the dynamic option ?
I've been running some tests with a 3rd party application during the last few days, but the ODBC doesn´t seem to be working well.
The ODBCs are configured to go through specific ports, since there's a firewall between the server (production area) and the database (which is located in the dev area). If i press the TEST CONFIGURATION button after i configured the ODBCs, the test is successful, and the log file of the firewall monitor shows that the server is connecting through the designated ports.
But when i run the 3rd party application, the queries fail, showing an error that says "The server cannot be found or you don´t have access", after this error, another one appears, saying something like "Connection().opened..." - unfortunately I don't have the actual text, I'll try to post it as soon as i get them .
Just to make sure that the 3rd party app is doing its job, dev team wrote a simple VB6 app to query the database, and it shows the same error.
Both apps are running well in the dev environment, since dev machines don't have to go through the firewall, and both apps are using the ODBC configured in the same way as the server. I could think that the problem is the firewall, but the firewall logs show that the production server is trying to use ports 1433, 1434, 445 and 139, and there isn´t a single entry showing activity for the ports specified on the ODBCs configuration.
The database server is running SQL Server 2000, the dev pcs are running Windows 2000, and the ODBC driver version is 2000.85.1117.00.
On the Production environment the server that is trying to access the database is running Windows 2003 Server Ent Ed. SP 1 , and the ODBC driver version is 2000.86.1830.00
I hope some one outthere has any ideas to solve this problem, or at least any idea of what is causing this error, because i´m running out of them.
Hi there, I want to create an SQL Function that checks if a table exists and returns true or false. I will pass this function a paramter (say @COMPANYID) e.g.
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[tblmyTableName_' + @COMPANYID) and OBJECTPROPERTY(id, N'IsUserTable') = 1)
how would I write this so the query is dynamically executed and I can get a value of true or false back?
I have created dynamic sql to declare variables based on columns from the table and i set values to those variable now here is the issue . i want to check the variable values how do i do that dynamically
drop table test create table test ( id varchar(10) not null, col1 varchar(10) , col2 varchar(10)
[Code] .....
Now my next step is verify if the variable is blank or not how do i do that ?
How do i verify all of the columns one after the other .
I am after the statement like this dynamically
-- IF NOT (@col1 = '') THEN set @SQL = @SQL + '[col1] = ' + @col1 + ' ' --IF NOT (@col2 = '') THEN set @SQL = @SQL + '[col2] = ' + @col2 + ' '
I need to check if the columns are blank or not dynamically as i do not want to hard code the column names there.
I am using SSIS 2014 with the below .net framework version and installed in Windows server 2012 R2 . I have installed my client's odbc drivers (both 32 bit and 64 bit) in my production server and created ODBC system DSNs for 32 bit and 64 bit.
When i open SSIS 2014 and tried to create the odbc connection but i can able to see only the 32 bit system DSN connection ,i can't able to see my 64 bit odbc system dsn connection.
Microsoft Visual Studio 2012 Shell (Integrated) Version 11.0.50727.1 RTMREL Microsoft .NET Framework Version 4.5.51650
SQL Server Integration Services   Microsoft SQL Server Integration Services Designer Version 12.0.1524.0
And i installed my client odbc drivers(32,64 bit) and created ODBC system DSNs in my local system and when i open ssis 2014 and i can able to see both the ODBC system DSNS(32,64) connections from SSIS ODBC connection.
I am using below version of .net framework in my local system which was installed in windows 7 and i have SSIS 2012 also installed in my system and i can able to see both ODBC connections using 2012 as well in my local system.
Microsoft Visual Studio 2012 Shell (Integrated) Version 11.0.50727.1 RTMREL Microsoft .NET Framework Version 4.5.50938
SQL Server Integration Services   Microsoft SQL Server Integration Services Designer Version 12.0.1524.0
why i can not see the ODBC 64 bit system DSN connection from SSIS in my production server ?
I am using VB.NET 2005 and set up an ODBC connection via ODBC.ODBCConnection to a MDB database. Therefor, I use the "Microsoft Access ODBC Driver (*.mdb)".
When I set up a ODBCCommand like "ALTER DATABASE..." or "CREATE TABLE..." and issue it with the com.ExecuteNonQuery() command, I get an error from ODBC driver, that a SQL statement has to begin with SELECT, INSERT, UPDATE or DELETE.
How can I use DDL statements via ODBC?
I would appreciate if you could help me to use ODBC for that - no OLE, no ADO.
I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.
I am running Windows XP Pro SP2. I have installed the SQL Native Client for XP. However, when I try to add a new data source through ODBC Connection Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the SQL Native Client to not show up in the list of available ODBC data sources?
Hi all,I am having trouble getting linked Oracle 9 server in MS SQL Server2005 Express to work properly. My machine is running Windows XP.The Microsoft and Oracle OLE DB Providers have problems dealing withOracle's Numeric Data Type, so I decided to use Microsoft's OLE DB forODBC Provider and an Oracle ODBC source. When using the Microsoft ODBCfor Oracle Driver in my ODBC source I have inconsistent behavior.Sometimes my queries are processed properly, then other times I get thefollowing errorOLE DB provider "MSDASQL" for linked server "ODBCBEAST" returnedmessage "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttrfailed".OLE DB provider "MSDASQL" for linked server "ODBCBEAST" returnedmessage "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttrfailed".OLE DB provider "MSDASQL" for linked server "ODBCBEAST" returnedmessage "[Microsoft][ODBC driver for Oracle][Oracle]".Msg 7303, Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider "MSDASQL"for linked server "ODBCBEAST".I have no idea why sometimes I can connect to the linked server with noproblems andwhy other times it performs like this. I'm not changing anything aboutthe system I can think of. When I use an Oracle client (PL/SQL) I haveabsolutely no problems connecting. TNSPING returns that the connectionis good.This is unacceptable so I decided to try my luck with the Oracle 10gODBC driver. However when I use this and perform an openquery selectagainst the linked server I get back only 11 rows, when I know that thedatabase has over 100 rows (in fact when using the Microsoft ODBCdriver and it works that's what I get). I figured maybe the buffersetting needed to be raised in the ODBC configuration so I took it from64000 to 600000 (a magnitude of 10) but I still get back only 11 rows.I'm at my wit's end.Any suggestions on resolving one or the other problem would be muchappreciated.Thanks much
I have set up a new web server in my DMZ. This web server needs to "talk" to an application server located on my LAN. It communicates via a COM + Component.
I would like to keep the access that is open between the DMZ & LAN to minimal, obviously for security reasons. Does anyone know what port is used for COM + communication?
Please help share with me if you know the version compatibility matrix of Ms SQL Server, ODBC driver (sqlsrv32.dll), Driver Manager (odbc32.dll) and ODBC API spec. For instance, how can I know Ms SQL Server 2000 can work with which version of sqlsrv32.dll, a particular version of sqlsrv32.dll can work with which version of odbc32.dll and a certain version of sqlsrv32.dll/odbc32.dll conforms to which version of ODBC API spec (e.g. 3.5).
24/7 Production Call Centre server running NT4.0 and SQL 6.5 with all the latest service packs.
SQL mail fails(with dull regularity) and the SQL server services stop.
When the SQL server Services are restarted an error message appears stating that Port 1433 is in use after which nobody can connect via TCP/IP. Obviously the port believes the previous SQL session is still running, and won't release the port to the "New Application requesting it".
On a unix system you can force a port reset so you don't need to shutdown and restart the box. Can you do this from either SQL or NT?
Any solutions would be greatly appreciated the DBA's are 100 Miles from the Servers, so restarts are reliant on other people!
Does anyone have an idea on why when using IP with port 1433 that on the SQL 2000 Server a bind failure happens on port 1433 and are not able to get to the SQL using IP but you can use Named Pipes.
I've been diagnosing deadlocks for a last couple weeks at a client site and I understand the KEY: and TAB: locks issues. However, the client recently experienced a series of multi-branch deadlocks for which I can find no information. Attached is the deadlock text from the ERRORLOG. Any help would be much appreciated.
Iwant to know PORT number of B on A server. Iam following the following process to get B PORT number.
1) Loging to server A. 2)Opened SQL Server Configuration Manager. 3)Opened SQL Server 2005 Network Configuration. 4)Opened TCPIP properties of Protocol for B. 5)On that opened IP Address TAB 6)Got PORT number from TCP Dynamic Ports
Am i going n right way. If not please advice me the right way to get port numbers.
1. Is there a quick way to find out what port number SQL is listening to? I have 10 instances running on one server and I could find out by going to SQL log but it's bit time consuming.
I'm trying to setup SQL Server 2005 Express to communicate through a non standard port. I can connect to SQLServer on a remote machine using port 1433 when it is set as such but when I change the server to another port and try and connect using SSMSE I can't get through. I'm specifying the ip address and a colon followed by port number to connect.
For example: 123.123.123.123:1234
Any ideas?
---------------------------------- Standing on the shoulders of giants
Not sure how this particular topic should be labeled but I figured I would start here.
I have a third party Time and Attendance program that uses SQL 2000 and IIS on top of Win2003. It also uses a client side program that sits on an XP box that pulls Time clocks entries than passes that info to the SQL server. We recently needed to move to a different service, still utilizing the same Time and Attendance program but a different client utility that pulls the Time clocks. Both the client and Time and Attnedants program are developed by the same company. All that being said the new clock utility cannot connect to the SQL service. The difference between the 2 utilities is the first utility uses UDP, the second uses TCP and requires port 5405. Basically the way I€™m seeing things is that the server does not have port 5405 open this also confirmed by the company the wrote the program. There is no firewall on this server. RRAS is installed but does not have any filters enables which I believe means it will receive and pass all protocols to all ports. Using a port scan utility it shows port 5405 not to be open How can I get port 5405 open?
Just wanted to find out what port does SSIS utilizes when communicated with a remote SQL Server. Is it 1434, 1433 or something? I have a SSIS Package on Server 1, which which does inserts on SQL DB on Server 2. I think between Server 1 and Server 2, some ports are being blocked because the 2 servers are separated by a firewall. When SSIS makes connection to Server 2 (SQL), what ports does it use? Also, any other tips would also help. Here is the error I am getting:
Cannot connect to 10.xx.xx.xx.
===================================
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
I installed a new instance and changed the default tcp/ip port and configured the applications. based on request i have changed the port to default 1433. now the problem is, the instance is not coming up. Then I restored the port now its working fine. But the application user wants 1433. could you please tell me why the instances is not comming up if the port is 1433? Thanks in advance
The powers that be at my company have decided to redisign our network. The big change is that they are completely separating the two domains, whereas I guess right now one runs inside of the other.
What this means to me is that I need to get a document together which shows all the connections between different SQL servers, web pages and services that I've created over the last year.
My question is, what ports do all of these things use to communicate with SQL Server 2000? I believe the only connections right now are using ADO/ADO.NET, or straight SQL Linked Servers.
