(Complete newbie) Please help! Installation problem (I think)

Hello,

I most likely am being incredibly stupid here, but I have installed SQL 2005 Enterprise and Service Pack 2 on my Acer laptop running Vista Business and cannot for the life of me figure out how to start the thing.

When I hit the start button on the toolbar, and go to Microsoft SQL Server 2005, there is one folder that expands down called Configuration Tools. This has the options Notification Services, Configuration Management, Error and Usage Reports, and Surface Area Configuration. But no where can I find an icon that actually starts the database thing so I can create a database and learn some SQL stuff.

I would be most grateful if anybody could point out where I am going wrong or if there is anything I need to do.

Many thanks,

Chima

The default installation does NOT install the client tools.

Using the install media, run Setup again, and this time choose Client Tools.

|||Marvellous thanks Arnie!

"Your upgrade is blocked"

I am getting the following error message when I tried installing the 2005 Developer Edition from the MSDN kit. I previously installed the 2005 Express Edition, and it worked just fine, so I thought that the install failed as it was at a lower version than the Express Edition. I uninstalled the SQLExpress Edition, however, when I try to install SQL Server 2005 again, I get the following message:

Name: Microsoft SQL Server 2005 Tools

Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:

Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

Name: Microsoft SQL Server 2005 Tools

Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:

Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

I have also installed Visual Studio NET, and I wonder if some component in the Studio app is holding back the SQL Server install. I have uninstalled all SQL components several times already, and I keep on getting this message.

Gregory

Gregory

Gregory, when you go to Add/Remove Programs, do you see any SQL 2005 installation info there? If so, what versions does the report say?

Also, what version of SQL Server Express did you install? RTM or SP1?

Thanks,
Samuel Lester (MSFT)

sql

"Upgrade" from 2000 to 2005, version still says 8.0.2039

I just installed 2005 and accepted all the defaults to upgrade the default instance of 2000 as prompted. However, when I open the SQL Server Mgnt Studio, my server shows 8.0.2039 as the version which is 2000, and I can't restore a backup from another 2005 server, because it gives an error message like it still thinks its 2000. The whole installation process went fine including sp1. I looked in Services to see if there was more than one instance of SQL Server, and there isn't. Also, all my database files are still in the old 2000 (mssql\data) directory. Any ideas, solutions? Thanks.

Michael

I have the same problem. It's like the upgrade didn't totally happen. The new Management studio is installed, but the 2005 specific progs don't work. Like the surface area configure program errors when started since it can't find any 2005 servers installed.

|||

Here's the response that I received from someone else on another forum that was kind enough to reply and it also worked. I simply stopped the 2000 service, and reinstalled. You would think that the installer would do this for you, but oh well. HTH

Before you update to 2005, you have to stop the 2000 version. If you don’t, the code to start 2005 is not installed and the code for starting and stopping 2000 will remain on the server. Thus 2000 will always be started and not 2005. Hope this helps.

Try stopping 2000 and reinstalling 2005.

|||

That's correct, since files are always in use, you need to restart the services for both versions to get the full upgrade to work.

Thanks,
Sam Lester (MSFT)

|||

So to be clear...

I don't have to uninstall either version now. All I have to do is stop all of the current SQL services that are running. Then re-insert the 2005 disc, and it will re-upgrade over itself? ( I don't want a new instace installed, I literally wanted the upgrade so that only one version would be on the machine )

Is there a way to do this without putting the disc back in? i.e. Are all of the files present since I tried to upgrade the first time. So now, I could just stop the services and use some other method to get it to reinstall all new files and services over itself? Or do I have to physically reinsert the disc to follow normal steps?

