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 have been trying to use openrowset with a shared drive, and even though the share has "full control" permissions granted to "everyone" and the accout that SQL runs under has been granted explicit full control permissions I am unable to open the file which itself has no security on it.
Can I not use a \ path and only use mapped drives?
Thanks
below works...
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=C:5People.xls', [Sheet1$])
below doesn't work...
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=\cluster02FileManager5People.xls', [Sheet1$])
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 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.
I am trying to move a log file from one drive to another.
What I have done is add another file to my file group. So now my log has a file on the 'e' drive and one on the 'f' drive. I now want to remove the file on the 'e' drive. I have emptied the file on the 'e' drive. When doing the command:
ALTER DATABASE Uniprodruntime REMOVE FILE m_rk_runtime_log
I get the following error message..
Server: Msg 5020, Level 16, State 1, Line 1 The primary data or log file cannot be removed from a database.
I have also gone into enterprise manager and tried to delete the file and it does nothing.
1: TempDB keeps getting filled. Restart of the server has not fixed it. I shrink it, but the space gets filled again. Now I can't even shrink it anymore 2: TempDB is at the wrong location. Its current location is this :C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLPROD6MSSQLDATA empdb
How do I change its location?
C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLPROD6MSSQLDATA empdb Correct location of TempDB should be: TempDB(T:) But its not there
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.
Being a very novice SQL Server administrator, I need to ask the experts a question.
How do I go about moving a database from 1 drive to another? The source drive (C is local to the server, but the target drive (E is on a Storage Area Network (SAN), although it is still a local drive for the server. I want to move the database from C: to E:. Can someone provide me with instructions?
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?
How to backup half of dbs from a server on C drive and the other half on D drive and vice versa, first half on D drive and other half On C drive using only one job and one stored procedure??
Using scheduling from job add 2 schedules to the job so first schedule backup first half to C and second half to D , the second schedule backup first half to D and second half to D.
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
This is the error it gives me for my code and then it calls out line 102. Line 102 is my buildDD(sql, ddlPernames) When I comment out this line the error goes away, but what I don't get is this is the same way I build all of my dropdown boxes and they all work but this one. Could it not like something in my sql select statement. thanksPrivate Sub DDLUIC_SelectedIndexChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles DDLUIC.SelectedIndexChanged Dim taskforceID As Byte = ddlTaskForce.SelectedValueDim uic As String = DDLUIC.SelectedValue sql = "select sidstrNAME_IND from CMS.dbo.tblSIDPERS where sidstrSSN_SM in (Select Case u.strSSN from tblAssignedPersonnel as u " _ & "where u.bitPresent = 1 and u.intUICID in (select intUICID from tblUIC where intTaskForceID = " & taskforceID & " and strUIC = '" & uic & "'))"ddlPerNames.Items.Add(New ListItem("", "0")) buildDD(sql, ddlPerNames)
What I am trying to create a query to check, If recDT is not value or null, then will use value from SELECT top 1 recDtim FROM Serv. Otherwise, will use the value from recDT. I have tried the below query but it doesn't work. The error says, Incorrect syntax near the keyword 'SELECT'.Incorrect syntax near the keyword 'else'.1 SELECT 2 case when recDT='' then SELECT top 1 recDtim FROM Serv else recDT end 3 FROM abc 4 Anyone can help? Thanks a lot.
I am installing the X86 Executable version of SQL Server. I copied it to my desktop and clicked RUN. It extracts the files and then the Install Wizard tells me there is not enough space on the C Drive to load the program. I have 23 gigabits of free space and the program only takes about 900 megabits.
Hi I have a database(CEB) and my CEB.mdf is on D Drive and CEB.LDF is on G DRIVE ...NOw I want to move the CEB.LDF on to the different drive .. can any one suggest me the way and will I have any effect on the database. It is kind of urgent.
I have a shared drive mapped to the h: drive letter on my sql server and I want to create new databases on that drive. Is this at all possible? I try it and I couldn't see h: even if I typed it in.
What problems will I get if the hard drive for the transaction logs becomes defective? Will this affect transactions and/or backup? What should I do to fix this problem?
