Showing posts with label due. Show all posts
Showing posts with label due. Show all posts

Thursday, March 29, 2012

difference between SQL standard Edition and Enterprise Edition

Hi, there,

We are running SQL 2000 & SP4 with our ASP.NET application, now we plan to upgrade to Enterprise Edition due to the huge diffirence in price. Can any one of u give an brief introduction of the difference between these two, and what is the advantages of enterprise edition?

Any suggestion will greately appreciated.

Shermaine

There's a good comparison of the various versions of SQL Server here:-

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

|||

shermaine wrote:

now we plan to upgrade to Enterprise Edition due to the huge diffirence in price.

That seems logical.

Friday, February 24, 2012

Developer limitation under SQL 2005 under Vista Ultimate 64 bit

Just to be clear, I would like to know if a problem I face is due to an error on my part or a limitation on Microsoft's. In my experience (several hours-long installations, removals, reinstallations, using the skuupgrade=1 parameter from the command line, ad nauseum) I have concluded that the best one can do installing SQL Server 2005 Developer Edition from the Visual Studio 2005 Professional Edition package is to get the Express Edition, (actually styled MSSMLBIZ). In particular, what I'm hoping to be able to do is program to a test database that I have from my client, which I was able to do on my XP Professional machine. But on my new Vista Ultimate 64 bit machine (which will only let me install the x64 version of SQL Server 2005), I get an instance that is characterized as SQL Server Express and generates the following error message when I try to attach to the same MDF file to which I was able to attach under my prior, XP-Pro based configuration:

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'ZAPHOD42\MSSMLBIZ'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database. (Microsoft SQL Server, Error: 1827)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3054&EvtSrc=MSSQLServer&EvtID=1827&LinkId=20476

BUTTONS:

OK

===================================================================================
The following is the Help obtained when clicking on the button on the error msg and the references in the error msg:
===================================================================================
Details
ID: Attach database Server
Source: Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText

We're sorry
There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere.

--

Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information.

Currently there are no Microsoft Knowledge Base articles available for this specific error or event message. For information about other support options you can use to find answers online, see http://support.microsoft.com/default.aspx.

==================

Details
ID: 1827
Source: MSSQLServer

We're sorry
There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere.
Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information.

==========End of reproduction of error messages and help text ====================================

The Developer Edition, of course, is supposed to enable us to program to all levels of the database, and I would hate to think it is really crippled in this way, but after uninstalling everything, reinstalling multiple times (devoting several days to the process), it sure beats me how I can overcome this problem short of going back to my old machine. Any definitive answers on this apparent limitation, or useful procedural advice on installation quirks, would be appreciated (and, yes, I've spent a lot of time going through the installation/setup forum -- if the answer is there I can't find it).

Seems as you want to attach a user database to a Express instance ? What is the output if you connect to the mentioned server and execute the following command: SELECT @.@.Version ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||The server is my local machine, and I cannot attach to the database on it, as I tried to explain above, because the database is too big. When I run the command you suggest without attaching a specific database, the following output is obtained:

