Installing sql server on vista

Hi Guys,

I m a beginner to sql server 2000 or 2005 .i want to install sql server on my PC (windows vista).can you please tell me how to download and install the sql server.i want to practise some procedures and sql statements.can you please guide me what should i download (server and client).

Thanks in advance

OK, there is no "client" for SQL Server, you can use the normal MDAC drivers or install the SQL Native client. The server version which is free of charge can be downloaded from the Microsoft site. Head out for the SQL Server Express SP2 version (and especially for beginners the advanced edition with the additional toolset)

Jens K. Suessmeyer

http://www.sqlserver2005.de

Installing SQL server on a domain controller?

Hi guys,
I'm currently working on my MCDBA and I happen to be using the Microsoft
Press edition. The book states the server that you plan to intall SQL server
should be configured as a domain controller. From reading and listening to
outside experts, I've always thought that the server should be configured as
just a member server. Can someone clear this up for me?
That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
A Domain Controller has too much network traffic to compete with a SQL Server
installation. You will reduce the responsiveness of both. Moreover, what
makes a DBMS efficient is the exclusive use of large memory. This makes a
DBMS system unusfull as any other cohosted application system. The power of
distributed computing is the dedication of function accross multiple servers.
Each server should be dedicated to a SINGLE role, or function.
Lastly, this is a huge potential security issue. A SQL Server installation,
of necessity, controls most of the resources on the server it is installed
on. If this is a domain controller, this means the security database. If
this installation was compromised, this would mean your entire network would
be also.
Sincerely,
Anthony Thomas
"Charles" wrote:

> Hi guys,
> I'm currently working on my MCDBA and I happen to be using the Microsoft
> Press edition. The book states the server that you plan to intall SQL server
> should be configured as a domain controller. From reading and listening to
> outside experts, I've always thought that the server should be configured as
> just a member server. Can someone clear this up for me?
|||thanks!
"AnthonyThomas" wrote:
[vbcol=seagreen]
> That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
> A Domain Controller has too much network traffic to compete with a SQL Server
> installation. You will reduce the responsiveness of both. Moreover, what
> makes a DBMS efficient is the exclusive use of large memory. This makes a
> DBMS system unusfull as any other cohosted application system. The power of
> distributed computing is the dedication of function accross multiple servers.
> Each server should be dedicated to a SINGLE role, or function.
> Lastly, this is a huge potential security issue. A SQL Server installation,
> of necessity, controls most of the resources on the server it is installed
> on. If this is a domain controller, this means the security database. If
> this installation was compromised, this would mean your entire network would
> be also.
> Sincerely,
>
> Anthony Thomas
>
> "Charles" wrote:
|||http://giuciao.altervista.org/free_books.html
"Charles" <Charles@.discussions.microsoft.com> wrote in message news:<86D792B6-668D-4027-A953-945755BCB1DE@.microsoft.com>...[vbcol=seagreen]
> thanks!
> "AnthonyThomas" wrote:

Installing SQL server on a domain controller?

Hi guys,
I'm currently working on my MCDBA and I happen to be using the Microsoft
Press edition. The book states the server that you plan to intall SQL server
should be configured as a domain controller. From reading and listening to
outside experts, I've always thought that the server should be configured as
just a member server. Can someone clear this up for me?That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
A Domain Controller has too much network traffic to compete with a SQL Serve
r
installation. You will reduce the responsiveness of both. Moreover, what
makes a DBMS efficient is the exclusive use of large memory. This makes a
DBMS system unusfull as any other cohosted application system. The power of
distributed computing is the dedication of function accross multiple servers
.
Each server should be dedicated to a SINGLE role, or function.
Lastly, this is a huge potential security issue. A SQL Server installation,
of necessity, controls most of the resources on the server it is installed
on. If this is a domain controller, this means the security database. If
this installation was compromised, this would mean your entire network would
be also.
Sincerely,
Anthony Thomas
"Charles" wrote:

> Hi guys,
> I'm currently working on my MCDBA and I happen to be using the Microsoft
> Press edition. The book states the server that you plan to intall SQL serv
er
> should be configured as a domain controller. From reading and listening to
> outside experts, I've always thought that the server should be configured
as
> just a member server. Can someone clear this up for me?|||thanks!
"AnthonyThomas" wrote:
[vbcol=seagreen]
> That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER
.
> A Domain Controller has too much network traffic to compete with a SQL Ser
ver
> installation. You will reduce the responsiveness of both. Moreover, what
> makes a DBMS efficient is the exclusive use of large memory. This makes a
> DBMS system unusfull as any other cohosted application system. The power
of
> distributed computing is the dedication of function accross multiple serve
rs.
> Each server should be dedicated to a SINGLE role, or function.
> Lastly, this is a huge potential security issue. A SQL Server installatio
n,
> of necessity, controls most of the resources on the server it is installed
> on. If this is a domain controller, this means the security database. If
> this installation was compromised, this would mean your entire network wou
ld
> be also.
> Sincerely,
>
> Anthony Thomas
>
> "Charles" wrote:
>|||http://giuciao.altervista.org/free_books.html
"Charles" <Charles@.discussions.microsoft.com> wrote in message news:<86D792B6-668D-4027-A953
-945755BCB1DE@.microsoft.com>...[vbcol=seagreen]
> thanks!
> "AnthonyThomas" wrote:
>

Installing SQL server on a domain controller?

