Thursday, March 29, 2012
Difference between Standard and Enterprise Edition
s
for a customer who would be quering over the WANHi
http://www.microsoft.com/sql/editio...rd/default.mspx
"Tariq" <Tariq@.discussions.microsoft.com> wrote in message
news:FF73CE26-9939-4621-83B9-67222E648CE9@.microsoft.com...
> Where can I find about differences between two edition. I need to advise
> this
> for a customer who would be quering over the WAN
Difference between Standard and Enterprise Edition
for a customer who would be quering over the WANHi
http://www.microsoft.com/sql/editions/standard/default.mspx
"Tariq" <Tariq@.discussions.microsoft.com> wrote in message
news:FF73CE26-9939-4621-83B9-67222E648CE9@.microsoft.com...
> Where can I find about differences between two edition. I need to advise
> this
> for a customer who would be quering over the WANsql
Difference between Standard and Enterprise Edition
for a customer who would be quering over the WAN
Hi
http://www.microsoft.com/sql/edition...d/default.mspx
"Tariq" <Tariq@.discussions.microsoft.com> wrote in message
news:FF73CE26-9939-4621-83B9-67222E648CE9@.microsoft.com...
> Where can I find about differences between two edition. I need to advise
> this
> for a customer who would be quering over the WAN
Difference between SSIS and Biztalk
Hi
Can anybody please tell me the basic differences between Biztalk and SSIS and when to choose which technology over other?
Regards,
Sandeep Saran
SSIS is just a small piece of BizTalk. BizTalk is more Business to Business (B2B). SSIS is more simply, data integration.I suggest you read the documentation for each on Microsoft's site to make your own judgments:
BizTalk
SSIS|||
I asked this question from a Microsoft tech evangelist and I will try and paraphrase the reply:
Biztalk is a "messaging" application basically. It is designed and optomized to move single transactions (called "messages", and consisting of relatively tiny amounts of data in each discrete "message") between different systems or processes in real time. It wraps all user data in XML. As a result, it is extremely verbose during the data movement. It is not fast and would not be very satisfactory to manipulate large data sets using batch processing. Performance would be abysmal most likely.
Whereas SSIS _is_ designed specifically to move and manipulate large datasets using extremely high performance batch processing...
|||
kenambrose wrote:
I asked this question from a Microsoft tech evangelist and I will try and paraphrase the reply:
Biztalk is a "messaging" application basically. It is designed and optomized to move single transactions (called "messages", and consisting of relatively tiny amounts of data in each discrete "message") between different systems or processes in real time. It wraps all user data in XML. As a result, it is extremely verbose during the data movement. It is not fast and would not be very satisfactory to manipulate large data sets using batch processing. Performance would be abysmal most likely.
Whereas SSIS _is_ designed specifically to move and manipulate large datasets using extremely high performance batch processing...
Think EDI - Electronic Data Interchange|||
Sandeep Saran wrote:
Hi
Can anybody please tell me the basic differences between Biztalk and SSIS and when to choose which technology over other?
Start with this whitepaper describing possible approaches:
http://www.microsoft.com/technet/prodtechnol/biztalk/2004/whitepapers/integration.mspx
Difference between SQL2k Enterprise & Developer editions?
i mean except that with in the developer edition only 1 user can login
on what version is it better to develop ?
does the developer ver. include something that the entprise does not ? (or vice versa)
(say in theory i can choose on which version to work ;-))
thanx, max.Directly from Microsoft's site:
Developer edition is designed to allow developers to build any type of application on top of SQL Server. It includes all the functionality of Enterprise Edition but with a special development and test end-user license agreement (EULA) that prohibits production deployment. It is the ideal choice for Independent Software Vendors (ISVs), consultants, system integrators, solution providers, and corporate developers developing and testing applications because it is cost effective, runs on a variety of platforms, and can be upgraded for production use to SQL Server 2000 Enterprise Edition.
It is the only edition of SQL Server 2000 that gives the licensee the right to download and install SQL Server 2000 Windows CE Edition (SQL Server CE). The Developer Edition licensee also has the right to redistribute SQL Server CE-based applications to an unlimited number of devices at no additional cost beyond the purchase price of SQL Server 2000 Developer Edition.|||SQL Server 2000 has the following editions:
Personal Edition
Standard Edition
Enterprise Edition
Developer Edition
Desktop Engine
SQL Server CE
Evaluation Edition
Personal Edition can work on the Windows 98, Windows NT Server 4.0 with Service Pack 5 or later, Windows NT Workstation 4.0 with Service Pack 5 or later and on the all editions of Windows 2000. This edition is related to SQL Server 7.0 Desktop Edition.
This edition has some restrictions:
maximum 2 CPU
no Distributed Partitioned Views
no Log Shipping
no Parallel DBCC
no Parallel index creation
no Failover clustering
no publishing for transaction replication
maximum 2Gb RAM
Standard Edition can work on the Windows NT Server 4.0 with Service Pack 5, Windows NT Server 4.0 Enterprise Edition and on the Windows 2000 Server/Advanced Server/DataCenter.
This edition has the following restrictions:
maximum 4 CPU (up to 8 CPU on the Windows NT Enterprise Edition)
no Distributed Partitioned Views
no Log Shipping
no Parallel index creation
no Failover clustering
maximum 2Gb RAM
Enterprise Edition can work on the Windows NT Server 4.0 with Service Pack 5, Windows NT Server 4.0 Enterprise Edition and on the Windows 2000 Server/Advanced Server/DataCenter.
This edition can use:
up to 32 CPU on the Windows 2000 DataCenter up to 8 CPU on the Windows 2000 Advanced Server and on the Windows NT Server 4.0 Enterprise Edition up to 4 CPU on the Windows NT Server 4.0 and on the Windows 2000 Server
up to 64Gb RAM on the Windows 2000 DataCenter up to 8 Gb RAM on the Windows 2000 Advanced Server up to 4 Gb RAM on the Windows 2000 Server up to 3 Gb RAM on the Windows NT Server 4.0 Enterprise Edition up to 2 Gb RAM on the Windows NT Server 4.0
Distributed Partitioned Views
Log Shipping
Parallel index creation
Failover clustering
The Developer Edition can be used by developers to create and debug stored procedures and triggers. This edition comes with its own compact disc and can be upgraded to SQL Server 2000 Enterprise Edition.
The Desktop Engine has no graphical user interface and is related to the MSDE, not to the SQL Server 7.0 Desktop Edition. The size of Desktop Engine databases cannot exceed 2 GB. The Desktop Engine can use maximum 2 CPU.
The SQL Server CE edition can work only on the Microsoft Windows CE, so it has all restrictions of this operation system (can use only 1 CPU, no Parallel index creation, no Full-Text Search and so on).
The Evaluation Edition can be used only for the test purposes to learn more about the new features and enhancements and should be uninstalled after a 120-day evaluation period.
difference between sql2k and sql2005
differences between sql2k and sql2005?
tia,
dkYes. 2005 Books Online details the differences pretty explicitly. Be
prepared to spend several hours, because the information is several hundred
pages deep.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"dk" <dk@.discussions.microsoft.com> wrote in message
news:215A1B80-81D1-4788-96A2-A63153EEB5C1@.microsoft.com...
> is there a good article or book or faq which highlights the
> differences between sql2k and sql2005?
> tia,
> dk|||There is no simple answer as 2005 is a major upgrade and there are lots of
new features. One of the most interesting features involves CLR integration,
which lets you can code your stored procedures, functions, and triggers in
the .NET Framework language of your choice. Microsoft Visual Basic .NET and
the C#. Another major new feature is Database Mirroring and a complete
rewrite of DTS. DTS is now called SSIS (SQL Server Integration Services )
Lots of new features in reporting services and Business Intelligence. See
www.sqlservercentral for a bunch of great articles on 2005.
For the Microsoft perspective see
http://www.microsoft.com/sql/prodinfo/overview/whats-new-in-sqlserver2005.mspx
"dk" wrote:
> is there a good article or book or faq which highlights the
> differences between sql2k and sql2005?
> tia,
> dk|||This is a multi-part message in MIME format.
--020109090507080508080807
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In addition, Michael Otey (the Technical Director for SQLMag) wrote a
book about a year & a half ago (so it will be based on a Beta version I
think) published by Osborne called Microsoft SQL Server 2005 New
Features
<http://www.amazon.com/gp/product/0072227761/sr=1-1/qid=1138921308/ref=sr_1_1/102-3661316-4174542?%5Fencoding=UTF8>.
I haven't read it myself but it sounds like it might be right up your alley.
--
*mike hodgson*
http://sqlnerd.blogspot.com
Michael Hotek wrote:
>Yes. 2005 Books Online details the differences pretty explicitly. Be
>prepared to spend several hours, because the information is several hundred
>pages deep.
>
>
--020109090507080508080807
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>In addition, Michael Otey (the Technical Director for </tt><tt>SQLMag</tt><tt>)
wrote a book about a year & a half ago (so it will be based on a
Beta version I think) published by Osborne called <a
href="http://links.10026.com/?link=Microsoft">http://www.amazon.com/gp/product/0072227761/sr=1-1/qid=1138921308/ref=sr_1_1/102-3661316-4174542?%5Fencoding=UTF8">Microsoft
SQL Server 2005 New Features</a>. I haven't read it myself but it
sounds like it might be right up your alley.</tt><br>
<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"><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>
Michael Hotek wrote:
<blockquote cite="midesC9ngBKGHA.3728@.tk2msftngp13.phx.gbl" type="cite">
<pre wrap="">Yes. 2005 Books Online details the differences pretty explicitly. Be
prepared to spend several hours, because the information is several hundred
pages deep.
</pre>
</blockquote>
</body>
</html>
--020109090507080508080807--
Difference between SQL 2000 st. and SQL 2000 Enterprise
I feel a bit silly here. If spent the last 45 mins searching the web trying
to find a definite list of the differences between SQL 2000 Standard and SQL
2000 Enterprise. All the links at microsoft.com seem to redirect to the 2005
version. If anyone can link me to a feature comparison or know the numbers
off the top of their head I would be grateful. The most pressing question is
this:
What if I buy a standard edition and install it on a server with 4Gb RAM,
would I:
Violate my license since standard only supports up to 2 Gb?
or would the SQL server simply just use only 2Gb RAM and work just fine and
no license would be violated?
Thanks in advance
IbIb,
In your SQL Server 2000 Books Online is a topic "Features Supported by the
Editions of SQL Server 2000" that will give general guidance on features.
Installing standard edition on a server with more RAM will not violate a
license. SQL Server will only use as much memory as it can.
RLF
"Ib Schrader" <ibschrader@.gmail.com> wrote in message
news:e1LaFcw6HHA.2632@.TK2MSFTNGP06.phx.gbl...
> Hi there
> I feel a bit silly here. If spent the last 45 mins searching the web
> trying to find a definite list of the differences between SQL 2000
> Standard and SQL 2000 Enterprise. All the links at microsoft.com seem to
> redirect to the 2005 version. If anyone can link me to a feature
> comparison or know the numbers off the top of their head I would be
> grateful. The most pressing question is this:
> What if I buy a standard edition and install it on a server with 4Gb RAM,
> would I:
> Violate my license since standard only supports up to 2 Gb?
> or would the SQL server simply just use only 2Gb RAM and work just fine
> and no license would be violated?
> Thanks in advance
> Ib
>|||The information is in Books on Line, the documentation. You could
download and install that from the Microsoft site, or read it on the
web.
http://msdn2.microsoft.com/en-us/library/aa175266(SQL.80).aspx
That should put you int he neighborhood.
Roy Harvey
Beacon Falls, CT
On Thu, 30 Aug 2007 15:09:36 +0200, "Ib Schrader"
<ibschrader@.gmail.com> wrote:
>Hi there
>I feel a bit silly here. If spent the last 45 mins searching the web trying
>to find a definite list of the differences between SQL 2000 Standard and SQL
>2000 Enterprise. All the links at microsoft.com seem to redirect to the 2005
>version. If anyone can link me to a feature comparison or know the numbers
>off the top of their head I would be grateful. The most pressing question is
>this:
>What if I buy a standard edition and install it on a server with 4Gb RAM,
>would I:
>Violate my license since standard only supports up to 2 Gb?
>or would the SQL server simply just use only 2Gb RAM and work just fine and
>no license would be violated?
>Thanks in advance
>Ib
>|||Books online..never knew something like that existed.
Thanks to both of you
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:nmidd351bfo31q14ee6hufgq5jf75r2e89@.4ax.com...
> The information is in Books on Line, the documentation. You could
> download and install that from the Microsoft site, or read it on the
> web.
> http://msdn2.microsoft.com/en-us/library/aa175266(SQL.80).aspx
> That should put you int he neighborhood.
> Roy Harvey
> Beacon Falls, CT
> On Thu, 30 Aug 2007 15:09:36 +0200, "Ib Schrader"
> <ibschrader@.gmail.com> wrote:
>>Hi there
>>I feel a bit silly here. If spent the last 45 mins searching the web
>>trying
>>to find a definite list of the differences between SQL 2000 Standard and
>>SQL
>>2000 Enterprise. All the links at microsoft.com seem to redirect to the
>>2005
>>version. If anyone can link me to a feature comparison or know the numbers
>>off the top of their head I would be grateful. The most pressing question
>>is
>>this:
>>What if I buy a standard edition and install it on a server with 4Gb RAM,
>>would I:
>>Violate my license since standard only supports up to 2 Gb?
>>or would the SQL server simply just use only 2Gb RAM and work just fine
>>and
>>no license would be violated?
>>Thanks in advance
>>Ib
Difference between SPs
Thanks.http://support.microsoft.com/default.aspx?scid=kb;en-us;306908
Tuesday, March 27, 2012
Difference between MS SQL 2000 and MS SQL 2005
TIA
Maheshsql 2k5 extend trigger functionality for DDL statement also ( eg create table statement) that to database level and server level trigger|||great question.
more functionality, and more secure database|||Please find the details here. and here.sql
Thursday, March 22, 2012
Difference between AMO and ADOMD.NET
AMO is the management object model, used to create, alter, delete, backup, restore objects.
ADOMD.NET is the query object model, used to run MDX queries, discover requests.
Adrian Dumitrascu
Difference between 2000 and 2005
do you know defined performance differences between SQL 2000 and SQL
2005?
thanks in advance
I can't compare directly - there are loads of enhancements in the
architecture, some of which have no direct comparison eg a lot of what was
originally done in post snapshot scripts can now be done directly and merge
has unidirectional articles which aren't logged using triggers etc - also we
have different hardware between the installations.. For a quantitative
comparison where things are held constant as far as possible, have a look at
this article:
http://www.microsoft.com/technet/prodtechnol/sql/2005/mergrepl.mspx. If
applies to merge, but some of the snapshot details will equally apply to
transactional also.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .