Re: Don't understand what version of SQL to install

Jeffery, I think the difficulty is my level of knowledge on this topic is
very basic so I don't understand much of what's being shared, like:
scripting, 90 verses ???.

So far, I created a database using sql 2005 express edition. The database
files, mdf and log file is within the app_data folder of the site. The
database works fine. But I cannot make changes to it remotely. I need to
download the database, make the changes, then reupload it again. It works
fine.

But as I understand, I cannot add databases to the app_data folder when
using SQL workgroup and above, they need to be outside the site and added to
the 90 folder (or whatever). Is this correct?

I tried to make a remote connection to the database, but I couldn't do it.

Over the past 2 years, i purchased several books, including paying over
$6000.00 for training videos on SQL Server and asp.net related videos from a
training company. What a total waste of money that was. I have MS and am on a
small disability and started web design and development in the hope to
suppliment my disability. And those videos didn't help at all. I also spent
another I'm so dissapointed. In addition, I purchased Visual Studio Pro with
MSDN subscrition (a few days ago), and the Adobe Suite Master Collection. Now
I can't afford to eat more than one meal a day. So for me, learning is do or
die. I can't even afford a book from a used bookstore.

Dispite all my problems, I'm determined to learn asp.net web development and
design.

Sorry for rambling, I'm a little frustrated right now.

"Jeffrey Williams" wrote:

Okay, it really depends upon what you mean by database. In a lot of cases,
what people mean by database is the schema (objects) that make up the
database (i.e Tables, Views, Stored Procedures, Functions, etc...). I think
what you are talking about is the physical database files (i.e. db_data.mdf,
db_log.ldf, etc...).

What Ekrem is saying is that you can create your database in 90
compatibility mode. Using this mode will prevent you from using 2008
features in that database. When you are ready to deploy, you will script
out all of the objects (tables, views, procedures, etc....) and execute
those scripts on your customers system to create your database.

What Geoff is referring to is what I think you are talking about, and that
is taking a backup of your database and restoring it on your customers site,
or copying the mdf/ldf files (detach) and attaching the database files to
your customers site.

So, you need to decide on how you are going to implement your system and
manage change control. Think about what needs to happen after you have
deployed your solution and you need to make a change. You won't be able to
restore a full database because you won't have the customers data. You are
going to need to script the changes and apply those changes to each
customers system.

With that in mind - could you use SQL Server 2008 Developer Edition? Yes,
as long as you are sure that you have verified the changes against a 90
compatible database.

I hope I have not confused you further,

Jeff

"VeganMan" <VeganMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6B080302-FB77-430A-A2F8-0E99ED1D30D1@xxxxxxxxxxxxxxxx
Oh man, I'm so confused now!

Can I use SQL Developer 2008 to create 2005 databases on different
versions
or not? If so, what problems does this create. I know nothing about
scripting
a schema. I created a database using VS Pro 2008 and added it in the
app_Data
folder.

Terry

"Geoff N. Hiten" wrote:

CORRECTION!!!!

You cannot attach (or move or backup/restore) a SQL 2008 database to a
SQL
2005 server regardless of edition.

END CORRECTION!!!

When you develop a database in a specific version (2000, 2005, 2008) of
SQL
Server, you can "move" that database to a new host within that version,
even
if the edition (express, developer, standard, workgroup, enterprise) is
different. There are a vew restrictions, but for the most part that is
how
it works.

Enterprise is generally used for large-scale systems. SQL Express is the
intended back-end for small single-server web sites.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP



"VeganMan" <VeganMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:59D49338-E994-4F34-BDE9-C3BB3F5C8BF1@xxxxxxxxxxxxxxxx
Hi Ekrem, thanks for being specific.

I'm talking about developing and testing databases for my client and
deploying them on their website. I don't have any access to installing
programs on their servers, as far as I know anyway. So I will not be
installing SQL on anyones server. I'm not just where you got that
impression.
Perhaps I'm not using the right lingal. I'm very new with asp.net and
using
databases. As a matter of fact, I just created my first one but haven't
deployed it yet. (Using the express edition). I haven't even downloaded
any
programs from MSDN yet, other than VS Pro, a couple days ago.

Just to confirm before I maked this as answered:

To my XP, I can add SQL Developer 2008 to develop (I guess I should
say,
"Design") and test databases, including 2005. (I can remove sql
express)

To my Vita, I can use the SQL Enterprise 2008 version.

So I can use SQL Developer 2008 to create a database in standard 2005,
then
an hour later, I can easily use it to develop a express 2008 database?
If
so,
awesome.

I just don't know how to change things to 90. But, your links should
answer
all that.

One more question, please...
What are the benefits of using the Enterprise edition over the
Developer
Edition using my vista system?

Terry

Thanks a head of time, Ekrem.

"Ekrem Önsoy" wrote:

I use two computers for development, on using XP and the other using
Vista,
so I know I cannot use the Enterprise version of SQL, CORRECT?

Not correct literally, because SQL Server 2008 Enterprise Edition can
be
installed on Client OSs such as Windows Vista. This was a limitation
for
Enterprise Editions of SQL Server 2005 and below.