Microsofty SQL Server 2005 - 9.00.3054.00 (Intel X86) Mar 23 2007 16:28:52 Copyright (c) 1988-2005 Microsoft Corporation Express Ediition on Windows NT 6.0 (Build 6000Smile

I must say the X86 reference surprises me. I hope this means more to you than it does to me.
Bob

|||

Using a SQL Server Express edition you are limited to 4GB database size (all databases in sum of the instance)

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

I face the same problem... I have a Vista ultimate x64 and I tried to attach a small MDF to SQLexpress and I had an error. It's the same if I try to create a new db?

could you give me some help

Developer limitation under SQL 2005 under Vista Ultimate 64 bit

Just to be clear, I would like to know if a problem I face is due to an error on my part or a limitation on Microsoft's. In my experience (several hours-long installations, removals, reinstallations, using the skuupgrade=1 parameter from the command line, ad nauseum) I have concluded that the best one can do installing SQL Server 2005 Developer Edition from the Visual Studio 2005 Professional Edition package is to get the Express Edition, (actually styled MSSMLBIZ). In particular, what I'm hoping to be able to do is program to a test database that I have from my client, which I was able to do on my XP Professional machine. But on my new Vista Ultimate 64 bit machine (which will only let me install the x64 version of SQL Server 2005), I get an instance that is characterized as SQL Server Express and generates the following error message when I try to attach to the same MDF file to which I was able to attach under my prior, XP-Pro based configuration:

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'ZAPHOD42\MSSMLBIZ'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database. (Microsoft SQL Server, Error: 1827)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3054&EvtSrc=MSSQLServer&EvtID=1827&LinkId=20476

BUTTONS:

OK

===================================================================================
The following is the Help obtained when clicking on the button on the error msg and the references in the error msg:
===================================================================================
Details
ID: Attach database Server
Source: Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText

We're sorry
There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere.

--

Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information.

Currently there are no Microsoft Knowledge Base articles available for this specific error or event message. For information about other support options you can use to find answers online, see http://support.microsoft.com/default.aspx.

==================

Details
ID: 1827
Source: MSSQLServer

We're sorry
There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere.
Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information.

==========End of reproduction of error messages and help text ====================================

The Developer Edition, of course, is supposed to enable us to program to all levels of the database, and I would hate to think it is really crippled in this way, but after uninstalling everything, reinstalling multiple times (devoting several days to the process), it sure beats me how I can overcome this problem short of going back to my old machine. Any definitive answers on this apparent limitation, or useful procedural advice on installation quirks, would be appreciated (and, yes, I've spent a lot of time going through the installation/setup forum -- if the answer is there I can't find it).

Seems as you want to attach a user database to a Express instance ? What is the output if you connect to the mentioned server and execute the following command: SELECT @.@.Version ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||The server is my local machine, and I cannot attach to the database on it, as I tried to explain above, because the database is too big. When I run the command you suggest without attaching a specific database, the following output is obtained:

Microsofty SQL Server 2005 - 9.00.3054.00 (Intel X86) Mar 23 2007 16:28:52 Copyright (c) 1988-2005 Microsoft Corporation Express Ediition on Windows NT 6.0 (Build 6000Smile

I must say the X86 reference surprises me. I hope this means more to you than it does to me.
Bob

|||

Using a SQL Server Express edition you are limited to 4GB database size (all databases in sum of the instance)

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

I face the same problem... I have a Vista ultimate x64 and I tried to attach a small MDF to SQLexpress and I had an error. It's the same if I try to create a new db?

could you give me some help

Tuesday, February 14, 2012

Determining trigger execution state

Is there a way to determine if a trigger fired due to an insert or update
operation. I need to know this for the following reason. I have fields in
my tables that I want to initialize only when a record is inserted. If the
record is later updated, I do not want these fields changed. I also do not
want to have to maintain two seperate triggers to do this. In SqlAnywhere,
they have variables you check in the trigger to determine this as the
following example illustrates.
IF Inserting
!do inserting code
END IF
IF Updating
!do updating code
END IF
Is there something similar to this in SQL server?
Thanks in advance for any help.
Mark GenovyHi Mark
If any rows were affected, an insert trigger will only populate the inserted
table, but an update trigger will populate both inserted and deleted. So I
usually just look at the count(*) value from these tables. However, if no
rows were affected, the triggers will still fire, and both inserted and
deleted will have 0 rows. So then you can't tell what operation occurred.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Mark Genovy" <Mark Genovy@.discussions.microsoft.com> wrote in message
news:24381F86-0662-4913-A703-139BC0A9DF46@.microsoft.com...
> Is there a way to determine if a trigger fired due to an insert or update
> operation. I need to know this for the following reason. I have fields
> in
> my tables that I want to initialize only when a record is inserted. If
> the
> record is later updated, I do not want these fields changed. I also do
> not
> want to have to maintain two seperate triggers to do this. In
> SqlAnywhere,
> they have variables you check in the trigger to determine this as the
> following example illustrates.
> IF Inserting
> !do inserting code
> END IF
> IF Updating
> !do updating code
> END IF
> Is there something similar to this in SQL server?
> Thanks in advance for any help.
> Mark Genovy