MRe: Cannot start SQLEXPRESS

I have just had to reinstall all my SQLServer instances (SQL2005 Standard, BCM2007, and SQLEXPRESS).

The first two have started fine, but I cannot get the SQLExpress instance to start. When I start in the Management Studio, the error I get is:-

"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: SQL Network Interfaces, error: 26 - Error Loating Server/Instance Specified) (Microsoft SQL Server)."

Can anyone tell me what I have to do to correct this problem:?

I have looked in the Add or Remove Programs window and cannot see ANY instance relating to SQL Server Express 2005.

Hi,

First, if you have installed SQLExpress on your local machine then it should allow you to connect. If not try to configure it to allow remote connections. Following links will help you to do so.

And last, if you want to know about SQLEXpress instance, go to services in management console and there you can find if SQLExpress service is running or not and at the same location you can find the SQLExpress instance information.

Links are:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1712017&SiteID=1

http://techno-geeta.blogspot.com/2007/04/sql-server-2005-remote-connections.html

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

|||

Unfortunately, none of these suggestions can be implemented. SQLEXPRESS does NOT appear in either the Surface Area Configuration menu, nor in the Configuration Manager module in MMC.

It does appear in the services tab, but when I attempt to start it, I get the response:-

"Could not start the SQL Server (SQLEXPRESS) service on local computer. Error 3: the system cannot find the path specified."

How do I reconfigure this to allow it to work?

|||

Hi.

It seems that your SQLExpress installtion has problems. Please try to reinstall it. It may solve the problem.

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

|||

Mayur

Thanks for that information.

I tried the installation again, and all tasks completed successfully other than the last one "SQL Server Database Services" where it reported an error:-

"The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "Howto view SQL Server setup log files" and "Starting SQL Server manually"."

This repeats when I retry. When I cancel, the install process finishes, but the SQLExpress instance does not appear.

This install generated an error report that is apparently sent to Microsoft. However, this does NOT help me with getting SQLExpress to actually WORK.

How do I rectify this issue? I need to have this instance running so that I can support my clients with another package that depends upon this working.

I am including the last part of the summary installation log which may help with your examination:-

Failed to install package
Fatal error during installation.
Setting package return code to: 29503
Complete: InstallSqlAction at: 2007/5/17 14:45:10, returned false
Error: Action "InstallSqlAction" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Skipped: InstallToolsAction.10
Skipped: Action "InstallToolsAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "tools", install will be skipped as a result.
Skipped: InstallASAction
Skipped: Action "InstallASAction" was not run. Information reported during analysis:
No install request found for package: "as", install will be skipped as a result.
Skipped: InstallRSAction
Skipped: Action "InstallRSAction" was not run. Information reported during analysis:
No install request found for package: "rs", install will be skipped as a result.
Skipped: InstallToolsAction
Skipped: Action "InstallToolsAction" was not run. Information reported during analysis:
No install request found for package: "tools", install will be skipped as a result.
Skipped: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2007/5/17 14:45:10
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 3
Error Code: 0x80070003 (3)
Windows Error Text: The system cannot find the path specified.

Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521

- Context --
sqls::HostSetupPackageInstallerSynch:ostCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539

|||

Hi,

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=175249&SiteID=17

I'm bit confused too but this may solve your problem.

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

|||

Mayur

This may have some bearing on my problem. Yesterday, because I was having problems updating SQLExpress with SP2, I decided to uninstall SQL Server entirely. However, I did NOT remove the various MSSQL* sub-directories. Could it be that SQL Express is getting confused with which of these it should instantiate? The sub-directories I have now are:-

MSSQL - containing what looks like my SQL Express databases - this was previously a MSDE2000 instance.

MSSQL.1 - containing what looks to be the SQL Standard edition databases. This has an OLAP sub-directory.

MSSQL.2 - does not contain any databases. This instance does have Reporting Services and OLAP sub-directories.

MSSQL.3 - also does not contain any databases.

MSSQL.4 - seems to be only Reporting Services.

MSSQL.5 - has some empty default databases.

Do you think that I should re-install SQL Server SE and SQL Server Express again, having removed the entire directory structure again? (clearly after backing up the databases I need - which I did do yesterday, of course).

|||

Hi,