In your first post you said mentioned creating your clients'
databases,
is
that it? I mean are your clients going to be connecting to your SQL
Server
Instance where you perform your development tasks? In this case, you
can
not
use Developer Edition because it's against the license agreement. This
edition of SQL Server is only for one user per license and it's
intended
for
development, test and demo purposes.

If I install the Developer 2008 Edition, can I create databases on
the
needs
of all eight clients, as above? EG: A client needs to have an
express
2005
database created, can I use SQL Developer 2008 to create and test
it?

Yes. By changing the compatibility level of the database to 90.

I can't use the developer 2005 edition for anything using any 2008
versions,
CORRECT?

If you mean creating 2008 version databases then correct, you can't
use a
2005 version instance for that puspose. Because new features of 2008
are
not
included in the previous version.

To sum up, if I install the sql developer edition 2008, can I create
databases for all versions in year 2005 and 2008 without the need to
install
other version, even the express editions, if not, could you explain
please?

Yes, you don't need to install other version or editions. 2008 version
Developer Edition would be sufficient. However see my above comment
about
licensing. Simply, you can't use this Edition of SQL Server as a
"server"
where users connect in a production environment. This can be done only
for
test purposes.

I suggest you to see the Comparison Tables:

For SQL Server 2005:
http://www.microsoft.com/Sqlserver/2005/en/us/compare-features.aspx

For SQL Server 2008:
http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx

--
Ekrem Önsoy - SQL Server MVP



"VeganMan" <VeganMan@xxxxxxxxxxxxxxxxxxxxxxxxx>, iletisinde şunu
yazdı,
news:0613E2A1-F02E-48B2-AB62-E6CDDE803E97@xxxxxxxxxxxxxxxx
Thanks for responding Geoff. But I don't understand what you are
saying.

I spend the entire weekend looking for a answer and still haven't
found
it.
However, I did find out that I cannot use the enterprise edition due
to
only
having XP and Vista.

So I'm down to installing the Developer Edition.

I may not understand your response due to you not understanding my
question,
perhaps... So I will ask in a different way. I hope you don't mind
responding
again.

Let's say I have eight clients:

Client 1 uses Sql Express 2008
Client 2 uses Sql Express 2005
Client 3 uses Sql Workgroup 2008
Client 4 uses Sql Workgroup 2008
Client 5 uses Sql Standard 2008
Client 6 uses Sql Standard 2005
Client 7 uses Sql Enterprise 2008
Client 8 uses Sql Enterprise 2005

Have I missed anything???

I use two computers for development, on using XP and the other using
Vista,
so I know I cannot use the Enterprise version of SQL, CORRECT?

I can't use the developer 2005 edition for anything using any 2008
versions,
CORRECT?

If I install the Developer 2008 Edition, can I create databases on
the
needs
of all eight clients, as above? EG: A client needs to have an
express
2005
database created, can I use SQL Developer 2008 to create and test
it?

To sum up, if I install the sql developer edition 2008, can I create
databases for all versions in year 2005 and 2008 without the need to
install
other version, even the express editions, if not, could you explain
please?

Sorry for my lengthly explaination. I just want to be sure I have
all
my
basis covered.

Thanks,
Terry

"Geoff N. Hiten" wrote:

Unless you use an on-disk structure unique to Enterprise Edition
such
as
partitioning, you can move databases up and down Editions at will.
A
SQL
EE
database can be moved to SQL Express (provided it does not exceed
the
maximum size limitation of express).

Typically, I use Developer Edition to create the databases and then
test
them on whatever the client is running, then deploy them to the
client's
system.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP



"Terry" <Terry@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0755605F-D38F-40B6-BEB9-5C2851335F27@xxxxxxxxxxxxxxxx
I feel silly asking, but I'm a beginner. I have access to all MS
SQL
Servers,
the express, workgroup, standard, developer, and the enterprise
version,
both
2005 and 2008.

My question is, which one should I install for creating client
websites.
.

Relevant Pages

  • Re: Dont understand what version of SQL to install
    ... I'm talking about developing and testing databases for my client and ... To my XP, I can add SQL Developer 2008 to develop (I guess I should say, ... So I can use SQL Developer 2008 to create a database in standard 2005, ... installed on Client OSs such as Windows Vista. ...
    (microsoft.public.sqlserver.setup)
  • Re: Dont understand what version of SQL to install
    ... but "moving" a database implies a degree of automation. ... Principal SQL Infrastructure Consultant ... To my XP, I can add SQL Developer 2008 to develop (I guess I should say, ... installed on Client OSs such as Windows Vista. ...
    (microsoft.public.sqlserver.setup)
  • Re: Dont understand what version of SQL to install
    ... Subscription and I still have to pay $49 to use SQL Developer? ... I don't think you have to buy another license for the Developer Edition, but you better ask this question to whom you bought it. ... it's not stated that SQL Server 2008 Enterprise Edition can be ... > So I can use SQL Developer 2008 to create a database in standard 2005, ...
    (microsoft.public.sqlserver.setup)
  • Re: Database Server based on SQL database
    ... the raw database over WAN. ... So I will write a server program which receives requests from clients via ... Should I base this protocol on SQL or design my own protocol. ... ie the client doesn't have OLE DB, ADO, DAO or whatever installed - ...
    (microsoft.public.win32.programmer.networks)
  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)