Showing posts with label drive. Show all posts
Showing posts with label drive. Show all posts

Monday, March 19, 2012

Installation to different folder issue

I have only SQL engine installed to my D drive. (SQL Server 2005 no SP1)

I want to install SSIS to my D drive but i can not.

It only gives me the option to install to the default drive C:\...

saying that "the sql shared path has already been configured"

Is this a BUG ?

No Tools nor Notification Services are installed (which i understood to be related to the same path as SSIS)

thanks,

raviv

hi raviv,

there should be an advance option

to allow to configure the destination folder.

regards,

joey

|||

there is an advanced option.

but the changing of the path is disabled since it says:

"the sql shared path has already been configured"

but as this article indicates there must be a way to configure it:
http://msdn2.microsoft.com/en-us/library/ms143547.aspx

at least when non of the next components is installed:
Integration Services
Notification Services &
Client tools

since all must have the same path.

maybe it's just a problem of uninstalling (i did it to SSIS)
that is not freeing the registry entry of the "shared path" (BUG?)
if so, i might be able to change it directly.
but i don't want to mess with registry without knowing for sure ...

did anyone succeed to install SSIS to default path
and then trying to change the path (by reinstalling or other way) ?

Friday, March 9, 2012

Installation problem

When I had installed SQL 7.0 and about 99% completion,
the CD ROM drive is out of order and I had to end the
task.
Then I tried to uninstalled through add/remove program
but it is not successful.
Then I reinstalled SQL 7.0 again but the below messages
appears;
" There are files in the installation folder that do not
correspond to an existing installation listed in the
registry."
What has caused this? How to solve it? Please advise!Have a look at this article to see if it offers you any more information.
http://support.microsoft.com/default.aspx?scid=kb;en-us;276044&Product=sql
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Tan TL" <tackliong.tan@.sidel.com> wrote in message
news:0af301c393ad$5a5522a0$a301280a@.phx.gbl...
> When I had installed SQL 7.0 and about 99% completion,
> the CD ROM drive is out of order and I had to end the
> task.
> Then I tried to uninstalled through add/remove program
> but it is not successful.
> Then I reinstalled SQL 7.0 again but the below messages
> appears;
> " There are files in the installation folder that do not
> correspond to an existing installation listed in the
> registry."
> What has caused this? How to solve it? Please advise!

Installation of SQL Server 2005 on the partition disk drive

Trying to install SQL Server 2005 beta version on partition disk drive say
F:\ (Other than local disk drive c:\),

Does anyone know how can I do this? During the installation, it never asks
me on which drive it install to nor browse button is there to browse the
disk drive for installation...

Any help?

Thanks
J.Joriveek (nojunk@.please.com) writes:
> Trying to install SQL Server 2005 beta version on partition disk drive say
> F:\ (Other than local disk drive c:\),
> Does anyone know how can I do this? During the installation, it never asks
> me on which drive it install to nor browse button is there to browse the
> disk drive for installation...

As I recall, you need to go to the Advanced section to do this.

But part of the installations will always be in your ProgramFilesDir,
that is normally C:\Program Files.

Also, you should post your SQL 2005 to the SQL 2005 newsgroups, as these
are monitored by the SQL Server folks. See here for access:
http://go.microsoft.com/fwlink/?linkid=31765.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Wednesday, March 7, 2012

Installation of SQL Server - Security Question

Dear All,
We have recently had an audit of our Server and have been told to move the
installation as it cannot be on the same partition or drive as the OS.
Can anyone tell me why ?
We are running 2000 on a 2003 box.
Thanks
P
Hi
Ideally, the installation should be on another drive so that the OS has the
C drive to itself. This helps to keep applications from the OS, enhancing
security.
Data, Logs and Backups should never be on the OS drive, each should be on
seperate drives for recoverability and performance.
Regards
Mike
"Patricia" wrote:

> Dear All,
> We have recently had an audit of our Server and have been told to move the
> installation as it cannot be on the same partition or drive as the OS.
> Can anyone tell me why ?
> We are running 2000 on a 2003 box.
> Thanks
> P
|||Thanks Mike,
Our log and data files are on different drives.
What I can't understand is if they are on a different drive, then why do we
need to move our SQL Server program files ?
thanks
P
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Ideally, the installation should be on another drive so that the OS has the
> C drive to itself. This helps to keep applications from the OS, enhancing
> security.
> Data, Logs and Backups should never be on the OS drive, each should be on
> seperate drives for recoverability and performance.
> Regards
> Mike
> "Patricia" wrote:
|||Actually I'd think that most people would the happy with the OS and SQL
installation on the same drive. The important thing is to keep your Data,
Log and Backup on seperate drives. The only thing I can think of with
regards to the installation files, is if you have your swapfile and tempdb
files on the same drive as your OS and SQL installation. In that case I'd
think about moving these to another drive, but personally I wouldn't be
concerned about having my OS and SQL files on the same drive.
Regards
Steen
Patricia wrote:[vbcol=seagreen]
> Thanks Mike,
> Our log and data files are on different drives.
> What I can't understand is if they are on a different drive, then why
> do we need to move our SQL Server program files ?
> thanks
> P
> "Mike Epprecht (SQL MVP)" wrote:

Installation of SQL Server - Security Question

Dear All,
We have recently had an audit of our Server and have been told to move the
installation as it cannot be on the same partition or drive as the OS.
Can anyone tell me why ?
We are running 2000 on a 2003 box.
Thanks
PHi
Ideally, the installation should be on another drive so that the OS has the
C drive to itself. This helps to keep applications from the OS, enhancing
security.
Data, Logs and Backups should never be on the OS drive, each should be on
seperate drives for recoverability and performance.
Regards
Mike
"Patricia" wrote:

> Dear All,
> We have recently had an audit of our Server and have been told to move the
> installation as it cannot be on the same partition or drive as the OS.
> Can anyone tell me why ?
> We are running 2000 on a 2003 box.
> Thanks
> P|||Thanks Mike,
Our log and data files are on different drives.
What I can't understand is if they are on a different drive, then why do we
need to move our SQL Server program files ?
thanks
P
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Ideally, the installation should be on another drive so that the OS has th
e
> C drive to itself. This helps to keep applications from the OS, enhancing
> security.
> Data, Logs and Backups should never be on the OS drive, each should be on
> seperate drives for recoverability and performance.
> Regards
> Mike
> "Patricia" wrote:
>|||Actually I'd think that most people would the happy with the OS and SQL
installation on the same drive. The important thing is to keep your Data,
Log and Backup on seperate drives. The only thing I can think of with
regards to the installation files, is if you have your swapfile and tempdb
files on the same drive as your OS and SQL installation. In that case I'd
think about moving these to another drive, but personally I wouldn't be
concerned about having my OS and SQL files on the same drive.
Regards
Steen
Patricia wrote:[vbcol=seagreen]
> Thanks Mike,
> Our log and data files are on different drives.
> What I can't understand is if they are on a different drive, then why
> do we need to move our SQL Server program files ?
> thanks
> P
> "Mike Epprecht (SQL MVP)" wrote:
>

Installation of SQL Server - Security Question