I too think that, it would be a great solution. Also remove all SQL Client tools, SQL-XML and other tools that gets installed with SQL. There is no specific order in which you can install SQL Server's diff editions. However, I would recommend from older to newer and Express edition first before SQL SE 2005.

I guess, this will solve your problem.

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

sql

Moving the location of an MSDE database?

My friend has installed a copy of SBS Standard and is using SharedPortal Server which is using MSDE to store its data. As he expects the database to grow, he wishes to move the files off the C-drive (the default location) to a larger data drive.
How do you go about backing up and moving MSDE database's to a new location?
Any help would be much appreciated.
Thank you in advance.
Simon
hi Simon,
"Simon M" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:CD922A26-B656-4AD1-928F-FD18D08564DC@.microsoft.com...
> My friend has installed a copy of SBS Standard and is using SharedPortal
Server which is using MSDE to store its data. As he expects the database to
grow, he wishes to move the files off the C-drive (the default location) to
a larger data drive.
> How do you go about backing up and moving MSDE database's to a new
location?
> Any help would be much appreciated.
> Thank you in advance.
>
you can achive the desired result both restoring a database backp to a new
location and/or detaching/reattaching the dbs..
here you can find some useful info...
Moving DB's between Servers
http://www.support.microsoft.com/?id=314546
Moving SQL Server Databases to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=224071
Using WITH MOVE in a Restore
http://support.microsoft.com/?id=221465
Restoring a .mdf
http://www.sqlservercentral.com/scri...p?scriptid=599
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Detach the database, move the MDF/LDF files, attach the database.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Simon M" <anonymous@.discussions.microsoft.com> wrote in message
news:CD922A26-B656-4AD1-928F-FD18D08564DC@.microsoft.com...
> My friend has installed a copy of SBS Standard and is using SharedPortal
> Server which is using MSDE to store its data. As he expects the database
> to grow, he wishes to move the files off the C-drive (the default
> location) to a larger data drive.
> How do you go about backing up and moving MSDE database's to a new
> location?
> Any help would be much appreciated.
> Thank you in advance.
> Simon
>

Moving tempdb onto a faster drive

Hello all ...

is there a standard procedure or document that explains how to:

Expand tempdb onto a faster drive ... making it larger

then ...

Remove the small portion of tempdb from my c:\ drive to reduce contention?

Thanks!

Doug

So you want to move tempdb to a new location, correct? This should work on SQL 2005, it might work on SQL 2000 as well. See topic "Moving System Databases" in SQL 2005 books online: http://msdn2.microsoft.com/en-us/library/ms345408.aspx

|||

Yup, exactly what I wanted ... move tempdb on to a larger, faster drive with no contention w/ the Windows OS and paging.

Thanks so much!

DB

moving system databases