|||I did not uninstall anything. I just stopped the 2000 service, then reinserted the CD and reinstalled 2005 exactly as I did before, with the intent of upgrading (i.e. replacing) 2000. After completion, I may have had to start the MSSQLServer service manually and set to automatic, can't remember, but after that everything was just fine, and there only appears to be one instance/service (2005).|||Thanks much...I am clear now. I will try this tonight. Since I am about to do this...did you have any surprises or "gotchas" that you can warn me about? Anything that worked before then didn't work after? Also, did you do any timing studies to verify if the 2005 is faster than the 2000? I have heard that the BULK INSERTS are speed improved, but have not seen any benchmarks or other data on speed increases. Just wondering if you noticed some benefits and/or have data on the improvements. Thanks again for the help, glad you were still watching this thread even though you already got the answer elsewhere.|||

There seems to be a hitch. I stopped all of the SQL services. Pop in the disc, begin the install process.

First snafu...

The installer knows that my current install, 2005 Workgroup with SP1, is newer than the version I have on the disc, so it blocks the install. A small report window appears saying I can avoid this problem by installing from the command line and using the SKUUPGRADE=1 parameter. So, I open "Run..." from the start button. I run "F:\Setup.exe SKUUPGRADE=1" The installer begins, but...

Second snafu...

I eventually get to the part where I select the services to install. I choose all services and select the "All components will be installed" option for all of them. I tell it "default instance". Then the installer tells me that it can't continue since all of the components are already installed. Forced to exit.

Am I doing something wrong? Is there a way to just re-install without these problems?

|||

Hi Sam:

Thanks for trying to help...but, your response is not clear, you first say "That's correct" which makes me think that you agree with the info that came from the previous post, the one that says to stop SQL 2000 services and re-install 2005. But, then your post goes on to say "restart both services for both versions", which is not the same as stopping SQL 2000 then reinstalling 2005. Which is it?

Also, if you read my other posts in this thread, the "stop 2000 services and re-install 2005" does not work. The installer will not allow a "re-install" since it sees that 2005 is already installed...furthermore, when using the SKUUPGRADE=1 which is supposed to skip this problem, the installer stops since all of the programs are already installed.

Please help...I am still stuck in the same spot and not sure how to proceed. I suppose I could just uninstall all of the 2005 programs then try all this again...but I was hoping that there was an easier and less time consuming solution.

Thanks in advance.

|||

Sorry for not having a more direct answer, but can you read through this forum thread regarding SQL 2000 and 2005 on the same box and see if it applies to your situation?

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

Thanks,
Sam Lester (MSFT)

|||

Sorry Sam, this doesn't seem to be the problem I am having. The problem I am having is explained in all of the previous posts in this thread. A SQL 2005 upgrade from SQL 2000 appears to have worked, but it didn't. The version number still shows 8.00.2039 and the SQL 2005 Tools say that there is no 2005 instance on the machine. The other posts here explained how to fix this, but the fix doesn't work since the installer program sees the previous SQL 2005 install on the machine, it won't allow another install to cover over it.

But, since I read the other forum, now I am worried about trying to uninstall SQL 2005 and try again.

Please help if you have any other ideas or point me in the right direction for other resources that may know what to do.

Thanks

|||I am also having the very same problems to the "T". It is also causing a new installation of Reporting Services from properly initializing on the server. It complains about a version problem.

It would seem the next logical step would be to somehow get the databases converted, but outside of doing an upgrade from the SQL Server 2005 setup disk, I cannot find any good documentation on how to do this.

Any help with this problem would be greatly appreciated. I am at wits end.

"The feature(s) specified are not valid for this edition of SQL Server" error when ins

I've successfully installed SQL Server 2005 Standard Edition on an Enterprise edition of Windows Server 2003 x64. I'm now (and also tried & failed during the install of the database engine) attempting to install the "Management Tools" component on the same server. However, in all my attempts to do so, I receive the following error:

The feature(s) specified are not valid for this edition of SQL Server

The message box does not list the features that are not valid but since the only item I've selected to install is the "Management Tools" option under "Client Components" it obviously points to something with that.

Am I missing something or are the Management Tools not supported in my config - most notably SQL Server 2005 Standard edition running on Windows Server 2003 x64?

Thanks.

- Lance

Colorado State University

