Is Is It Advisable For SQL Installation Folder To Be On The Same Drive As Windows?
Dec 22, 2006
Hey Community,
What are the guidelines for installing the SQL Software? Is it bottleneck if both Windows and SQL software are installed on the same drive ( I have all the database .mdfs and and .ldfs on a seperate RAID array)?
Hi;I feel like an idiot to be asking this,but how do I change the default drive and folderin which new databases are created?I've been looking all over Server Mgmt Studio,and I can't find anything. I'm thinking that someonecan tell me this off the top of their heads,or slip me a link to a web page.Thanks,
when my snapshot folder is on a network drive, on which "simple filesharing" is enabled, i can access that folder without typing a user and password and configuring login security settings.
but in fact the network drive on which the snapshot folder will be located will do have a login and password. (when i go to it with windows explorer, i have to enter my login and password).
won't this cause problems for the replication? as i don't see where to enter net network login when i configure the replication via the wizard.
I was trying to install the Developer Edition of 2005 last night, and ran into a strange issue. I specified F:SQLDev as the installation directory, but the installer still refused to install claiming lack of disk space. Checking the disk cost, I saw that it was still asking for about 1.5 GB on my C: drive. I double checked, and I did specify the installation directory as F:SQLDev.
Is there documentation somewhere that describes why it would require space on the boot drive? Or am I missing a switch somewhere or something?
Why wont the installer for SQL Server let me install onto a drive other than the C drive? I am trying to install the Client tools only, but it insists on making me install to C. I need to install to a different drive for space reasons. I had SQL Server 2000 client installed, but I have since uninstalled it and tried the SQL 2005 install again and every time it wants to use the C drive.
If anyone knows a why to make this work I would greatly appreciate it.
Trying to install SQL Server 2005 beta version on partition disk drive sayF: (Other than local disk drive c:),Does anyone know how can I do this? During the installation, it never asksme on which drive it install to nor browse button is there to browse thedisk drive for installation...Any help???ThanksJ.
I'm running a security application that generates a lot of events. I have gone in over the past couple days and deleted large numbers of old events in an effort to reclaim space on the D: drive where the SQL DB for this app resides. I did this throught the app itself... through its GUI front end.
I'm not having any impact. There is not a file on the same drive where the deleted events are being directed to. If all these events are going away, why does my used space on the drive not shrink? I came at it from another tack, creating sql queries to delete old events from the same app. I did this through queries in the SQL mgmt studio. The tasks (multiple) completed successfully, and the report on the # of rows 'affected' showed that it was a substantial number. No decrease in the windows drive space being used. Any tips?
Is it possible to query a windows folder via t-sql?
A table will hold the possible file names of a set of files we receive each day. Is it possible to query the folder and match on the file names stored in t-sql to what is in the folder?
Is there a way to extract only installation files to install SQL 2012 client tools from complete media set. I'm interested in SQL MGMT Studio/Profiler/Data Quality services/Configuration tools.
Hi, On x64 versions of Windows server 2003, there is a folder called "Program Files (x86)". The use of parenthesis in this name has caused a few issues so far, particularly with connecting SQL Server 2005 to Oracle using SSIS. After several hours of searching I realized that the parenthesis was causing it, and eventually I found that the best way is to avoid creating such a name while installing the OS itself, by using winnt.sif. This would be better than renaming it and changing registry entries after the installation is done.
I realize this may not be the best question to ask of Microsoft, but why not just call it "Program Filesx86" by default so no special procedure has to be done to get around these issues? The use of parenthesis is likely to cause even more compatibility issues with other software later?
BTW I use Microsoft products regularly and love most of them
SQL server 20005 SP2 is install in my WIN XP machine. I implement a SSRS report and try to deliver the report to a share folder in window 2000 server.
I create and set permissions on a shared folder as per the information in http://msdn2.microsoft.com/en-us/library/ms345228.aspx. The account that I use in subscription is local admin account in the target machine.
I have try path \<servername>c$XXX and \<servername>XXX. Both is not ok.
I find following error message in the log file of reporting service.
ReportingServicesService!library!d!04/29/2008-00:03:40:: e ERROR: Throwing Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider+NetworkErrorException: A logon error occurred when attempting to access the file share. The user account or password is not valid., A logon error occurred when attempting to access the file share. The user account or password is not valid.; Info: Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider+NetworkErrorException: A logon error occurred when attempting to access the file share. The user account or password is not valid. ---> System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword) at Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.GetImpersonationToken(String userName, String domain, String userPwd) --- End of inner exception stack trace ---
If I try to deliver same report to a share folder in WIN XP in the same way. It is ok.
I try to install SQL Server 2000 SP3 on my Windows XP server.
During the installation, the setup process inform me database services can't be install on my machine. I can only install client tools.
It seems to success, but when I try to connect register a new database in the Enterprise Manager tool, connection to my server databases always fail with error: "waiting time expire"
If I try to connect to the same database with the Querty Analyzer it works.
How can I solve this problem ? His there a patch ?
I have Windows 98 I had MSsql 7 installed and suddenly 3 days back I got error openconnection failed.
I reinstalled MSSql 7.0 in my machine now I have different problem while installing when it comes to starting service it gets hang up for very long time and finally it says
Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information
cnfgsvr.out file looks like this Starting Service ...
An error occurred while attempting to start the service (1460)
SQL Server configuration failed.
can anyone figure out why sqlserver 7 cannot be started and it remedy and send me solution to overcome Thanks
I'm sort of newbie in sql server, so don't mind for confusion.
I installed SQL Server 2005 Express edition with Advanced Services. During Setup I have choosen to use Windows authentication for connecting to my server, cause I read it can be removed in SQL Server Management Studio (right-click on server, Properties, Security, SQL Authentication).
Few days ago I got some mdf database to attach to my server, but in readme file in the same folder, there was a message to create new user called 'Bob' (password 'msdn') with dbo permission to that database (with SQL Authentication mode access to server). I did so, created user, went to Server Properties, changed mode for Authentication), disconnect from server, and closed Management Studio. When I opened it again I clicked on SQL Authentication to connect, typed Bob as user name, msdn as password, and I got a message which was something about that it is not possible to connect with SQL Server Authentication mode, although I made a difference in Properties.
Should I install SQL Server with the new instance and with SQL Authentication mode?
I am having trouble installing SQL 7.0 beta 3 on my home PC running Windows 98. The setup process fails in the last stage when it attempts to start the server. The one thing missing on my PC is it still doesn`t have any TCP/IP address; does it matter? I have also noticed that when I run the setup, it doesn`t recognize Named pipe protocol. Have anybody had similar problem?
Any help is greatly appreciated. Thank you. -Manoj
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
INSTANCEID="SHAREPOINT"
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
FEATURES=SQLENGINE,REPLICATION
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Setup will not display any user interface.
QUIET="True"
; Setup will display progress only without any user interaction.
QUIETSIMPLE="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; The directory for the extracted service pack files used to update the setup media.
PCUSOURCE="d:d8ad8f24d77c0777a5PCUSOURCE"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; Specify the root installation directory for native shared components.
i have a windows 2003 server up and running and a client workstation connected via a crossoever cable. they both can ping each other.
my next step, i would like to replicate a "real world" scenario where i have the database engine and the sample databases on the server and i would like to be able to write to and from the cleint to main database which is going to be on the server.
so my question is, do i need a full install on both machines?
I try to install MSDE as a new instance (SQL2) on my computer with Windows 2000 Professional, but a problem occurs and instalaltion does not complete successfully. I am an administrator of the computer. The application log contains the following errors descriptions: "The SYSTEMCurrentControlSetServicesMSSQL$SQL2Perfo rmance key could not be opened or accessed in order to install counter strings.The Win32 status returned by the call is in the Record Data as DWORD 0. " and "Installing the performance counter strings for MSSQL$SQL2 failed. The Error code is DWORD 0 of the Record Data. "
I am trying to install SQL Express on Window Home XP and SCC is returning the following error:
The SQL Server Configuration Checker cannot b execute due to WMI configuration on the machine ..... Error 2147942405 (0X80070005).
I tried running the following batch file which I believe resolved the same issue that someone else raised earlier (though I am not sure whether the OS was Home XP)
Will upgrading from XP Home to XP Professional (academic version) help me install SQL express successfully>
The Batch file I ran looks like this:
FIXWMI.CMD ------------------------
@echo on cd /d c: emp if not exist %windir%system32wbem goto TryInstall cd /d %windir%system32wbem net stop winmgmt winmgmt /kill if exist Rep_bak rd Rep_bak /s /q rename Repository Rep_bak for %%i in (*.dll) do RegSvr32 -s %%i for %%i in (*.exe) do call :FixSrv %%i for %%i in (*.mof,*.mfl) do Mofcomp %%i net start winmgmt goto End
:FixSrv if /I (%1) == (wbemcntl.exe) goto SkipSrv if /I (%1) == (wbemtest.exe) goto SkipSrv if /I (%1) == (mofcomp.exe) goto SkipSrv %1 /RegServer
:SkipSrv goto End
:TryInstall if not exist wmicore.exe goto End wmicore /s net start winmgmt :End
Installation of MSDE 2000 fails on 64-bit Windows Vista (Build 5308).
The error message is "Setup failed to configure the server.Please refer the error logs for more information". No error log can be found on the machine at the time of installation. Please let me know if anyone else has encountered this problem?
Is it possible to install MSDE 2000 on 64-bit Windows Vista(Build 5308)?
hi my application is applocation1 i kept a file in this folder i want to read it from application how can i get the path of that file in my application.
i want to read the file in my root folder excluding the bin path
Hi, i tried to install SQL Server 2000 Developer and MSDE the whole day on my Windows XP SP2. MDAC is the latest, that come with WinXP SP2 (2.81). The installation fails at the end after 100% complete.
It says: Translated: "the setup programm starts the server and installs the configuration you chose..." ("das setup-programm startet den server und installiert die von ihnen gewählte konfiguration...")
then it takes some time and the failure appears, saying: "the setup programm could not configure the server. you can find more information in the server-failure-log files and in "C:windowssqlstp.log."
I have a Windows 2003 Enterprise x64 edition cluster setup and functioning normally. Now, I am trying to get SQL Server 2000 installed as a failover cluster but am having some difficulty. When installing, I get the message '[sqsrvres] ODBC sqldriverconnect failed' in the event log. The message happens when the installer is trying to bring the SQL Server Service resource online.
I am able to ping the name of the instance successfully. I am able to manually start the 'MSSQL$InstanceName' service. I have turned off the firewall on both machines, but this did not help. I have the DTC Service setup as a resource in the same cluster group.
I also read http://support.microsoft.com/default.aspx?scid=kb;en-us;815431 which seemed promising, but did not reolve the problem.
I am trying to install SQL Server 2005 on Windows Vista Home Premium edition, when I run the Installer I received are the following error message.
IIS Feature Requirement (Warning)
Messages
IIS Feature Requirement
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
I already configure IIS7 with all feature, but system still generate above mentioned message.
Hello,I am trying to recover a SQL Server 7 database from another hard diskdrive that has a corrupted Windows 2000 Advanced Server installation. Iam not able to repair the corrupted Windows 2000 Advanced Serverinstallation but the file system is intact. I have installed a new copyof SQL Server 7 onto a new hard disk and have used the sp_attach_dbsystem stored procedure to attach the database from the old hard driveinto the new installation of SQL Server 7 on the new hard drive. Thedatabase shows up in the Enterprise Manager View and all the data andstructure are there, but when I try to run a Web site that uses ODBCconnections to the database I get the following error:ODBC Error Code = 08001 (Unable to connect to data source)[Microsoft][ODBC SQL Server Driver][Named Pipes]Specified SQL servernot found.I have double-checked that all the NTFS permissions, ODBC DSNs, and WebServer settings are correct and when I run the SQL Server ODBC drivertest at the completion of each ODBC DSN setup, it is successfull.1) Why am I getting this ODBC error?2) What steps have I missed in the recovery process?3) If I have done something wrong recovering my database, can I stillrecover it since I still have: a) The old master database file and logfile; b) The old database (non-master) file and log file; c)A backed-up(Enterprise Manager -> Right Click A Database -> All Tasks -> BackupDatabase) copy of the old database (non-master) file; ?My System Specifications:-Windows 2000 Advanced Server-SQL Server 7-IIS 5.0-Cold Fusion Server 4.5 Professional Full EditionThanks For Your Time,Nathan
We deploy an application that uses SQL Server Express 2005. One of our test engineers tried to use our setup on Windows XP SP 3. But the SQL server installer gave an error - unable to update msxml6r.dll. Is this a bug of the SQL Server installer or do we need to make use of a more recent version of msxml6?
I need a hand here, referring to this knowledge base on Microsoft (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811) i applied this knowledge base, and it worked, the MSSQL and SQLSERVERAGENT have run under local non admin account.
But after i installed SP1, MSSQL service is ok, but SQLSERVERAGENT wont run. The warning message is : "Some service run and then stop if they have no work to do."
Is there any way i can install SP1 but in the same time run SQLSERVERAGENT under local non admin account?