Dear All,
We have recently had an audit of our Server and have been told to move the
installation as it cannot be on the same partition or drive as the OS.
Can anyone tell me why ?
We are running 2000 on a 2003 box.
Thanks
PHi
Ideally, the installation should be on another drive so that the OS has the
C drive to itself. This helps to keep applications from the OS, enhancing
security.
Data, Logs and Backups should never be on the OS drive, each should be on
seperate drives for recoverability and performance.
Regards
Mike
"Patricia" wrote:
> Dear All,
> We have recently had an audit of our Server and have been told to move the
> installation as it cannot be on the same partition or drive as the OS.
> Can anyone tell me why ?
> We are running 2000 on a 2003 box.
> Thanks
> P|||Thanks Mike,
Our log and data files are on different drives.
What I can't understand is if they are on a different drive, then why do we
need to move our SQL Server program files ?
thanks
P
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Ideally, the installation should be on another drive so that the OS has the
> C drive to itself. This helps to keep applications from the OS, enhancing
> security.
> Data, Logs and Backups should never be on the OS drive, each should be on
> seperate drives for recoverability and performance.
> Regards
> Mike
> "Patricia" wrote:
> > Dear All,
> > We have recently had an audit of our Server and have been told to move the
> > installation as it cannot be on the same partition or drive as the OS.
> >
> > Can anyone tell me why ?
> >
> > We are running 2000 on a 2003 box.
> >
> > Thanks
> > P|||Actually I'd think that most people would the happy with the OS and SQL
installation on the same drive. The important thing is to keep your Data,
Log and Backup on seperate drives. The only thing I can think of with
regards to the installation files, is if you have your swapfile and tempdb
files on the same drive as your OS and SQL installation. In that case I'd
think about moving these to another drive, but personally I wouldn't be
concerned about having my OS and SQL files on the same drive.
Regards
Steen
Patricia wrote:
> Thanks Mike,
> Our log and data files are on different drives.
> What I can't understand is if they are on a different drive, then why
> do we need to move our SQL Server program files ?
> thanks
> P
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Ideally, the installation should be on another drive so that the OS
>> has the C drive to itself. This helps to keep applications from the
>> OS, enhancing security.
>> Data, Logs and Backups should never be on the OS drive, each should
>> be on seperate drives for recoverability and performance.
>> Regards
>> Mike
>> "Patricia" wrote:
>> Dear All,
>> We have recently had an audit of our Server and have been told to
>> move the installation as it cannot be on the same partition or
>> drive as the OS.
>> Can anyone tell me why ?
>> We are running 2000 on a 2003 box.
>> Thanks
>> P

Installation of MS SQL SP3 failed

Hello,
We have a problem installing SP3 on some machines. We get
the following error:
"There is not enough space on drive C:\ to extract this
package. Please free up 109.41 MB and click Retry."
We found a Microsoft Knowledge Base Article - No. 301913
on this problem, but it gives a workaround that is not
helpfull for us:
"To work around this problem, add or delete files on your
computer so that the free disk space is not a multiple of
4-gigabytes."
Is there another solution/workaround for this problem?
The link for the articale is:
http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com:80/support/kb/articles/Q3
01/9/13.ASP&NoWebContent=1
Thanks,
ShiriSP3a fixes problems with the installation of SP3. Suggest going straight to
SP3a
--
HTH
Ryan Waight, MCDBA, MCSE
<Shiri.Tzuk@.verint.com> wrote in message
news:093201c3a7a0$bd103db0$a501280a@.phx.gbl...
> Hello,
> We have a problem installing SP3 on some machines. We get
> the following error:
> "There is not enough space on drive C:\ to extract this
> package. Please free up 109.41 MB and click Retry."
> We found a Microsoft Knowledge Base Article - No. 301913
> on this problem, but it gives a workaround that is not
> helpfull for us:
> "To work around this problem, add or delete files on your
> computer so that the free disk space is not a multiple of
> 4-gigabytes."
> Is there another solution/workaround for this problem?
> The link for the articale is:
> http://support.microsoft.com/default.aspx?
> scid=http://support.microsoft.com:80/support/kb/articles/Q3
> 01/9/13.ASP&NoWebContent=1
> Thanks,
> Shiri
>|||Shiri - why can you not manually use some space up?
> We have a problem installing SP3 on some machines. We get
> the following error:
> "There is not enough space on drive C:\ to extract this
> package. Please free up 109.41 MB and click Retry."
> We found a Microsoft Knowledge Base Article - No. 301913
> on this problem, but it gives a workaround that is not
> helpfull for us:
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq

Installation of IS to Server

Hi,

Is there a need to install the Integration Services to a Server? Isn't it enough to just port the .dtsx file from my local drive to the server and execute it by SQL Agent using DTExec /f command?

thanks,

cherriesh

cherriesh wrote:

Hi,

Is there a need to install the Integration Services to a Server? Isn't it enough to just port the .dtsx file from my local drive to the server and execute it by SQL Agent using DTExec /f command?

thanks,

cherriesh

You won't have dtexec.exe without installing SSIS. And SSIS is required to be installed regardless, as dtexec.exe would require the SSIS dlls to execute anyway. SSIS isn't redistributable like the old DTS was.