Do we have to manually install the ODBC 3.70 drivers for SQL server 7.0, or do they get automatically installed during the SQL server 7.0 installation. I did not see anything when I installed. So I am thinking that the drivers have to be installed separately
I really don't understand this, in an attempt to upgrade/install SP3a, I download the file sql2kdesksp3.exe, which from the documentation, you can either use for upgrading or new installs. I run a new install; in the new instance, I execute "select @@version" and get "Service Pack 1"??
this may well be the wrong place for my post, if so please move it.
I have a variety of boxes with SQL tools installed on them. For some reason last week several of them seem to have gone a bit squif.
Server 1. Enterprise manager fails to run, giving message MMC could not create the snap-in. QA runs fine.
Server 2. Load EM click on a database and try Tools --> QA it comes back with File Not Found. Add isqlw as an external tool and you can run that ok, but still File Not found on the QA tab.
I know its not data corruption, but I hope someone can give me a clue on this!
I am currently attempting to install SQL Server 2005. I had to install once due to a faulty install now when I try re-install it says all components are installed and won't continue install procedure and shuts itself down. Anyone else have this issue and know the work around or fix?
At my application I'm installing sqlexpr32.exe by doing this:
Code Block
System.Diagnostics.Process proc1 = System.Diagnostics.Process.Start( Environment.ExpandEnvironmentVariables("%SQLHome%")+ @" sqlexpr32.exe", "/norebootchk /qb reboot=ReallySuppress addlocal=all " + "instancename=SQLEXPRESS SQLAUTOSTART=1"); proc1.WaitForExit(); proc1.Close(); when I do this for the first time the sql setup runs but gives me an error saying that the file sqlncli.msi (Native Client) was not found
but if I go to the temp directory the msi is there..
when I run the app for the second time the sqlexpr32.exe detects the Native Client setup file and does the installation perfectly..
I had a working SQL 2005 that I had to uninstall. I tried to verify things were cleaned up appropriately after the uninstall and rebooted afterwards.
When I went to reinstall I choose to install on another logical drive under raid 5 (lets say H:) in the EXACT same configuration as it was previously installed sans some of the services. Post-installation the data, Install etc folders you would expect to be under H:Program FilesSQL Server are actually under C:Program FilesSQL Server and the only thing installed under the H: selection was the 90/ folder. We uninstalled again and went back through the process and confirmed the selection of drive H: and AGAIN it installed it all to C:.
I completed an install of SQL 2005 SP2 on Windows Server 2003. Everything worked fine I can connect while logged into the box, while connected thru RDP. I can create databases add users without any issue. Until!!!!
I have a third party application (Tririga) which I run the install and indicate the SQL database (in this case local) The application begins to install but when I get to the point of adding the SA password the install fails. "login fails for sa) 18456 sev 8 (wrong password) but it is the same password I use to connect to the DB. So I change the sa assword and try again and it still fails. any suggestions would be nice. by the way on machines on which I have run an upgrade from 2000 (sql) to 2005 (sql) the install does not fail.
Hi,anyone could explain this : I have installed the same asp.net application on 2 distinct hosts, each with its own SQL Server 2000 database.However, in some SQL queries in Stored Procedures, the results do not come out the same.For example, on one server the query "select @value = (select ....)-(select ...)" works and on the other one it returns a null valueAny hint ?Thanks for your helpJohann
I have a quick question about automating installation of SQL 2005. This question doesn't relate as much to SQL 2005 as it does setting up a database server.
I know that it's usually standard practice to allow SQL to "lock pages in memory". What I am trying to do is find a command line utility that will allow me to add this step to the SQL install script. Any help is appreciated. Thank you.
I am trying to install SQL 2005 that came with my Visual Studio 2008 on my Vista Machine, it will install successfully, but when I want to get to say, the Management Studio, or the Configuration Manager, there is no "Microsoft SQL 2005" node in my All Programs. what gives? you kind of need those. thanks.
With Vista Ultimate (release), I installed SQL server 2005 Developer edition. I installed SP1, apparently successfully. But my Windows update history shows the SP being installed successfully every night. I have automatic updating turned on (via AD policy).
Has anyone seen this, and does anyone know how to fix it?
I nabbed a couple from some recent installs I did, and, assuming I can get my SAN guy to always give drives the same letter assignment, it looks fairly useful.
There's still a bunch of additional stuff to do, like turn on instant file initialization, size/create additional tempdb files, and set up alerts and database mail, etc.
Can the configuration file be expanded to handle any of that? Do you use something else to template/automate your SQL installs? The more I do it, the less I want to keep doing it.
I have created a setup in visual studio and set the sql server as a pre-requsites.
now when the setup is run from
setup.exe
it checks whether sql server is installed... if installed then continues otherwise install sql server express edition, now this installation is silent,
I need to set the sa password during installation of sql server . i have no option to set the password during installation, can any one help
I am intsalling SQL 2005 in an activepassive cluster. The OS is Windows 2003 with SP1. Everything installs OK but the sql server service cannot start afterwards. There are many access errors in the Security Event log - see example below - and numerous "SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. " errors in both the SQL and Application event logs. I have tried installing SQL in both mixed mode and under Windows Authentication and get the same errors. I can install SQL 2005 outside of the cluster on both nodes. Other items of note: This was a SQL 2000 cluster. I uninstalled SQL 2K, the virtual name was changed (IP remained the same) and the DNS entry was updated to reflect the new name. Early in the installation process - 3 or 4 days ago - I got a few errors about the Server Principal Name had to be updated but when I do a setspn -l the both nodes are listed and the entries look fine, though there are no entries for the sql service (MSSQLSvc). Not sure if there should be entries for the virtual name, but there aren't any for either the old or new name. Does the new virtual name need to be added to AD? Here is the security error - Event ID is 560 and it looks like there's a problem with Remote Access and is generated when trying to access either node: Category: Object Access Type: Failure Audit Event_ID: 560 User: NT AuthorityNetwork Service Object Open: Object Server: SC Manager Object Type: SERVICE OBJECT Object Name: RemoteAccess Handle ID: - Operation ID: {0,134558507} Process ID: 1516 Image File Name: C:WINDOWSsystem32services.exe Primary User Name: CM-OHCO-DS006B$ Primary Domain: SWNA Primary Logon ID: (0x0,0x3E7) Client User Name: NETWORK SERVICE Client Domain: NT AUTHORITY Client Logon ID: (0x0,0x3E4) Accesses: Query status of service
One other informational message that may be of use - looks like there's a problem with dll's for remote access, though this isn't pertaining to SQL: The description for Event ID ( 0 ) in Source ( srmservice ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: srmservice error: 0, Started the agent (srmagent.exe)..
I have successfully installed SQL Server 2005 SP1 but when I go to the "Microsoft Update" site it is still shown as required. I have tried going back to an old image of the PC and installing SQL Server 2005 and SP1 again but still the "Microsoft Update" page is not picking up the fact that SP1 has installed successfully. Anyone had the same problem or know of a fix?
I've had some problems with Reporting Services and getting connected to the database server after configuration. I am now getting the following error message:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) (rsRPCError)
In my Database Setup everything runs fine when I click apply except for the Setting Connection Info for Reporting Server this has a yellow triangle with a ! and says that the report server cannot access internal information.
I also have not been able to Initialize as there are no instances to initialize and none are created when I go through setup. Is there something I need to delete from the registry or the file system that does not get removed upon uninstall?
Finding the "pieces of information" I need to successfully install the SQL Server Express edition is so complex. Uninstalls do "not" really uninstall completely, leading to failure of SQL install. Can you suggest a thorough, one-stop site for directions for the order of app uninstalls and then the order for app installs for the following...
SQL Server Express edition
Visual Studios 2005
Jet 4.0 newest upgrade
.Net Framework 2.0 (or should I use 3.0)
VS2005 Security upgrade
Anything else I need for just creating a database for my VS2005 Visual Basic project?
I was trying to use MS Access as my backend db but would like to try SQL Express
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
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).
On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.
Thanks,
Arif
Server Error in '/' Application. --------------------------------------------------------------------------------
ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
When I installed VS 2005, it installed the default version of SQL Server 2005 Express that ships with Visual Studio 2005 installer media.
How can apply SQL Server 2005 Express SP1 to update this existing instance?
Currently, if I run this query:
SELECT @@version
I get the following:
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
After applying SP1, I should get 9.00.2047.00.
Should I just go to this link and download & install the SQL Server 2005 Express Edition SP1:
I am using the following connecting string in report.aspx.vb and would like to use ODBC (DSN) string, how to? Dim myConnString As String = "server=TESTSQLEXPRESS;database=test;uid=test;pwd=12345"Dim dbConnection As System.Data.IDbConnection = New System.Data.SqlClient.SqlConnection(myConnString)
HeyI have developed a asp.net 2 system on my local machine using a local sql2000 server.Now i'm trying to deploy it to a windows 2003 server, using a sql2000 server on another windows 2003 server. I thought the only thing i had to do was to create a ODBC connection to the sql server, and change the connectionstring. But no :) What kind of changes do i need to do. Do i need to change the dataprovider. I get this error: 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) But i don't use a sql 2005 server. Pleace help :)
What is the native way of a front end app connecting to SQL server ? Heard it is faster than traditional ODBC. Is it SQL OLE ? If so, how do I work with ODBC mgr in windows control panel? SQL OLE is not there !
I get the follwing error when I try to link table in MS Access or try to connect to an oracle data source in a DTS Package. [ORACLE][ODBC ORACLE DRIVER][ORACLE OCI]ORA-12532: TNS:invalid argument. (#12532) [Microsoft][ODBC Drvier Manager] Driver's SQLSetConnectAttr failed (#0). I can set up the same datasource and connect to it on some machines but then on some others I get the above error. This is an orcale connection so there is no way to test it until I actually try to connect. I understand it might be a problem with WINS (resolving computer name to IP address. I do not know much about WINS, can someone tell me how to check WINS to see if this is my problem? Thanks
If your database is using NT authentication and a user creates an ODBC data source to your database, does this mean that this user can now read and write to your database?
I get the follwing error when I try to link table in MS Access or try to connect to an oracle data source in a DTS Package. [ORACLE][ODBC ORACLE DRIVER][ORACLE OCI]ORA-12532: TNS:invalid argument. (#12532) [Microsoft][ODBC Drvier Manager] Driver's SQLSetConnectAttr failed (#0). I can set up the same datasource and connect to it on some machines but then on some others I get the above error. Any Ideas? Thanks
I was wondering if anyone out there can help out. Anytime I run Query Analyzer I get the following error messages: (SQL Server Query Analyzer requires ODBC Driver version 3.7 or greater and ODBC Driver Manager version 3.5 or greater. Incompatible versions of odbc32.dll and/ or sqlsrv32.dll are installed on this machine. Are you sure you want to use SQL Server Query Analyzer?) After checking the web site the only version I came acrossed was ODBC version 2.65.0240 and I need version 3.7 or greater, can anyone tell me what to do now?
Has anyone connected from Access 2 16 bit ODBC to SQL Server 7?? I have not seen 16 bit ODBC Drivers. SQL 6.0 and 6.5 came with 16 bit drivers. PS: Phase one is to convert Access 2.0 to use SQL followed by phase to goto Access 2000.