Hi all.
Long story, I have a clustered SQL Server 2005 Standard Edition that is
using a SAN. We have just added more drives to our SAN and I need to move
the system database off the current drive to another drive. I have read some
others that have too have asked the same question. And Article ID 224071
keeps coming up. Well I just tried following this article this morning on my
beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
production and after I tried changing the startup parameters and tried
starting SQL server instance backup I received the following error.
FCB::Open: Operating system error 2(The system cannot find the file
specified.) occurred while creating or opening file 'F:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
Diagnose and correct the operating system error, and retry the operation.
And after a Google search I ran across an article out on MSDN, saying that
you need to use a ';' in between the parameters.
http://msdn2.microsoft.com/en-us/library/ms190699.aspx
I had to use SQL Server Configuration Manager to change the startup
parameters because there was no 'startup parameters' under the general tab
under Enterprise Manager (I had 2 other people check the steps out too and
they couldn't find it either).
Did I do something wrong? Should there be ';' between the parameters or not?
Thanks in advance!
Kris
If it helps, my SQL 2005 startup parameters from teh Config manager:
-dC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
Or check in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\MSSQLServer\Parameters
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
> Hi all.
> Long story, I have a clustered SQL Server 2005 Standard Edition that is
> using a SAN. We have just added more drives to our SAN and I need to move
> the system database off the current drive to another drive. I have read
> some
> others that have too have asked the same question. And Article ID 224071
> keeps coming up. Well I just tried following this article this morning on
> my
> beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
> production and after I tried changing the startup parameters and tried
> starting SQL server instance backup I received the following error.
> FCB::Open: Operating system error 2(The system cannot find the file
> specified.) occurred while creating or opening file 'F:\Program
> Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
> Diagnose and correct the operating system error, and retry the operation.
> And after a Google search I ran across an article out on MSDN, saying that
> you need to use a ';' in between the parameters.
> http://msdn2.microsoft.com/en-us/library/ms190699.aspx
> I had to use SQL Server Configuration Manager to change the startup
> parameters because there was no 'startup parameters' under the general tab
> under Enterprise Manager (I had 2 other people check the steps out too and
> they couldn't find it either).
> Did I do something wrong? Should there be ';' between the parameters or
> not?
> Thanks in advance!
> Kris
>
|||OK by adding in the ';' between the parameters via Config Manager I am now
getting the following message when I try to connect to the server after I
restart the instance backup.
Cannot connect to 'servername'
Login failed for user 'sa'. Reason: Server is in single user mode. Only
one administrator can connect at this time. (Microsoft SQL Server, Error:
18461)
I even went to the length to unplugg the network cable and restart with
server off the network and I still received the same error. Only database I
was moving at the time was 'Model' using the procedures of Article ID 224071.
Doing another search I found a tech net artilce telling of another want to
move all system databases other then master and resources
http://technet.microsoft.com/en-us/library/ms345408.aspx
, which is different then 224071. Any ideas and help is great!
Thanks again!
Kris
"Tibor Karaszi" wrote:

> It depend son what tool you are using. In Config Manager: Yes.
> In RegEdit: No, since each parameter has it's own key.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
> news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
>

moving system databases

Hi all.
Long story, I have a clustered SQL Server 2005 Standard Edition that is
using a SAN. We have just added more drives to our SAN and I need to move
the system database off the current drive to another drive. I have read som
e
others that have too have asked the same question. And Article ID 224071
keeps coming up. Well I just tried following this article this morning on m
y
beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
production and after I tried changing the startup parameters and tried
starting SQL server instance backup I received the following error.
FCB::Open: Operating system error 2(The system cannot find the file
specified.) occurred while creating or opening file 'F:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
Diagnose and correct the operating system error, and retry the operation.
And after a Google search I ran across an article out on MSDN, saying that
you need to use a ';' in between the parameters.
http://msdn2.microsoft.com/en-us/library/ms190699.aspx
I had to use SQL Server Configuration Manager to change the startup
parameters because there was no 'startup parameters' under the general tab
under Enterprise Manager (I had 2 other people check the steps out too and
they couldn't find it either).
Did I do something wrong? Should there be ';' between the parameters or not
?
Thanks in advance!
KrisIf it helps, my SQL 2005 startup parameters from teh Config manager:
-dC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
Or check in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
Server\MSSQL.1\MSSQLServer\Parameters
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
> Hi all.
> Long story, I have a clustered SQL Server 2005 Standard Edition that is
> using a SAN. We have just added more drives to our SAN and I need to move
> the system database off the current drive to another drive. I have read
> some
> others that have too have asked the same question. And Article ID 224071
> keeps coming up. Well I just tried following this article this morning on
> my
> beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
> production and after I tried changing the startup parameters and tried
> starting SQL server instance backup I received the following error.
> FCB::Open: Operating system error 2(The system cannot find the file
> specified.) occurred while creating or opening file 'F:\Program
> Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
> Diagnose and correct the operating system error, and retry the operation.
> And after a Google search I ran across an article out on MSDN, saying that
> you need to use a ';' in between the parameters.
> http://msdn2.microsoft.com/en-us/library/ms190699.aspx
> I had to use SQL Server Configuration Manager to change the startup
> parameters because there was no 'startup parameters' under the general tab
> under Enterprise Manager (I had 2 other people check the steps out too and
> they couldn't find it either).
> Did I do something wrong? Should there be ';' between the parameters or
> not?
> Thanks in advance!
> Kris
>|||> Should there be ';' between the parameters or not?
It depend son what tool you are using. In Config Manager: Yes.
In RegEdit: No, since each parameter has it's own key.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
> Hi all.
> Long story, I have a clustered SQL Server 2005 Standard Edition that is
> using a SAN. We have just added more drives to our SAN and I need to move
> the system database off the current drive to another drive. I have read s
ome
> others that have too have asked the same question. And Article ID 224071
> keeps coming up. Well I just tried following this article this morning on
my
> beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
> production and after I tried changing the startup parameters and tried
> starting SQL server instance backup I received the following error.
> FCB::Open: Operating system error 2(The system cannot find the file
> specified.) occurred while creating or opening file 'F:\Program
> Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
> Diagnose and correct the operating system error, and retry the operation.
> And after a Google search I ran across an article out on MSDN, saying that
> you need to use a ';' in between the parameters.
> http://msdn2.microsoft.com/en-us/library/ms190699.aspx
> I had to use SQL Server Configuration Manager to change the startup
> parameters because there was no 'startup parameters' under the general tab
> under Enterprise Manager (I had 2 other people check the steps out too and
> they couldn't find it either).
> Did I do something wrong? Should there be ';' between the parameters or n
ot?
> Thanks in advance!
> Kris
>|||OK by adding in the ';' between the parameters via Config Manager I am now
getting the following message when I try to connect to the server after I
restart the instance backup.
Cannot connect to 'servername'
Login failed for user 'sa'. Reason: Server is in single user mode. Only
one administrator can connect at this time. (Microsoft SQL Server, Error:
18461)
I even went to the length to unplugg the network cable and restart with
server off the network and I still received the same error. Only database I
was moving at the time was 'Model' using the procedures of Article ID 224071
.
Doing another search I found a tech net artilce telling of another want to
move all system databases other then master and resources
http://technet.microsoft.com/en-us/...y/ms345408.aspx
, which is different then 224071. Any ideas and help is great!
Thanks again!
Kris
"Tibor Karaszi" wrote:

> It depend son what tool you are using. In Config Manager: Yes.
> In RegEdit: No, since each parameter has it's own key.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
> news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
>

moving system databases

Hi all.
Long story, I have a clustered SQL Server 2005 Standard Edition that is
using a SAN. We have just added more drives to our SAN and I need to move
the system database off the current drive to another drive. I have read some
others that have too have asked the same question. And Article ID 224071
keeps coming up. Well I just tried following this article this morning on my
beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
production and after I tried changing the startup parameters and tried
starting SQL server instance backup I received the following error.
FCB::Open: Operating system error 2(The system cannot find the file
specified.) occurred while creating or opening file 'F:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
Diagnose and correct the operating system error, and retry the operation.
And after a Google search I ran across an article out on MSDN, saying that
you need to use a ';' in between the parameters.
http://msdn2.microsoft.com/en-us/library/ms190699.aspx
I had to use SQL Server Configuration Manager to change the startup
parameters because there was no 'startup parameters' under the general tab
under Enterprise Manager (I had 2 other people check the steps out too and
they couldn't find it either).
Did I do something wrong? Should there be ';' between the parameters or not?
Thanks in advance!
KrisIf it helps, my SQL 2005 startup parameters from teh Config manager:
-dC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
Or check in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\MSSQLServer\Parameters
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
> Hi all.
> Long story, I have a clustered SQL Server 2005 Standard Edition that is
> using a SAN. We have just added more drives to our SAN and I need to move
> the system database off the current drive to another drive. I have read
> some
> others that have too have asked the same question. And Article ID 224071
> keeps coming up. Well I just tried following this article this morning on
> my
> beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
> production and after I tried changing the startup parameters and tried
> starting SQL server instance backup I received the following error.
> FCB::Open: Operating system error 2(The system cannot find the file
> specified.) occurred while creating or opening file 'F:\Program
> Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
> Diagnose and correct the operating system error, and retry the operation.
> And after a Google search I ran across an article out on MSDN, saying that
> you need to use a ';' in between the parameters.
> http://msdn2.microsoft.com/en-us/library/ms190699.aspx
> I had to use SQL Server Configuration Manager to change the startup
> parameters because there was no 'startup parameters' under the general tab
> under Enterprise Manager (I had 2 other people check the steps out too and
> they couldn't find it either).
> Did I do something wrong? Should there be ';' between the parameters or
> not?
> Thanks in advance!
> Kris
>|||> Should there be ';' between the parameters or not?
It depend son what tool you are using. In Config Manager: Yes.
In RegEdit: No, since each parameter has it's own key.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
> Hi all.
> Long story, I have a clustered SQL Server 2005 Standard Edition that is
> using a SAN. We have just added more drives to our SAN and I need to move
> the system database off the current drive to another drive. I have read some
> others that have too have asked the same question. And Article ID 224071
> keeps coming up. Well I just tried following this article this morning on my
> beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
> production and after I tried changing the startup parameters and tried
> starting SQL server instance backup I received the following error.
> FCB::Open: Operating system error 2(The system cannot find the file
> specified.) occurred while creating or opening file 'F:\Program
> Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
> Diagnose and correct the operating system error, and retry the operation.
> And after a Google search I ran across an article out on MSDN, saying that
> you need to use a ';' in between the parameters.
> http://msdn2.microsoft.com/en-us/library/ms190699.aspx
> I had to use SQL Server Configuration Manager to change the startup
> parameters because there was no 'startup parameters' under the general tab
> under Enterprise Manager (I had 2 other people check the steps out too and
> they couldn't find it either).
> Did I do something wrong? Should there be ';' between the parameters or not?
> Thanks in advance!
> Kris
>|||OK by adding in the ';' between the parameters via Config Manager I am now
getting the following message when I try to connect to the server after I
restart the instance backup.
Cannot connect to 'servername'
Login failed for user 'sa'. Reason: Server is in single user mode. Only
one administrator can connect at this time. (Microsoft SQL Server, Error:
18461)
I even went to the length to unplugg the network cable and restart with
server off the network and I still received the same error. Only database I
was moving at the time was 'Model' using the procedures of Article ID 224071.
Doing another search I found a tech net artilce telling of another want to
move all system databases other then master and resources
http://technet.microsoft.com/en-us/library/ms345408.aspx
, which is different then 224071. Any ideas and help is great!
Thanks again!
Kris
"Tibor Karaszi" wrote:
> > Should there be ';' between the parameters or not?
> It depend son what tool you are using. In Config Manager: Yes.
> In RegEdit: No, since each parameter has it's own key.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Kris McCarty" <Kris McCarty@.discussions.microsoft.com> wrote in message
> news:AE19C53B-7F0E-4A33-AF14-85748AAF7559@.microsoft.com...
> > Hi all.
> >
> > Long story, I have a clustered SQL Server 2005 Standard Edition that is
> > using a SAN. We have just added more drives to our SAN and I need to move
> > the system database off the current drive to another drive. I have read some
> > others that have too have asked the same question. And Article ID 224071
> > keeps coming up. Well I just tried following this article this morning on my
> > beta server (SQL 2005 Dev Edition) to ensure things would go smoothly on
> > production and after I tried changing the startup parameters and tried
> > starting SQL server instance backup I received the following error.
> >
> > FCB::Open: Operating system error 2(The system cannot find the file
> > specified.) occurred while creating or opening file 'F:\Program
> > Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -m -T3608'.
> > Diagnose and correct the operating system error, and retry the operation.
> >
> > And after a Google search I ran across an article out on MSDN, saying that
> > you need to use a ';' in between the parameters.
> > http://msdn2.microsoft.com/en-us/library/ms190699.aspx
> >
> > I had to use SQL Server Configuration Manager to change the startup
> > parameters because there was no 'startup parameters' under the general tab
> > under Enterprise Manager (I had 2 other people check the steps out too and
> > they couldn't find it either).
> >
> > Did I do something wrong? Should there be ';' between the parameters or not?
> >
> > Thanks in advance!
> > Kris
> >
>

Moving SQL server installation from one Drive letter to another.

I'm hoping you can help a newbie with a quick question. I need to move
an installation of SQL server 2000 sp3a on a Win2003 Standard server
from the C Drive to the D drive. I'm running out of room on the C Drive
and have more then enough room on the D drive. I know you can detach
databases and move the files and attach them again but I'm looking to
move the whole "C:\Program Files\Microsoft SQL Server" folder to
"D:\Program Files\Microsoft SQL Server"
Is this possible and if so how do you do it? I've seen web pages on how
to move an installation of SQL server from one server to another but
that is not what I'm needing to do.
Thanks in advance,
NathanMoving the complete folder \Program Files\Microsoft SQL Server will pretty
much require a reinstall, if you want to be safe. Just moving the data and
log files ( see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224071) and the
backups, will leave with a more or less basic install of SQL Server, which
takes about 250 MB. That might solve your needs.
--
Jacco Schalkwijk
SQL Server MVP
<nbheck@.hotmail.com> wrote in message
news:1111037005.791634.315720@.z14g2000cwz.googlegroups.com...
> I'm hoping you can help a newbie with a quick question. I need to move
> an installation of SQL server 2000 sp3a on a Win2003 Standard server
> from the C Drive to the D drive. I'm running out of room on the C Drive
> and have more then enough room on the D drive. I know you can detach
> databases and move the files and attach them again but I'm looking to
> move the whole "C:\Program Files\Microsoft SQL Server" folder to
> "D:\Program Files\Microsoft SQL Server"
> Is this possible and if so how do you do it? I've seen web pages on how
> to move an installation of SQL server from one server to another but
> that is not what I'm needing to do.
> Thanks in advance,
> Nathan
>

Moving SQL server installation from one Drive letter to another.

I'm hoping you can help a newbie with a quick question. I need to move
an installation of SQL server 2000 sp3a on a Win2003 Standard server
from the C Drive to the D drive. I'm running out of room on the C Drive
and have more then enough room on the D drive. I know you can detach
databases and move the files and attach them again but I'm looking to
move the whole "C:\Program Files\Microsoft SQL Server" folder to
"D:\Program Files\Microsoft SQL Server"
Is this possible and if so how do you do it? I've seen web pages on how
to move an installation of SQL server from one server to another but
that is not what I'm needing to do.
Thanks in advance,
Nathan
Moving the complete folder \Program Files\Microsoft SQL Server will pretty
much require a reinstall, if you want to be safe. Just moving the data and
log files ( see
http://support.microsoft.com/default...;en-us;Q224071) and the
backups, will leave with a more or less basic install of SQL Server, which
takes about 250 MB. That might solve your needs.
Jacco Schalkwijk
SQL Server MVP
<nbheck@.hotmail.com> wrote in message
news:1111037005.791634.315720@.z14g2000cwz.googlegr oups.com...
> I'm hoping you can help a newbie with a quick question. I need to move
> an installation of SQL server 2000 sp3a on a Win2003 Standard server
> from the C Drive to the D drive. I'm running out of room on the C Drive
> and have more then enough room on the D drive. I know you can detach
> databases and move the files and attach them again but I'm looking to
> move the whole "C:\Program Files\Microsoft SQL Server" folder to
> "D:\Program Files\Microsoft SQL Server"
> Is this possible and if so how do you do it? I've seen web pages on how
> to move an installation of SQL server from one server to another but
> that is not what I'm needing to do.
> Thanks in advance,
> Nathan
>

Moving SQL server installation from one Drive letter to another.

I'm hoping you can help a newbie with a quick question. I need to move
an installation of SQL server 2000 sp3a on a Win2003 Standard server
from the C Drive to the D drive. I'm running out of room on the C Drive
and have more then enough room on the D drive. I know you can detach
databases and move the files and attach them again but I'm looking to
move the whole "C:\Program Files\Microsoft SQL Server" folder to
"D:\Program Files\Microsoft SQL Server"
Is this possible and if so how do you do it? I've seen web pages on how
to move an installation of SQL server from one server to another but
that is not what I'm needing to do.
Thanks in advance,
NathanMoving the complete folder \Program Files\Microsoft SQL Server will pretty
much require a reinstall, if you want to be safe. Just moving the data and
log files ( see
http://support.microsoft.com/defaul...b;en-us;Q224071) and the
backups, will leave with a more or less basic install of SQL Server, which
takes about 250 MB. That might solve your needs.
Jacco Schalkwijk
SQL Server MVP
<nbheck@.hotmail.com> wrote in message
news:1111037005.791634.315720@.z14g2000cwz.googlegroups.com...
> I'm hoping you can help a newbie with a quick question. I need to move
> an installation of SQL server 2000 sp3a on a Win2003 Standard server
> from the C Drive to the D drive. I'm running out of room on the C Drive
> and have more then enough room on the D drive. I know you can detach
> databases and move the files and attach them again but I'm looking to
> move the whole "C:\Program Files\Microsoft SQL Server" folder to
> "D:\Program Files\Microsoft SQL Server"
> Is this possible and if so how do you do it? I've seen web pages on how
> to move an installation of SQL server from one server to another but
> that is not what I'm needing to do.
> Thanks in advance,
> Nathan
>

Moving sql 2000 DTS packages to sql 2005 standard edition

I have been tasked with upgrading around 150 SQL Server 2000 DTS packages to SSIS in SQL Server 2005 standard edition. I made a backup of the 2000 database upon which the DTS packages operate and restored it to the SQL 2005 server. So far, so good. I have the database in place. Now I need to get the DTS packages themselves into the SLQ 2005 server. I think I need to check my install and make sure that I have the SQL Server 2000 DTS services installed on the SQL 2005 server. I can do that.

However, I wonder what would be the most effective way to physically get the packages from the SQL 2000 server to the SQL 2005 server. Should I use structured storage files? If so, how do I go about opening them in SQL 2005 in order to save them to SQL server 2005?

I should mention that these packages make heavy use of ActiveX scripting so I am looking at rewriting them from scratch to be SSIS packages. I just need the packages on the SQL Server 2005 box so I can make sure I am creating exactly the same functionality in 2005 as existed in SQL server 2000. Each DTS 2000 individual package tends to be fairly simple and I think I can greatly improve the process by consolidating them.

Thanks in advance for any advice.

S. Wells

You'll need the DTS2000 editor by teh sounds of it. Downloadable from here: http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

-Jamie

|||

Thanks Jamie,

It does appear that this will give me what I need. I had read another, earlier, post on the forum that indicated the legacy components did not have to be separately installed now that 2005 is in production release if one had chosen to install integration services. I did not realize that the designer was not installed as part of the legacy DTS components install. I looked all over the BI interface and could not see where I could open a DTS package and then save it to SQL 2005.

Again, thanks.

S. Wells

|||

Just a quick note to say that there is a new version (an update to the previous link):

Instead of:

Feature Pack for Microsoft SQL Server 2005 - November 2005
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Download from:

Feature Pack for Microsoft SQL Server 2005 - April 2006
http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en

6th item down:

Microsoft SQL Server 2000 DTS Designer Components

The Microsoft SQL Server 2000 Data Transformation Services (DTS) package designer is a design tool used by developers and administrators of SQL Server 2005 servers to edit and maintain existing DTS packages until they can be upgraded or recreated in the SQL Server 2005 Integration Services package format. After installing this download, SQL Server 2005 users can continue to edit and maintain existing DTS packages from the Object Explorer in SQL Server 2005 Management Studio and from the Execute DTS 2000 Package Task Editor in Business Intelligence Development Studio, without needing to reinstall the SQL Server 2000 tools. The DTS package designer in this download was formerly accessed from the Data Transformation Services node in SQL Server 2000 Enterprise Manager.
Audience(s): Customer, Developer
X86 Package (SQLServer2005_DTS.msi) - 5088 KB

Also look at

SQL Server 2005 Books Online

SQL Server 2005 Integration Services Backward Compatibility
Updated: 17 July 2006
http://msdn2.microsoft.com/en-us/library/ms143706.aspx

General Compatibility between DTS and SSIS
Because Integration Services is an entirely new product, and not a version upgrade, you will not encounter software conflicts between DTS and SSIS.

You can install both DTS and SSIS on the same server.
You can run both DTS and SSIS packages on the same server when both products are installed. You can run DTS packages, even when the SQL Server 2000 tools are not present, by using an updated version of the DTS runtime that is installed with Integration Services.
You can save DTS packages in the MSDB database of a SQL Server 2000 or SQL Server 2005 instance. You can save SSIS packages only on a SQL Server 2005 instance.
You can edit DTS packages, even when the SQL Server 2000 tools are not present, by using an updated version of the DTS Designer that is available for download. You cannot edit DTS packages in Business Intelligence Development Studio. You can edit SSIS packages only in BI Development Studio.