Can someone please clarify the difference between Detach / Attach of MDF/LDF
files versus the Backup / Restore of backup to device/file feature? Which
would be ideal for restores of actual databases?
Thank you.Transact-SQL BACKUP/RESTORE is the normal method for database backup and
recovery. Databases can be backed up while online. The backup file size is
usually smaller than the database files since only used pages are backed up.
Also, in the FULL or BULK_LOGGED recovery model, you can reduce potential
data loss by performing transaction log backups.
Detaching a database removes the database from SQL Server while leaving the
physical database files intact. This allows you to rename or move the
physical files and then re-attach. Although one could perform cold backups
using this technique, detach/attach isn't really intended to be used as a
backup/recovery process.
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Can someone please clarify the difference between Detach / Attach of
> MDF/LDF files versus the Backup / Restore of backup to device/file
> feature? Which would be ideal for restores of actual databases?
> Thank you.
>|||Thanks for the explanation. If I was to restore a WSS or SPS which uses SQL
that exists in one domain and restore to another domain - would the Backup /
Restore be better?
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Transact-SQL BACKUP/RESTORE is the normal method for database backup and
> recovery. Databases can be backed up while online. The backup file size
> is usually smaller than the database files since only used pages are
> backed up. Also, in the FULL or BULK_LOGGED recovery model, you can reduce
> potential data loss by performing transaction log backups.
> Detaching a database removes the database from SQL Server while leaving
> the physical database files intact. This allows you to rename or move the
> physical files and then re-attach. Although one could perform cold
> backups using this technique, detach/attach isn't really intended to be
> used as a backup/recovery process.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "KP" <kp@.msn.com> wrote in message
> news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
>|||I usually use backup/restore to move databases between servers. It doesn't
matter if the servers on a different domains.
After you restore to another box, you'll need to make sure you don't have
orphaned users. See sp_change_users_login in the Books Online for
information on how to report/correct the users.
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:eiTM5UxhFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Thanks for the explanation. If I was to restore a WSS or SPS which uses
> SQL that exists in one domain and restore to another domain - would the
> Backup / Restore be better?
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
>
Showing posts with label clarify. Show all posts
Showing posts with label clarify. Show all posts
Sunday, March 25, 2012
Difference between Backup/Restore & Attach/Detach
Can someone please clarify the difference between Detach / Attach of MDF/LDF
files versus the Backup / Restore of backup to device/file feature? Which
would be ideal for restores of actual databases?
Thank you.Transact-SQL BACKUP/RESTORE is the normal method for database backup and
recovery. Databases can be backed up while online. The backup file size is
usually smaller than the database files since only used pages are backed up.
Also, in the FULL or BULK_LOGGED recovery model, you can reduce potential
data loss by performing transaction log backups.
Detaching a database removes the database from SQL Server while leaving the
physical database files intact. This allows you to rename or move the
physical files and then re-attach. Although one could perform cold backups
using this technique, detach/attach isn't really intended to be used as a
backup/recovery process.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Can someone please clarify the difference between Detach / Attach of
> MDF/LDF files versus the Backup / Restore of backup to device/file
> feature? Which would be ideal for restores of actual databases?
> Thank you.
>|||Thanks for the explanation. If I was to restore a WSS or SPS which uses SQL
that exists in one domain and restore to another domain - would the Backup /
Restore be better?
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Transact-SQL BACKUP/RESTORE is the normal method for database backup and
> recovery. Databases can be backed up while online. The backup file size
> is usually smaller than the database files since only used pages are
> backed up. Also, in the FULL or BULK_LOGGED recovery model, you can reduce
> potential data loss by performing transaction log backups.
> Detaching a database removes the database from SQL Server while leaving
> the physical database files intact. This allows you to rename or move the
> physical files and then re-attach. Although one could perform cold
> backups using this technique, detach/attach isn't really intended to be
> used as a backup/recovery process.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "KP" <kp@.msn.com> wrote in message
> news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
>> Can someone please clarify the difference between Detach / Attach of
>> MDF/LDF files versus the Backup / Restore of backup to device/file
>> feature? Which would be ideal for restores of actual databases?
>> Thank you.
>|||I usually use backup/restore to move databases between servers. It doesn't
matter if the servers on a different domains.
After you restore to another box, you'll need to make sure you don't have
orphaned users. See sp_change_users_login in the Books Online for
information on how to report/correct the users.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:eiTM5UxhFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Thanks for the explanation. If I was to restore a WSS or SPS which uses
> SQL that exists in one domain and restore to another domain - would the
> Backup / Restore be better?
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
>> Transact-SQL BACKUP/RESTORE is the normal method for database backup and
>> recovery. Databases can be backed up while online. The backup file size
>> is usually smaller than the database files since only used pages are
>> backed up. Also, in the FULL or BULK_LOGGED recovery model, you can
>> reduce potential data loss by performing transaction log backups.
>> Detaching a database removes the database from SQL Server while leaving
>> the physical database files intact. This allows you to rename or move
>> the physical files and then re-attach. Although one could perform cold
>> backups using this technique, detach/attach isn't really intended to be
>> used as a backup/recovery process.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "KP" <kp@.msn.com> wrote in message
>> news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
>> Can someone please clarify the difference between Detach / Attach of
>> MDF/LDF files versus the Backup / Restore of backup to device/file
>> feature? Which would be ideal for restores of actual databases?
>> Thank you.
>>
>
files versus the Backup / Restore of backup to device/file feature? Which
would be ideal for restores of actual databases?
Thank you.Transact-SQL BACKUP/RESTORE is the normal method for database backup and
recovery. Databases can be backed up while online. The backup file size is
usually smaller than the database files since only used pages are backed up.
Also, in the FULL or BULK_LOGGED recovery model, you can reduce potential
data loss by performing transaction log backups.
Detaching a database removes the database from SQL Server while leaving the
physical database files intact. This allows you to rename or move the
physical files and then re-attach. Although one could perform cold backups
using this technique, detach/attach isn't really intended to be used as a
backup/recovery process.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Can someone please clarify the difference between Detach / Attach of
> MDF/LDF files versus the Backup / Restore of backup to device/file
> feature? Which would be ideal for restores of actual databases?
> Thank you.
>|||Thanks for the explanation. If I was to restore a WSS or SPS which uses SQL
that exists in one domain and restore to another domain - would the Backup /
Restore be better?
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Transact-SQL BACKUP/RESTORE is the normal method for database backup and
> recovery. Databases can be backed up while online. The backup file size
> is usually smaller than the database files since only used pages are
> backed up. Also, in the FULL or BULK_LOGGED recovery model, you can reduce
> potential data loss by performing transaction log backups.
> Detaching a database removes the database from SQL Server while leaving
> the physical database files intact. This allows you to rename or move the
> physical files and then re-attach. Although one could perform cold
> backups using this technique, detach/attach isn't really intended to be
> used as a backup/recovery process.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "KP" <kp@.msn.com> wrote in message
> news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
>> Can someone please clarify the difference between Detach / Attach of
>> MDF/LDF files versus the Backup / Restore of backup to device/file
>> feature? Which would be ideal for restores of actual databases?
>> Thank you.
>|||I usually use backup/restore to move databases between servers. It doesn't
matter if the servers on a different domains.
After you restore to another box, you'll need to make sure you don't have
orphaned users. See sp_change_users_login in the Books Online for
information on how to report/correct the users.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:eiTM5UxhFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Thanks for the explanation. If I was to restore a WSS or SPS which uses
> SQL that exists in one domain and restore to another domain - would the
> Backup / Restore be better?
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
>> Transact-SQL BACKUP/RESTORE is the normal method for database backup and
>> recovery. Databases can be backed up while online. The backup file size
>> is usually smaller than the database files since only used pages are
>> backed up. Also, in the FULL or BULK_LOGGED recovery model, you can
>> reduce potential data loss by performing transaction log backups.
>> Detaching a database removes the database from SQL Server while leaving
>> the physical database files intact. This allows you to rename or move
>> the physical files and then re-attach. Although one could perform cold
>> backups using this technique, detach/attach isn't really intended to be
>> used as a backup/recovery process.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "KP" <kp@.msn.com> wrote in message
>> news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
>> Can someone please clarify the difference between Detach / Attach of
>> MDF/LDF files versus the Backup / Restore of backup to device/file
>> feature? Which would be ideal for restores of actual databases?
>> Thank you.
>>
>
Difference between Backup/Restore & Attach/Detach
Can someone please clarify the difference between Detach / Attach of MDF/LDF
files versus the Backup / Restore of backup to device/file feature? Which
would be ideal for restores of actual databases?
Thank you.
Transact-SQL BACKUP/RESTORE is the normal method for database backup and
recovery. Databases can be backed up while online. The backup file size is
usually smaller than the database files since only used pages are backed up.
Also, in the FULL or BULK_LOGGED recovery model, you can reduce potential
data loss by performing transaction log backups.
Detaching a database removes the database from SQL Server while leaving the
physical database files intact. This allows you to rename or move the
physical files and then re-attach. Although one could perform cold backups
using this technique, detach/attach isn't really intended to be used as a
backup/recovery process.
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Can someone please clarify the difference between Detach / Attach of
> MDF/LDF files versus the Backup / Restore of backup to device/file
> feature? Which would be ideal for restores of actual databases?
> Thank you.
>
|||Thanks for the explanation. If I was to restore a WSS or SPS which uses SQL
that exists in one domain and restore to another domain - would the Backup /
Restore be better?
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Transact-SQL BACKUP/RESTORE is the normal method for database backup and
> recovery. Databases can be backed up while online. The backup file size
> is usually smaller than the database files since only used pages are
> backed up. Also, in the FULL or BULK_LOGGED recovery model, you can reduce
> potential data loss by performing transaction log backups.
> Detaching a database removes the database from SQL Server while leaving
> the physical database files intact. This allows you to rename or move the
> physical files and then re-attach. Although one could perform cold
> backups using this technique, detach/attach isn't really intended to be
> used as a backup/recovery process.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "KP" <kp@.msn.com> wrote in message
> news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
>
|||I usually use backup/restore to move databases between servers. It doesn't
matter if the servers on a different domains.
After you restore to another box, you'll need to make sure you don't have
orphaned users. See sp_change_users_login in the Books Online for
information on how to report/correct the users.
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:eiTM5UxhFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Thanks for the explanation. If I was to restore a WSS or SPS which uses
> SQL that exists in one domain and restore to another domain - would the
> Backup / Restore be better?
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
>
sql
files versus the Backup / Restore of backup to device/file feature? Which
would be ideal for restores of actual databases?
Thank you.
Transact-SQL BACKUP/RESTORE is the normal method for database backup and
recovery. Databases can be backed up while online. The backup file size is
usually smaller than the database files since only used pages are backed up.
Also, in the FULL or BULK_LOGGED recovery model, you can reduce potential
data loss by performing transaction log backups.
Detaching a database removes the database from SQL Server while leaving the
physical database files intact. This allows you to rename or move the
physical files and then re-attach. Although one could perform cold backups
using this technique, detach/attach isn't really intended to be used as a
backup/recovery process.
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Can someone please clarify the difference between Detach / Attach of
> MDF/LDF files versus the Backup / Restore of backup to device/file
> feature? Which would be ideal for restores of actual databases?
> Thank you.
>
|||Thanks for the explanation. If I was to restore a WSS or SPS which uses SQL
that exists in one domain and restore to another domain - would the Backup /
Restore be better?
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Transact-SQL BACKUP/RESTORE is the normal method for database backup and
> recovery. Databases can be backed up while online. The backup file size
> is usually smaller than the database files since only used pages are
> backed up. Also, in the FULL or BULK_LOGGED recovery model, you can reduce
> potential data loss by performing transaction log backups.
> Detaching a database removes the database from SQL Server while leaving
> the physical database files intact. This allows you to rename or move the
> physical files and then re-attach. Although one could perform cold
> backups using this technique, detach/attach isn't really intended to be
> used as a backup/recovery process.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "KP" <kp@.msn.com> wrote in message
> news:%23PtI97whFHA.3300@.TK2MSFTNGP15.phx.gbl...
>
|||I usually use backup/restore to move databases between servers. It doesn't
matter if the servers on a different domains.
After you restore to another box, you'll need to make sure you don't have
orphaned users. See sp_change_users_login in the Books Online for
information on how to report/correct the users.
Hope this helps.
Dan Guzman
SQL Server MVP
"KP" <kp@.msn.com> wrote in message
news:eiTM5UxhFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Thanks for the explanation. If I was to restore a WSS or SPS which uses
> SQL that exists in one domain and restore to another domain - would the
> Backup / Restore be better?
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:u85i3JxhFHA.3316@.TK2MSFTNGP14.phx.gbl...
>
sql
Friday, February 24, 2012
Developer Edition of SQL 2005
Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
went to MS SQL site and I do not see a Developer Edition -
http://www.microsoft.com/sql/2005/pr...5features.mspx
Okay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <mm@.mailme.com> wrote in message
news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> went to MS SQL site and I do not see a Developer Edition -
> http://www.microsoft.com/sql/2005/pr...5features.mspx
>
>
|||Yeah, the only real difference between Developer Edition & Enterprise
Edition is how it is licensed
<http://www.microsoft.com/sql/howtobuy/development.mspx>. Standard
Edition & Enterprise Edition are both available in MSDN Subscribers
downloads (I don't think they're available for download on the public
part of MSDN) and, of course, the eval edition
<http://www.microsoft.com/sql/evaluat...l/default.mspx> (120-day
time-bombed) is available on the public Microsoft SQL Server website.
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean SQL Server 2000 Enterprise Edition
<http://www.microsoft.com/sql/evaluat.../choosing.mspx> or SQL
Server 2005 Enterprise Edition
<http://www.microsoft.com/sql/2005/pr...5features.mspx> or
are you talking about Windows Server 2003 Enterprise
<http://www.microsoft.com/windowsserv...eeditions.mspx>?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
MM wrote:
>Okay, I just saw a post that basically says its equivalent to Enterprise.
>Then what's the real difference - it is just a license restriction? Will
>the Actual standard and Enterprise 2003 be available for download on MSDN?
>
>"MM" <mm@.mailme.com> wrote in message
>news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
>
|||MM wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
developer edition is always the same (sql 7, sql 2000) as eneterprise.
Only difference is license!
You'll probably get to download evaluation edition, which is , again,
the same as enterprise edition but with 120 days evaluation period
|||No difference? Have you tried to install enterprise edition on Windows 2000
pros or XP pro?
"MM" wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
went to MS SQL site and I do not see a Developer Edition -
http://www.microsoft.com/sql/2005/pr...5features.mspx
Okay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <mm@.mailme.com> wrote in message
news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> went to MS SQL site and I do not see a Developer Edition -
> http://www.microsoft.com/sql/2005/pr...5features.mspx
>
>
|||Yeah, the only real difference between Developer Edition & Enterprise
Edition is how it is licensed
<http://www.microsoft.com/sql/howtobuy/development.mspx>. Standard
Edition & Enterprise Edition are both available in MSDN Subscribers
downloads (I don't think they're available for download on the public
part of MSDN) and, of course, the eval edition
<http://www.microsoft.com/sql/evaluat...l/default.mspx> (120-day
time-bombed) is available on the public Microsoft SQL Server website.
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean SQL Server 2000 Enterprise Edition
<http://www.microsoft.com/sql/evaluat.../choosing.mspx> or SQL
Server 2005 Enterprise Edition
<http://www.microsoft.com/sql/2005/pr...5features.mspx> or
are you talking about Windows Server 2003 Enterprise
<http://www.microsoft.com/windowsserv...eeditions.mspx>?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
MM wrote:
>Okay, I just saw a post that basically says its equivalent to Enterprise.
>Then what's the real difference - it is just a license restriction? Will
>the Actual standard and Enterprise 2003 be available for download on MSDN?
>
>"MM" <mm@.mailme.com> wrote in message
>news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
>
|||MM wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
developer edition is always the same (sql 7, sql 2000) as eneterprise.
Only difference is license!
You'll probably get to download evaluation edition, which is , again,
the same as enterprise edition but with 120 days evaluation period
|||No difference? Have you tried to install enterprise edition on Windows 2000
pros or XP pro?
"MM" wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
Developer Edition of SQL 2005
Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
went to MS SQL site and I do not see a Developer Edition -
http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspxOkay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <mm@.mailme.com> wrote in message
news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> went to MS SQL site and I do not see a Developer Edition -
> http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
>
>|||This is a multi-part message in MIME format.
--070200070908020003050409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Yeah, the only real difference between Developer Edition & Enterprise
Edition is how it is licensed
<http://www.microsoft.com/sql/howtobuy/development.mspx>. Standard
Edition & Enterprise Edition are both available in MSDN Subscribers
downloads (I don't think they're available for download on the public
part of MSDN) and, of course, the eval edition
<http://www.microsoft.com/sql/evaluation/trial/default.mspx> (120-day
time-bombed) is available on the public Microsoft SQL Server website.
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean SQL Server 2000 Enterprise Edition
<http://www.microsoft.com/sql/evaluation/features/choosing.mspx> or SQL
Server 2005 Enterprise Edition
<http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx> or
are you talking about Windows Server 2003 Enterprise
<http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx>?
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
MM wrote:
>Okay, I just saw a post that basically says its equivalent to Enterprise.
>Then what's the real difference - it is just a license restriction? Will
>the Actual standard and Enterprise 2003 be available for download on MSDN?
>
>"MM" <mm@.mailme.com> wrote in message
>news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>>Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
>>went to MS SQL site and I do not see a Developer Edition -
>>http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
>>
>>
>
>
--070200070908020003050409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Yeah, the only real difference between Developer Edition &
Enterprise Edition is how it is <a
href="http://links.10026.com/?link=licensed</a>. ">http://www.microsoft.com/sql/howtobuy/development.mspx">licensed</a>.
Standard Edition & Enterprise Edition are both available in MSDN
Subscribers downloads (I don't think they're available for download on
the public part of MSDN) and, of course, the <a
href="http://links.10026.com/?link=eval">http://www.microsoft.com/sql/evaluation/trial/default.mspx">eval
edition</a> (120-day time-bombed) is available on the public Microsoft
SQL Server website.<br>
<br>
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean <a
href="http://links.10026.com/?link=SQL">http://www.microsoft.com/sql/evaluation/features/choosing.mspx">SQL
Server 2000 Enterprise Edition</a> or <a
href="http://links.10026.com/?link=SQL">http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx">SQL
Server 2005 Enterprise Edition</a> or are you talking about <a
href="http://links.10026.com/?link=Windows">http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx">Windows
Server 2003 Enterprise</a>?<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
MM wrote:
<blockquote cite="miduSkNVM32FHA.1276@.TK2MSFTNGP09.phx.gbl" type="cite">
<pre wrap="">Okay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:mm@.mailme.com"><mm@.mailme.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl">news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
went to MS SQL site and I do not see a Developer Edition -
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx</a>">http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx">http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx</a>
</pre>
</blockquote>
<pre wrap=""><!-->
</pre>
</blockquote>
</body>
</html>
--070200070908020003050409--|||MM wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>>Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
>>went to MS SQL site and I do not see a Developer Edition -
>>http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
>>
>
>
developer edition is always the same (sql 7, sql 2000) as eneterprise.
Only difference is license!
You'll probably get to download evaluation edition, which is , again,
the same as enterprise edition but with 120 days evaluation period|||No difference? Have you tried to install enterprise edition on Windows 2000
pros or XP pro?
"MM" wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> > Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> > went to MS SQL site and I do not see a Developer Edition -
> > http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
> >
> >
> >
>
>
went to MS SQL site and I do not see a Developer Edition -
http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspxOkay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <mm@.mailme.com> wrote in message
news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> went to MS SQL site and I do not see a Developer Edition -
> http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
>
>|||This is a multi-part message in MIME format.
--070200070908020003050409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Yeah, the only real difference between Developer Edition & Enterprise
Edition is how it is licensed
<http://www.microsoft.com/sql/howtobuy/development.mspx>. Standard
Edition & Enterprise Edition are both available in MSDN Subscribers
downloads (I don't think they're available for download on the public
part of MSDN) and, of course, the eval edition
<http://www.microsoft.com/sql/evaluation/trial/default.mspx> (120-day
time-bombed) is available on the public Microsoft SQL Server website.
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean SQL Server 2000 Enterprise Edition
<http://www.microsoft.com/sql/evaluation/features/choosing.mspx> or SQL
Server 2005 Enterprise Edition
<http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx> or
are you talking about Windows Server 2003 Enterprise
<http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx>?
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
MM wrote:
>Okay, I just saw a post that basically says its equivalent to Enterprise.
>Then what's the real difference - it is just a license restriction? Will
>the Actual standard and Enterprise 2003 be available for download on MSDN?
>
>"MM" <mm@.mailme.com> wrote in message
>news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>>Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
>>went to MS SQL site and I do not see a Developer Edition -
>>http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
>>
>>
>
>
--070200070908020003050409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Yeah, the only real difference between Developer Edition &
Enterprise Edition is how it is <a
href="http://links.10026.com/?link=licensed</a>. ">http://www.microsoft.com/sql/howtobuy/development.mspx">licensed</a>.
Standard Edition & Enterprise Edition are both available in MSDN
Subscribers downloads (I don't think they're available for download on
the public part of MSDN) and, of course, the <a
href="http://links.10026.com/?link=eval">http://www.microsoft.com/sql/evaluation/trial/default.mspx">eval
edition</a> (120-day time-bombed) is available on the public Microsoft
SQL Server website.<br>
<br>
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean <a
href="http://links.10026.com/?link=SQL">http://www.microsoft.com/sql/evaluation/features/choosing.mspx">SQL
Server 2000 Enterprise Edition</a> or <a
href="http://links.10026.com/?link=SQL">http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx">SQL
Server 2005 Enterprise Edition</a> or are you talking about <a
href="http://links.10026.com/?link=Windows">http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx">Windows
Server 2003 Enterprise</a>?<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
MM wrote:
<blockquote cite="miduSkNVM32FHA.1276@.TK2MSFTNGP09.phx.gbl" type="cite">
<pre wrap="">Okay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:mm@.mailme.com"><mm@.mailme.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl">news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
went to MS SQL site and I do not see a Developer Edition -
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx</a>">http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx">http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx</a>
</pre>
</blockquote>
<pre wrap=""><!-->
</pre>
</blockquote>
</body>
</html>
--070200070908020003050409--|||MM wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>>Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
>>went to MS SQL site and I do not see a Developer Edition -
>>http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
>>
>
>
developer edition is always the same (sql 7, sql 2000) as eneterprise.
Only difference is license!
You'll probably get to download evaluation edition, which is , again,
the same as enterprise edition but with 120 days evaluation period|||No difference? Have you tried to install enterprise edition on Windows 2000
pros or XP pro?
"MM" wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> > Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> > went to MS SQL site and I do not see a Developer Edition -
> > http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
> >
> >
> >
>
>
Developer Edition of SQL 2005
Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
went to MS SQL site and I do not see a Developer Edition -
http://www.microsoft.com/sql/2005/p...05features.mspxOkay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <mm@.mailme.com> wrote in message
news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> went to MS SQL site and I do not see a Developer Edition -
> http://www.microsoft.com/sql/2005/p...05features.mspx
>
>|||Yeah, the only real difference between Developer Edition & Enterprise
Edition is how it is licensed
<http://www.microsoft.com/sql/howtobuy/development.mspx>. Standard
Edition & Enterprise Edition are both available in MSDN Subscribers
downloads (I don't think they're available for download on the public
part of MSDN) and, of course, the eval edition
<http://www.microsoft.com/sql/evalua...al/default.mspx> (120-day
time-bombed) is available on the public Microsoft SQL Server website.
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean SQL Server 2000 Enterprise Edition
<http://www.microsoft.com/sql/evalua...s/choosing.mspx> or SQL
Server 2005 Enterprise Edition
<http://www.microsoft.com/sql/2005/p...05features.mspx> or
are you talking about Windows Server 2003 Enterprise
<http://www.microsoft.com/windowsser...ns.ms
px>?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
MM wrote:
>Okay, I just saw a post that basically says its equivalent to Enterprise.
>Then what's the real difference - it is just a license restriction? Will
>the Actual standard and Enterprise 2003 be available for download on MSDN?
>
>"MM" <mm@.mailme.com> wrote in message
>news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
>|||MM wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
>
developer edition is always the same (sql 7, sql 2000) as eneterprise.
Only difference is license!
You'll probably get to download evaluation edition, which is , again,
the same as enterprise edition but with 120 days evaluation period|||No difference? Have you tried to install enterprise edition on Windows 2000
pros or XP pro?
"MM" wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
went to MS SQL site and I do not see a Developer Edition -
http://www.microsoft.com/sql/2005/p...05features.mspxOkay, I just saw a post that basically says its equivalent to Enterprise.
Then what's the real difference - it is just a license restriction? Will
the Actual standard and Enterprise 2003 be available for download on MSDN?
"MM" <mm@.mailme.com> wrote in message
news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
> Can someone clarify what is the Developer Edition of SQL 2005 (MSDN) - I
> went to MS SQL site and I do not see a Developer Edition -
> http://www.microsoft.com/sql/2005/p...05features.mspx
>
>|||Yeah, the only real difference between Developer Edition & Enterprise
Edition is how it is licensed
<http://www.microsoft.com/sql/howtobuy/development.mspx>. Standard
Edition & Enterprise Edition are both available in MSDN Subscribers
downloads (I don't think they're available for download on the public
part of MSDN) and, of course, the eval edition
<http://www.microsoft.com/sql/evalua...al/default.mspx> (120-day
time-bombed) is available on the public Microsoft SQL Server website.
That's all SQL 2000. In your post you mention Enterprise 2003. Do you
mean SQL Server 2000 Enterprise Edition
<http://www.microsoft.com/sql/evalua...s/choosing.mspx> or SQL
Server 2005 Enterprise Edition
<http://www.microsoft.com/sql/2005/p...05features.mspx> or
are you talking about Windows Server 2003 Enterprise
<http://www.microsoft.com/windowsser...ns.ms
px>?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
MM wrote:
>Okay, I just saw a post that basically says its equivalent to Enterprise.
>Then what's the real difference - it is just a license restriction? Will
>the Actual standard and Enterprise 2003 be available for download on MSDN?
>
>"MM" <mm@.mailme.com> wrote in message
>news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
>|||MM wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
>
developer edition is always the same (sql 7, sql 2000) as eneterprise.
Only difference is license!
You'll probably get to download evaluation edition, which is , again,
the same as enterprise edition but with 120 days evaluation period|||No difference? Have you tried to install enterprise edition on Windows 2000
pros or XP pro?
"MM" wrote:
> Okay, I just saw a post that basically says its equivalent to Enterprise.
> Then what's the real difference - it is just a license restriction? Will
> the Actual standard and Enterprise 2003 be available for download on MSDN?
>
> "MM" <mm@.mailme.com> wrote in message
> news:OEO4pJ32FHA.3272@.TK2MSFTNGP09.phx.gbl...
>
>
Subscribe to:
Comments (Atom)