Hi guys,
I'm currently working on my MCDBA and I happen to be using the Microsoft
Press edition. The book states the server that you plan to intall SQL server
should be configured as a domain controller. From reading and listening to
outside experts, I've always thought that the server should be configured as
just a member server. Can someone clear this up for me?That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
A Domain Controller has too much network traffic to compete with a SQL Server
installation. You will reduce the responsiveness of both. Moreover, what
makes a DBMS efficient is the exclusive use of large memory. This makes a
DBMS system unusfull as any other cohosted application system. The power of
distributed computing is the dedication of function accross multiple servers.
Each server should be dedicated to a SINGLE role, or function.
Lastly, this is a huge potential security issue. A SQL Server installation,
of necessity, controls most of the resources on the server it is installed
on. If this is a domain controller, this means the security database. If
this installation was compromised, this would mean your entire network would
be also.
Sincerely,
Anthony Thomas
"Charles" wrote:
> Hi guys,
> I'm currently working on my MCDBA and I happen to be using the Microsoft
> Press edition. The book states the server that you plan to intall SQL server
> should be configured as a domain controller. From reading and listening to
> outside experts, I've always thought that the server should be configured as
> just a member server. Can someone clear this up for me?|||thanks!
"AnthonyThomas" wrote:
> That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
> A Domain Controller has too much network traffic to compete with a SQL Server
> installation. You will reduce the responsiveness of both. Moreover, what
> makes a DBMS efficient is the exclusive use of large memory. This makes a
> DBMS system unusfull as any other cohosted application system. The power of
> distributed computing is the dedication of function accross multiple servers.
> Each server should be dedicated to a SINGLE role, or function.
> Lastly, this is a huge potential security issue. A SQL Server installation,
> of necessity, controls most of the resources on the server it is installed
> on. If this is a domain controller, this means the security database. If
> this installation was compromised, this would mean your entire network would
> be also.
> Sincerely,
>
> Anthony Thomas
>
> "Charles" wrote:
> > Hi guys,
> > I'm currently working on my MCDBA and I happen to be using the Microsoft
> > Press edition. The book states the server that you plan to intall SQL server
> > should be configured as a domain controller. From reading and listening to
> > outside experts, I've always thought that the server should be configured as
> > just a member server. Can someone clear this up for me?|||http://giuciao.altervista.org/free_books.html
"Charles" <Charles@.discussions.microsoft.com> wrote in message news:<86D792B6-668D-4027-A953-945755BCB1DE@.microsoft.com>...
> thanks!
> "AnthonyThomas" wrote:
> > That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
> > A Domain Controller has too much network traffic to compete with a SQL Server
> > installation. You will reduce the responsiveness of both. Moreover, what
> > makes a DBMS efficient is the exclusive use of large memory. This makes a
> > DBMS system unusfull as any other cohosted application system. The power of
> > distributed computing is the dedication of function accross multiple servers.
> > Each server should be dedicated to a SINGLE role, or function.
> >
> > Lastly, this is a huge potential security issue. A SQL Server installation,
> > of necessity, controls most of the resources on the server it is installed
> > on. If this is a domain controller, this means the security database. If
> > this installation was compromised, this would mean your entire network would
> > be also.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> >
> > "Charles" wrote:
> >
> > > Hi guys,
> > > I'm currently working on my MCDBA and I happen to be using the Microsoft
> > > Press edition. The book states the server that you plan to intall SQL server
> > > should be configured as a domain controller. From reading and listening to
> > > outside experts, I've always thought that the server should be configured as
> > > just a member server. Can someone clear this up for me?

Installing Sql Mobile via CAB file

Hi guys,

wonder if someone can help? I have written an app the runs on PocketPC 2003 and uses CF 2 and Sql Mobile 2005. I need to be able to install my application and Sql Mobile from within a desktop app. This is what I am doing, but I have a few questions:

Using RAPI I copy over to the device; myApp.CAB and sqlce30.ppc.wce4.armv4.CAB.
Using RAPI I then run wceload on these two CAB files.

This works a treat, both application install properly and work!!

But, in the same directory as the sqlce30.ppc.wce4.armv4.CAB (in C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4) there are two other CAB files:

sqlce30.dev.ENU.ppc.wce4.armv4.CAB
sqlce30.repl.ppc.wce4.armv4.CAB

My application doesn't use replication so I didn't copy over the second file. But what is the first one, and do I need it installed on the device?

Thanks for your help
Graham

Hi

I installed

sqlce30.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4

and

sql.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Client\v2.0\wce400\armv4

and

Installing Sql Mobile via CAB file

Hi guys,

wonder if someone can help? I have written an app the runs on PocketPC 2003 and uses CF 2 and Sql Mobile 2005. I need to be able to install my application and Sql Mobile from within a desktop app. This is what I am doing, but I have a few questions:

Using RAPI I copy over to the device; myApp.CAB and sqlce30.ppc.wce4.armv4.CAB.
Using RAPI I then run wceload on these two CAB files.

This works a treat, both application install properly and work!!

But, in the same directory as the sqlce30.ppc.wce4.armv4.CAB (in C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4) there are two other CAB files:

sqlce30.dev.ENU.ppc.wce4.armv4.CAB
sqlce30.repl.ppc.wce4.armv4.CAB

My application doesn't use replication so I didn't copy over the second file. But what is the first one, and do I need it installed on the device?

Thanks for your help
Graham

Hi

I installed

sqlce30.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4

and

sql.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Client\v2.0\wce400\armv4

and