instance of sql server

I am learning SQL Server 2005 and I was told to install a second instance of
SQL Server 2005 on my machine. How can I install a second instance of SQL
Server 2005 on my machine

I already installed SQL Server 2005, I guess this is my first instance. To
install a second instance, do I just run setup again?Yes, just run setup again to create a 'named' instance. Setup will ask you
for an instance name.

A computer can have up to 1 default instance (probably what you installed
initially) but many named instances. To connect to the default instance
after installation, specify only the computer name. For the named instance,
specify computer name and instance name separated by a backslash
('ComputerName\InstanceName').

--
Hope this helps.

Dan Guzman
SQL Server MVP

"David" <david_vcp@.hotmail.com> wrote in message
news:bMKdnc_BtsngZ9fZRVn-rg@.comcast.com...
>I am learning SQL Server 2005 and I was told to install a second instance
>of SQL Server 2005 on my machine. How can I install a second instance of
>SQL Server 2005 on my machine
> I already installed SQL Server 2005, I guess this is my first instance.
> To install a second instance, do I just run setup again?

Installing SQL Server 2005 Developer Edition 64-bit extended on Windows 2003 SP2 cluster

Hello

I've installed Windows 2003 SP2 in a stand-alone cluster (will be adding a second node later). I'm now installing SQL Server 2005 Developer Edition 64-bit extended and would like to have the "Create a SQL Server Failover Cluster" box to not be grayed out. Even when I check the "SQL Server Database Services" box, it still has the cluster box grayed out.

Any idea's?

TIA!

Have you created and configured the cluster service (MSCS)?|||This is resolved. As per usual, SQL 2005 seems to install with more success when you copy the cabs local to the machine, and then run setup (versus over the network).thank anyways Arnie.

Integer datatype question

I have a column setup using the Int datatype and a length of 4. First: does this mean that the allowable range is from -9999 to 9999? Second: I can't seem to change the 4 to anything else, how can I modify the length :confused:That's the internaly stored length...

Look up datatypes in books online...

int is actually

Integer (whole number) data from -2^31 (-2,147,483,648) through 2^31 - 1 (2,147,483,647).|||no, the 4 indicates the amount of bytes used. It's a fixed size, you can't change it. As specified by BOL, integer values '(...)from -2^63 (-9,223,372,036,854,775,808) through 2^63-1 (9,223,372,036,854,775,807).'. If this won't do use a bigint instead.

EDIT: Brett, I'll quote you on this: Damn...sniped again

Installing SQL Express 2K5 on a domain controller?

I want to install SQL Express 2K5 on a lightly used second Windows 2003 SP1 DC. I know about the warning not to do this type of install. However, the group is small and their budget does not allow for another server just for one application. With that being said, the error message I keep getting is "can't create local groups......" (I know that you do not have local groups with AD). So, is there a work around to this issue or can someone point me in the right direction as how to install on a domain controller? Thanks in advance for your time!!!

hi,

please have a look at http://download.microsoft.com/download/f/1/0/f10c4f60-630e-4153-bd53-c3010e4c513b/ReadmeSQLEXP2005.htm, paragraph 3.10

regards

|||

Andrea,

Thanks for the link, however that is the reason for the post. Paragrph 3.10 states "

3.10 Installing SQL Server Express on a Windows Domain Controller

Security Note:

We recommend against running SQL Server Express on a domain controller.

It is possible to install SQL Server Express on a Windows domain controller; however, it cannot run on a Windows Server 2003 domain controller as Local Service or Network Service. SQL Server service accounts should run as Windows domain user accounts. It is also possible to install SQL Server service accounts to run as Local System, but this option is not recommended."

I just need to know how to get SQLExpress to install without trying to create local accounts and use a specific network user account. Again thanks for your time and effort.

|||

You will have to create specific domain accounts for the SQL Server Services -BEFORE you attempt to install. Here are some articles with information about what accounts are needed and why.

Configuration -Service Accounts, SQL Server 2005 - Setting Up Windows Service Accounts
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
http://msdn2.microsoft.com/en-us/library/ms143504.aspx

Configuration -Service Accounts, SQL Server or SQL Server Agent service account
http://support.microsoft.com/kb/283811/en-us
http://msdn2.microsoft.com/en-us/library/ms143691.aspx

Configuration -Service Accounts,Selecting an Account for the SQL Server Agent Service
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
http://support.microsoft.com/kb/907557

installing sql 2005 management studio express on 2nd hard drive

Hi,

I've downloaded the sql server 2005 management studio express executable to my second hard drive, as there is no room on my main drive

However, when I try to install, the program shows me both drives, and shows that there is not enough room on my main drive, but it does not allow me to change the installation to my second drive.

I have previously installed the main sql express product to my second drive with visual studio. There's loads of room.

Can anyone give me a clue as to why this might be happening.

Thanks

John

I'm going to move this to the Setup forum.

- Mike

INstalling sp3a on second node

I have a active/passive cluster with W2K Adv. and SQL 2000.
I was having the issue with setting up SQL on the second node. I fixed issue by installing directly onto the second node. But their is no option with the sp3a to install onto the second node locally. The same issue that happened with trying to remote inst
all with the primary node. The install failed because of a timeout issue. Error 121. All of my settings and correct accounts are setup. The person who told me to install directly on the second node to
install SQL stated that this was actually a known problem. What is the fix for the service packs if you cannot install remotely? It looks like sp3a installed correctly because when I ran query analyzer the version that showed up was sp3a. Any comments wou
ld be appreciated.
Thanks,
dcaldwell
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
There is no 'first node' and 'second node' concept in SQL 2000 clustering.
All nodes are equal. The only difference is what node is currently hosting
the instance. Adding and removing nodes is a different process and is well
documented in BOL. It sounds like you built the cluster on a single node or
applied the service pack with one node offline. Normal installation of SQL
Service packs will update all nodes at the same time if it is run from teh
node currently hosting the instance. If you need to reapply a service pack
to update binaries on a newly added or replaced node, you must run the
Service Pack from the 'new' node while hte SQL instance is hosted on an
'old' node. This is documented in the Service Pack readme file.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23%23T55iTgEHA.3272@.TK2MSFTNGP11.phx.gbl...
> I have a active/passive cluster with W2K Adv. and SQL 2000.
> I was having the issue with setting up SQL on the second node. I fixed
issue by installing directly onto the second node. But their is no option
with the sp3a to install onto the second node locally. The same issue that
happened with trying to remote install with the primary node. The install
failed because of a timeout issue. Error 121. All of my settings and correct
accounts are setup. The person who told me to install directly on the second
node to
> install SQL stated that this was actually a known problem. What is the fix
for the service packs if you cannot install remotely? It looks like sp3a
installed correctly because when I ran query analyzer the version that
showed up was sp3a. Any comments would be appreciated.
> Thanks,
> dcaldwell
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||What do you mean by "I fixed issue by installing directly onto the second
node. "
Did you install a local, non-clustered installation on the second node?
Perhaps now is a time to uninstall that local copy, and reinstall back as a
virtual SQL Server. You can find a clustering installation white paper at:
http://www.microsoft.com/technet/pro.../failclus.mspx
Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.
This posting is provided "as is" with no warranties and confers no rights.