I setup SQL 7.0 server on NT Server and SQL 7.0 client on NT workstation. I wrote a VC++ program using ODBC to connect
database and set ODBC Data Source Administrator as follow:
- Add a new User DSN
- setup name, description, server, of User DSN
- enter Login ID and psw
- Change the default database to "Test" which I've already built on server (leave other options remain)
- didn't change any settings in the next page
- Test Data Souce successfully.
But when I run the VC++ program, it comes out an error message like this:
SQL Error State:01000, Native Error Code: 1645, ODBC Error: [Microsoft]
[ODBC SQL Server Driver][SQL Server]Changed database context to 'Test'.
SQL Error State:01000, Native Error Code: 1647, ODBC Error: [Microsoft]
[ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
Can anyone tell me what are these error codes means? Are there any settings on the SQL server that I forgot to set?
Could someone please explain to me the client configuration utility in plain English please.
I have VB applications installed on the sales force`s laptops that log onto SQL Server through RAS and an ODBC connection. The client configuration utility is not installed on their machines, but everything works fine. The BOL say that when installing utilities, the user is given the option of selecting the net-library to use. I am not, when installing it on my NT Workstation, or W95 Operating system. The BOL also state that the control panel has an entry to allow selecting which protocol to use. I cannot see it
Who needs the client configuration utility installed, obviously not the clients, is it just the people who want enterprise manager on their desktops ?
I am completely confused by this application This is the one area of SQL Server where I am lost, help !
Maybe someone can help mewith this... Im running NT 4 SP5 on a compaq proliant 3000 server. Trying to create a DSN to connect with my remote SQL 7.0 server. When I click on the client configuration button (to set to TCPIP sockets), nothing happens. So now all DSN's default to named pipes...
I am looking to automate the rollout of the SQL Native client to our workstations. What I would like to do is use our login script to initiate an unattended install on the workstation. I will create the unattended file using the one that comes with SQL Server 2005 as a guide. This seems pretty straightforward.
More importantly, the other task I want to tackle is adding server aliases to the workstations. I am thinking of creating an alias for each of our applications and pushing the changes out by merging a registry key(maybe WMI? I dont know...). This way, should we need to move application databases to a different instance, we can just push an updated list of aliases to the workstations. The actual storage location remains transparent to the applications and users, (ie no configuration changes).
Has anyone done this or have any ideas? Are there any pros/cons that I have not thought of?
If I look under SQL native client configuration | Client protocols, I have no entries and no ability to look at the properties of SQL Native client Configuration. Something is missing which I think is related to an error when connecting to my local server.
sqlcmd -E -S .devmain, 1064
I get error :
Encryption not support sqlcmd: Error: microsoft SQL native Client : Client unable to establish connection
An error has occurred while establish 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..
In comparison to other machines here at work, it appears my remote connections are configured. But I have no Client Protocols under sql native client configuration, how can I get them in there?
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 have just finished installing SQL 2005 Ent Edition on Win 2000 Adv Server, SQL2005 SP2, and SP2 Hotfix KB934458. After the installation, I could see and configure all services via SQL Configuration Manager and SQL Server Surface Area Configuration tools. This worked for a couple of days and now both configuration tools no longer detect SQL2005 components. SQL Server Surface Area Configuration issued an error that said "No SQL Server 2005 components were found on specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLAC)". SQL Configuration Manager did not list any installed services. I don€™t know what caused this. Anyone has any idea? Please help! Below is the Installation Report which shows installed components.
===================================
The following components are installed on this server
Hi --I was wondering if this is a bug when I add new data in my table SSIS Confiurations and give wizard a new Configuration filter the package configuration wizard can not see the new values --the old values from the previous configuration are still showing---is there any known workaround or forced refresh I can do
thanks in advance Dave
Background:
SQL Package Configurations are most important because they provide the possibility of a central configuration store for your entire enterprise!!!!!!!! and is in my mind the only way to go
USE [ETLConfiguration] GO /****** Object: Table [dbo].[SSIS Configurations] Script Date: 05/23/2006 13:34:35 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[SSIS Configurations]( [ConfigurationFilter] [nvarchar](255) COLLATE Latin1_General_CI_AS NOT NULL, [ConfiguredValue] [nvarchar](255) COLLATE Latin1_General_CI_AS NULL, [PackagePath] [nvarchar](255) COLLATE Latin1_General_CI_AS NOT NULL, [ConfiguredValueType] [nvarchar](20) COLLATE Latin1_General_CI_AS NOT NULL ) ON [PRIMARY]
Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS
Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Native Client)
I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?
I have SQL2000 installed as the default instance, and now I'm trying to install SQL 2005 standard edition as a named instance.
I receive this error : SQL Server could not connect to database service for server configuration.. [SQL Native client] Encryption not supported on the client. However I'm able to install client tools
The setup works fine on other box with the same config : SQL 2000/Windows XP, is there any work around for this issue ?
In my SQL 2000 client network utilty "Force proctocol encryption " is desabled and did not find the setting for SQL 2005 !
Hello,Is it necessary to upgrade the Client Connectivity Tools on all clientmachines after the SQL Server database server is upgraded from Version7.0 to 2000?Thank you in advance!Eddy
It seems to me, that the best way is to have one Environment Varible containing the name of the SQL Server, so that you can look up the configuration in the SSIS Configuration Table when you run the package.
Is this the preferable way of doing it ? I would like to hear some positive/negative comment of why chosing a configuration type instead of another.
It seems to me that putting all of the configuration in the Environment variable is harder work but most secure (server breakdown vs table corruption/database error...)
I have tried this on several different operating systems (VISTA and XP ) and several versions of SQL NATIVE CLIENT including 2005.90.3042.0
I have a 64 bit "SQL NATIVE CLIENT" connection that fails. The exact same connection and code succeeds on 32 bit. My customer and I prepend "oledb:" to the connection string and it starts working.
FAILS on 64 bit: Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
WORKS oledb:Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
I debugged my code to the point that I know it is happening when I call CreateAccessor for my SQL statement.
I am creating a windows application to manage my ssis packages.
My SSIS packages use package configurations, and by default connect to the "SSIS Configurations" table in sql server.
However, I want it to connect to a view instead of this table, so i create a view "vwSSIS_Configurations" and point the package configuration to use the view in sql server.
The application SHOULD be capable of altering the package configuration's configuration and switch its connection between the default "ssis configurations" table, and the view.
Is this possible? I cannot think of a way which I can have my application switch the package configuration's connection.
I have a Sql7.0 box inside a firewall and Sql6.5 outside the firewall. I would like to use a DTS to transfer data. I followed the KB artice on configuring SQL to listen on a specfic port, but still have problems. I added entries in Client Config on both machines. Still no luck, looks like the 7.0 box not talking on new port...
I have a question about SQL Server configurations, especially those related to memory.
We are running SQL 6.5 SP5a on a 400 MHz machine with 1GB of RAM.
Our memory setting is 409600 (800 MB), which according to all the documentation that I have read is a conservative figure. The problem I believe is in our settings for Locks and Open Objects. The settings that are in place are Locks=3000000 and Open Objects=500000.
I am not a DBA, I am a developer, but have somehow become part of the DBA team. These settings seem out of proportion with the memory we have. The reason given for 3 million locks, by other members of the team, is that our biggest unit of work is a query that performs a select into of approx. 3 million records. To further compound things, we are getting an out of memory error on the server after only a day of running.
The other members of the team have implemented a start and start of the service to occur at 4 AM every morning, but I am convinced that this is not the appropriate action, but they will not action any configuration changes unless I can prove that it will help the memory problem and not effect the queries.
If anyone has any information or links to information regarding Locks and how they relate to query performance, or at least a sample of what your settings are it would go a long way towards convincing either myself or the rest of the team what direction to go.
I have SQL Reporting Services 2005 installed. When I go into the SQL Reporting Services Configuration Manager I immediately get an error that says that "No report servers were found on the specified machine" then Details: Invalid Namespace.
The machine that it is running on is our report server. The name in the Machine Name says the name of the report server not the name of the specific machine so maybe this is the problem? I think the name of the report server should go in instance? Problem is that it won't let me change anything and it just gives me that error and everything else on the screen is disabled.
Hey guys, got a question regarding hardware configuration for a new SQL server we are installing here. We are migrating from a Windows 2000 standard, SQL 2000 standard box with 4GB of RAM to a Windows 2000 datacenter, SQL 2000 enterprise box with 32GB of RAM.
What would be the best way to set this up in Enterprise Manager? Should I just let SQL Dynamically use the RAM or should I select a fixed amount? Also with the processors, should I allow SQL to use all available processors or just 3 of the processors? Also with such a large amount of RAM, I've read people setting there pagefile to 0 so there is no load on the hard drives.
We are running SQL 7 on a server, and are moving to a new server and will beupgrading to SQL 2005 at the same time. Currently, both the old and the newservers have two drives, one for programs and one for data.With the current configuration, SQL 7 and the data are both installed on thedata drive, in the MSSQL7 directory. Our sys admin wants to install SQL 2005on the program drive of the new server, while putting our databases on thedata drive. I argue that if SQL itself is on the program drive, then thesystem databases will be in one place, while our databases will be inanother. So I'd prefer to have SQL 2005 installed on the data drive, as itis now.I'm interested in any feedback regarding what you guys think is the betterconfiguration, and also if there's any performance hit from having theprogram and the database on two drives of the same machine.Thanks,Neil
In my Package Configurations, I have three different configurations. Two are of the type, SQL Server and one of type XML. I want to get the currently used Configuration name, Configuration String and the configuration type in my Script Task code. Can anybody help me with this code. Thank you.
We store our configurations in a SQL Server configuration table. We have SSIS packages that can be used in different senarios. Each of these senarios requires different configuration values.
Is it possible to change the SSIS configuration key used for a package at run time? i.e. we'd like to be able to use a job that says run this SSIS package but use configuration values with that name.
I've installed SBS 2003 with SQL 2005. The MBSA shows that the SQL service and agent should not be run as a Local System or Administrator. I've tried to create a new user and start the service with the new user, but no matter what I do, I cannot start the service with the new user. I've tried to add the user to the SQL* groups and Domain Users group, but no luck. I've tried adding permissions to those groups to all the SQL directories, but again, no luck. I'm getting error 5 - permission denied. Anyone got a good HOWTO?
Hi, I am very new to SSIS and SSRS.I just installed in sql server 2005 professional in my office machine. I am going to work on SSIS and SSRS. My machine itself will be the server.Could you please tell me what are the configurations I should do?.. Thanks in advance. -Selva
In my package I am using some 3 to 4 database connections. Hence I can say 3 to 4 connection managers I have. Other than that I have 2 Flat file connection manager.
What will be the best way to configure the same? and Please let me knowwhy that is the best choice.
Hi All, Using Visual studio 2005 you can create a simple database to enable the use of login using asp.net configuration by clicking on website on the menu bar. By default the database is created and stored in the App_data file. However my service provider has a separate server for SQL (SQL Server), therefor it will not work. How can I use this Asp.Net Configuration to create a database on my sql server? Hope this question makes sense!!
Hi Guys Got this problem, ive setup some new roles and users through asp.net configuration and it creates ASPNETDB.MDF in the App_Data folder when ive got a DB in SQL server 2005 express. Basically how do i change it so the tables created for the users and roles are created in the SQL Server 2005 Db? p.s I'm very new to sql server 2005 Thanks
To get an understanding of the SQL Server technology and the hardware requiremnets. To configure a VLDB system for OLTP what is a typical hardware configuration that will be used.
No of Rows:10 Million No of Tables : 50
Will have to spilt this out into many databases, or will one database be able to handle this. Assume that the database is normalized.
Any suggestion or information will be of great help. Does MS have any information relating to this information on their web site?