I was finally able to install the "Management Tools" with a pretty simple solution: Install using the installer files directly off of the physical DVD. My prior attempts had all been using a copy of the files on the DVD stored locally on the server. Incidently, I had used the same copied files to successfully install the DB engine and SSIS. Go figure.

"SQL Server Management Studio Express" install location

I just installed the "SQL Server Management Studio Express" but it didn't tell me where it was installed. How do I get the application started ?A short-cut should have been add to ALL Programs | Microsoft SQL Server 2005 | SQL Server Management Studio Express CTP.

Peter|||found it here

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe"

"Process Update" and "Process Incremental" no longer supported for SQL 2005

I've installed SQL 2005 service pack 1, and I found that process update and process incremental is disappeared in the process option. Is this no longer supported?

Thanks!

Kelvin Jor

There got to be some mistake. What object you are talking about.

Different objects have different processing options applied to them.

Take a look at this paper, it has a table listing objects and options applied to them: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5_asprocarch.asp

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"None of the selected features can be installed" error on SQL 2005 Cluster

Hey All,

I installed SQL 2005 on a cluster. Everything on the primary node works fine. However, as the documentation suggests, the SQL Management Studio (and other tools) are not installed on the standby node by default. However, when I go to try and install on the 2nd node I get the following error:

TITLE: Microsoft SQL Server Setup

None of the selected features can be installed or upgraded. Setup cannot proceed since no effective change is being made to the machine. To continue, click Back and then select features to install. To exit SQL Server Setup, click Cancel.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28108

The link is referencing something about requiring a complex SA password. I can verify that the directory structure on node 1 where the management studio and client tools exist does not exist on node 2. I'm at wits end here, I've tried uninstalling/reinstalling/everything.

Anyone have any ideas?

thanks!

I finally figured it out... Although the original install didn't actually install any of the tools on the 2nd node, it did create a "tools" directory on the 2nd node. I renamed this directory and then went to try and install the tools and it worked. Evidently the SQL setup was just looking to see if this directory existed.

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!
The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

"Enable user SQL instances"

Hi I have Visual Studio 2005 with SP1 installed, and I want to install the Management Studio. I tried many times installing that and I always got the same problem, which is when I try to create a database in VS I just don’t get trough as I used to. A message appears saying that I’ve to enable some estance. So to resolve the problem I saw if is everything ok with the SQL Server, which seemed to be fine, but I couldn’t start the Report service.

Now I just formatted the computer and I’m afraid to happen all over again. May be the version with only the Management would be fine, I don’t know if it adds something beside of that.

Thank you very much.

After installing Express, you need to explicitly enable remote connections. Is this the issue you are seeing? If not, please supply an exact error message or a log snippet showing the problem.

Thanks,
Sam Lester (MSFT)

|||

Was about "Enable user SQL instances" and the Report Service didn’t started too.

How do I enable this remote connections?

And in the instalation, Should I Add a user to the SQL Server Administration Role?

And also in the step "ready to install" of the SQL Server SP2 shows the following:

The following components will be installed:

· SQL Server Database Services (Upgrade)

(Database Services, Replication, Full-Text Search)

· Reporting Services

(Reporting Services, Report Manager)

· Client Components (Upgrade)

(Connectivity Components, Management Studio Express)

Warning: Setup found that the following components that already exist are at a different service pack level than the components being installed.

Components: Microsoft SQL Server 2005 Tools Express Edition, Microsoft SQL Server 2005 Express Edition (SQLEXPRESS)

After completing setup, you must download and apply the latest SQL Server 2005 service pack to all the components.

"could not open connection to SQL Server"?

I just installed a new SQL 2005 Server (September CTP - Developer Edition) on Windows Server 2003 (Using Virtual PC).

I have created a Data Model to be used for creating reports. When I tried to deploy the Model, I got an error along the lines of "...SQL Server does not allow remote connections...".

I then took a step back and tried to browse the report server (http://localhost/reportserver) and I got the message below:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I also notice that when I go into the Reporting Services Configuration Manager, I see that the Initialization item in the left hand side is Not Configured (has a "red x"). When I try clicking on this item, I get a similar message to the one above.

I am very new at SQL 2005 and this is my first install of it (I have been using other installations in the past). I did some searching and found that I should use the SQL Server Surface Area Configuration utility to allow remote connections for both TCP and Named Pipes. I did this and rebooted my server and I am still getting the same error messages.

Is there something I have yet to configure?

Any and all help is very much appreciated!!!

Thanks!

Brian McCulloughRight after I posted this I realized I renamed the Computer after I installed SQL. The problem was that when I installed reporting services, it created all the connection information based on the "old" computer name.

Brian|||What did you have to do to fix it? Where is the connection information?|||In the Reporting Services Configuration Manager select the Database Setup item on the left-hand side. This is where you specify the Database connection properties for the ReportServer database. I had to change the Server Name to match the current machine name, not what I had it as originally.

-Brian|||I had a similar problem - I was able to fix it by specifying my server as computer-name\servername
Hope this helps

"could not open connection to SQL Server"?

I just installed a new SQL 2005 Server (September CTP - Developer Edition) on Windows Server 2003 (Using Virtual PC).

I have created a Data Model to be used for creating reports. When I tried to deploy the Model, I got an error along the lines of "...SQL Server does not allow remote connections...".

I then took a step back and tried to browse the report server (http://localhost/reportserver) and I got the message below:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I also notice that when I go into the Reporting Services Configuration Manager, I see that the Initialization item in the left hand side is Not Configured (has a "red x"). When I try clicking on this item, I get a similar message to the one above.

I am very new at SQL 2005 and this is my first install of it (I have been using other installations in the past). I did some searching and found that I should use the SQL Server Surface Area Configuration utility to allow remote connections for both TCP and Named Pipes. I did this and rebooted my server and I am still getting the same error messages.

Is there something I have yet to configure?

Any and all help is very much appreciated!!!

Thanks!

Brian McCulloughRight after I posted this I realized I renamed the Computer after I installed SQL. The problem was that when I installed reporting services, it created all the connection information based on the "old" computer name.

Brian|||What did you have to do to fix it? Where is the connection information?|||In the Reporting Services Configuration Manager select the Database Setup item on the left-hand side. This is where you specify the Database connection properties for the ReportServer database. I had to change the Server Name to match the current machine name, not what I had it as originally.

-Brian|||I had a similar problem - I was able to fix it by specifying my server as computer-name\servername
Hope this helps

"Bad Request" error

Hi,

I've installed Reporting Services and configured it without any problem.
When I browse to http://x.x.x.x/reports I'm getting "Bad Request" error.

Is it related somehow to the IP mapping issue?
Any other clues?

Thanks,
Mark

ps
SQL 2005 RTM
W2K3 Std

Mark,

IP address should work fine. I just tried it, and I didn't have any problem. What happens when you use the NetBIOS name instead of the IP address?|||Mike - I have the same problem - did you ever figure it out?|||If you want to run Reporting Services under a different port than normal, you have to change these two config files:
rsreportserver.config
and
RSWebApplication.config

Enter the full path (like http://servername:port/ReportServer) to <ReportServerUrl> (delete <ReportServerVirtualDirectory> then!) or resp. <UrlRoot>

The result is then
<Configuration>
<UI>
<ReportServerUrl>http://mbs05:8088/reportserver</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
.....

and

<Configuration>
... <Service>
....
<MaxQueueThreads>0</MaxQueueThreads>
<UrlRoot>http://mbs05:8088/reportserver</UrlRoot>
<UnattendedExecutionAccount>
...

Hope this helps,
Martin

PS: see also http://msdn2.microsoft.com/en-us/library/ms159261(SQL.90).aspx

"Bad Request" error

Hi,

I've installed Reporting Services and configured it without any problem.
When I browse to http://x.x.x.x/reports I'm getting "Bad Request" error.

Is it related somehow to the IP mapping issue?
Any other clues?

Thanks,
Mark

ps
SQL 2005 RTM
W2K3 Std

Mark,

IP address should work fine. I just tried it, and I didn't have any problem. What happens when you use the NetBIOS name instead of the IP address?|||Mike - I have the same problem - did you ever figure it out?|||If you want to run Reporting Services under a different port than normal, you have to change these two config files:
rsreportserver.config
and
RSWebApplication.config

Enter the full path (like http://servername:port/ReportServer) to <ReportServerUrl> (delete <ReportServerVirtualDirectory> then!) or resp. <UrlRoot>

The result is then
<Configuration>
<UI>
<ReportServerUrl>http://mbs05:8088/reportserver</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
.....

and

<Configuration>
... <Service>
....
<MaxQueueThreads>0</MaxQueueThreads>
<UrlRoot>http://mbs05:8088/reportserver</UrlRoot>
<UnattendedExecutionAccount>
...

Hope this helps,
Martin

PS: see also http://msdn2.microsoft.com/en-us/library/ms159261(SQL.90).aspx

"Bad Request" error

Hi,

I've installed Reporting Services and configured it without any problem.
When I browse to http://x.x.x.x/reports I'm getting "Bad Request" error.

Is it related somehow to the IP mapping issue?
Any other clues?

Thanks,
Mark

ps
SQL 2005 RTM
W2K3 Std

Mark,

IP address should work fine. I just tried it, and I didn't have any problem. What happens when you use the NetBIOS name instead of the IP address?|||Mike - I have the same problem - did you ever figure it out?|||If you want to run Reporting Services under a different port than normal, you have to change these two config files:
rsreportserver.config
and
RSWebApplication.config

Enter the full path (like http://servername:port/ReportServer) to <ReportServerUrl> (delete <ReportServerVirtualDirectory> then!) or resp. <UrlRoot>

The result is then
<Configuration>
<UI>
<ReportServerUrl>http://mbs05:8088/reportserver</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
.....

and

<Configuration>
... <Service>
....
<MaxQueueThreads>0</MaxQueueThreads>
<UrlRoot>http://mbs05:8088/reportserver</UrlRoot>
<UnattendedExecutionAccount>
...

Hope this helps,
Martin

PS: see also http://msdn2.microsoft.com/en-us/library/ms159261(SQL.90).aspx

"A transport-level error has occurred..." When linking a server.

I just installed Microsoft SQL Server Express SP2. I setup a linked server to an Oracle database using the followings commands:

EXEC sp_addlinkedserver 'Oracle_DEV', 'Oracle', 'MSDAORA', 'DEV'

EXEC sp_addlinkedsrvlogin 'Oracle_DEV ', false, NULL, 'oracledbuser', 'dbuserpassword'

When I try and query the linked database I get the following error message:

Msg 109, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)

I've been searching the web and have gotten a lot of hits on the error message but have yet to uncover anything specifically related to linked servers or anything closely related enough to help me resolve this problem. Any advice would be appreciated. Thanks.I am having the exact same problem as you.. I am still trying to find a solution.. I will let you know if I do.. also if you find a solution could you post it here. Thanks|||

This is more of a general engine issue so I'm going to move it to that forum.

Mike

|||

I seem to have solved the problem.. I changed the registry settings for

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI

OracleSqlLib = orasql10.dll

OracleXaLib = oraclient10.dll

then in Admin tools / services. I stopped and started SQL server Express & SQL Server browser (not sure if this did anything - but just letting you know what worked for me)

I am now able to query the oracle database.

One thing though - it is a lot slower than using MS Access and an ODBC passthrough query

<MachineName>\NETSDK installation

I downloaded something that installed an SQL instance of <Machine
Name>NETSDK. It contains Northwind, Pubs, and other sample databases. Does
anyone know how I got this? For the life of me I can't remember.
Marty
If you installed .NET SDK (not just .NET framework), that is when you might
have also installed MSDE. But it would be installed automatically. It is
only when you choose to install .NET tutorial.
"Marty" <Marty@.discussions.microsoft.com> wrote in message
news:ADD3968D-7B7C-4456-9FEE-50A61C040810@.microsoft.com...
> I downloaded something that installed an SQL instance of <Machine
> Name>NETSDK. It contains Northwind, Pubs, and other sample databases. Does
> anyone know how I got this? For the life of me I can't remember.
> Marty
|||Is .NET SDK part of MSDE? If not, where can I get it?
Thanks for your help
"Norman Yuan" wrote:

> If you installed .NET SDK (not just .NET framework), that is when you might
> have also installed MSDE. But it would be installed automatically. It is
> only when you choose to install .NET tutorial.
> "Marty" <Marty@.discussions.microsoft.com> wrote in message
> news:ADD3968D-7B7C-4456-9FEE-50A61C040810@.microsoft.com...
>
>
|||"Marty" <Marty@.discussions.microsoft.com> wrote in message
news:595F40A2-ED7C-4A39-AD93-B6D76B1E111C@.microsoft.com...
> Is .NET SDK part of MSDE? If not, where can I get it?
> Thanks for your help
>
NetSDK is the name of your MSDE instance. That name was used because the
scripts set up to create your sample databases (Pubs, Northwind, etc.) were
written to expect that instance name.
As you say those databases have been created, it looks as if everything is
as it should be.
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|||But where did it come from? The the best of my knowledge, MSDE made an
instance called <MachineName>. Where did <MachineName>\NETSDK come from?
"Peter van der Goes" wrote:

> "Marty" <Marty@.discussions.microsoft.com> wrote in message
> news:595F40A2-ED7C-4A39-AD93-B6D76B1E111C@.microsoft.com...
> NetSDK is the name of your MSDE instance. That name was used because the
> scripts set up to create your sample databases (Pubs, Northwind, etc.) were
> written to expect that instance name.
> As you say those databases have been created, it looks as if everything is
> as it should be.
> --
> Peter [MVP Visual Developer]
> Jack of all trades, master of none.
>
>
|||When installing SQL Server/MSDE, you can choose to use INSTANCE name or not
to. Your "<MachineName\NetSDK" instance on MSDE IS from your installation
with or without your awareness. As I said, in previous reply, it is most
likely installed when you set up .NET tutorial. from .NET document. Of
course you can choose to install it without instance name in the
expenctation that .NET tutorial not working.
"Marty" <Marty@.discussions.microsoft.com> wrote in message
news:394A46D6-F165-4A8C-9F1D-6219828A3205@.microsoft.com...[vbcol=seagreen]
> But where did it come from? The the best of my knowledge, MSDE made an
> instance called <MachineName>. Where did <MachineName>\NETSDK come from?
> "Peter van der Goes" wrote:
were[vbcol=seagreen]
is[vbcol=seagreen]
|||No, I didn't. When I installed MSDE I used the command line: setup SAPWD=
<password> SecurityMode=SQL. That's it. And it's not just an instance. I
contains databases.
"Norman Yuan" wrote:

> When installing SQL Server/MSDE, you can choose to use INSTANCE name or not
> to. Your "<MachineName\NetSDK" instance on MSDE IS from your installation
> with or without your awareness. As I said, in previous reply, it is most
> likely installed when you set up .NET tutorial. from .NET document. Of
> course you can choose to install it without instance name in the
> expenctation that .NET tutorial not working.
> "Marty" <Marty@.discussions.microsoft.com> wrote in message
> news:394A46D6-F165-4A8C-9F1D-6219828A3205@.microsoft.com...
> were
> is
>
>
|||There is another argument for the command line setup:
INSTANCENAME="InstanceName". If you did not specify instance name and you
get <MachineName>\NETSDK, then it can only be explained by that you used the
MSDE coming with .NET SDK or VisualStudio.NET. If your MSDE is directed
downloaded from MS site or from MS Office Pro/Access, the installation would
not add "NetSDK" instance name automatically.
BTW, If you do not like the instance name, you can uninstall and reinstall
the MSDE.
"Marty" <Marty@.discussions.microsoft.com> wrote in message
news:46041F11-611A-4F8D-8B84-67E1D963FB17@.microsoft.com...[vbcol=seagreen]
> No, I didn't. When I installed MSDE I used the command line: setup SAPWD=
> <password> SecurityMode=SQL. That's it. And it's not just an instance. I
> contains databases.
>
> "Norman Yuan" wrote:
not[vbcol=seagreen]
installation[vbcol=seagreen]
from?[vbcol=seagreen]
the[vbcol=seagreen]
etc.)[vbcol=seagreen]
everything[vbcol=seagreen]
|||It was downloaded from MS. But I installed something else and I don't know
what. Add/Remove programs shows MSDE and MSDE (NETSDK). I must have installed
something else because there are two entries but I only installed MSDE once.
"Norman Yuan" wrote:

> There is another argument for the command line setup:
> INSTANCENAME="InstanceName". If you did not specify instance name and you
> get <MachineName>\NETSDK, then it can only be explained by that you used the
> MSDE coming with .NET SDK or VisualStudio.NET. If your MSDE is directed
> downloaded from MS site or from MS Office Pro/Access, the installation would
> not add "NetSDK" instance name automatically.
> BTW, If you do not like the instance name, you can uninstall and reinstall
> the MSDE.
> "Marty" <Marty@.discussions.microsoft.com> wrote in message
> news:46041F11-611A-4F8D-8B84-67E1D963FB17@.microsoft.com...
> not
> installation
> from?
> the
> etc.)
> everything
>
>
|||For the public, although roblem has already been solved via IM: Those
databases can be downloaded at Microsoft under the folling link:
http://www.microsoft.com/downloads/d...displaylang=en
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Marty" <Marty@.discussions.microsoft.com> schrieb im Newsbeitrag
news:ADD3968D-7B7C-4456-9FEE-50A61C040810@.microsoft.com...
>I downloaded something that installed an SQL instance of <Machine
> Name>NETSDK. It contains Northwind, Pubs, and other sample databases. Does
> anyone know how I got this? For the life of me I can't remember.
> Marty

<<SQL2k5>>

Can I have SQL2k5, Sql2k2, Sql2k5 Express Edition installed and functioning
correctly on 1 box?
TIA> Can I have SQL2k5, Sql2k2, Sql2k5 Express Edition installed and
functioning
> correctly on 1 box?
From
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/sseoverview.asp:
Multiple SQL Server 2005 Express installations can coexist on the same
machine along with other installations of SQL Server 2000, SQL Server 2005,
or Microsoft Desktop Engine (MSDE). In general, it is best that SQL Server
2000 instances be upgraded to SP3a or higher. The maximum limit to the
number of SQL instances is 50 on the same machine. These instances must be
uniquely named for the purpose of identifying them.
Still, be aware that SQL 2005 is in Beta version, so you might experience
problems. I prefer installing beta versions in a virtual machine.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

<<SQL2k5>>

Can I have SQL2k5, Sql2k2, Sql2k5 Express Edition installed and functioning
correctly on 1 box?
TIA
> Can I have SQL2k5, Sql2k2, Sql2k5 Express Edition installed and
functioning
> correctly on 1 box?
From
http://msdn.microsoft.com/library/de...eoverview.asp:
Multiple SQL Server 2005 Express installations can coexist on the same
machine along with other installations of SQL Server 2000, SQL Server 2005,
or Microsoft Desktop Engine (MSDE). In general, it is best that SQL Server
2000 instances be upgraded to SP3a or higher. The maximum limit to the
number of SQL instances is 50 on the same machine. These instances must be
uniquely named for the purpose of identifying them.
Still, be aware that SQL 2005 is in Beta version, so you might experience
problems. I prefer installing beta versions in a virtual machine.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com