Showing posts with label developing. Show all posts
Showing posts with label developing. Show all posts

Monday, March 12, 2012

MS SQL Developer Edition vs MS SQL Production Edition

Hi,
I am not very knowledgable of the MS SQL Server 2000 product range, but
according to a developing team we are in contact with, they have an
application experiencing long query times when several users are performing
queries against their MS SQL Server, which is a Developer Edition version of
MS SQL. As we're soon going to go live with the application, I would like to
know the differences between Developer Edition and any of the Production
Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely to
believe that a Production Edition have better performance, scalability and
stability compared to the Developer Edition, but this is just my thoughts.
Can someone please let me know the major differencies between Production
Editions and Developer Edition. Do you think that we will notice any
performance improvements moving to MS SQL Server Std./Ent. Edition?
Thanks in advance
// BjörnWith the new SQL 2005 product, it's hard to find informations about SQL 2000
on Microsoft website.
Take a look:
http://www.mssqlcity.com/FAQ/General/sql_server_2000_editions.htm
And for the new SQL 2005, take a look here:
http://www.microsoft.com/sql/editions/default.mspx
Carlos A.
"Björn Pettersson" wrote:
> Hi,
> I am not very knowledgable of the MS SQL Server 2000 product range, but
> according to a developing team we are in contact with, they have an
> application experiencing long query times when several users are performing
> queries against their MS SQL Server, which is a Developer Edition version of
> MS SQL. As we're soon going to go live with the application, I would like to
> know the differences between Developer Edition and any of the Production
> Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely to
> believe that a Production Edition have better performance, scalability and
> stability compared to the Developer Edition, but this is just my thoughts.
> Can someone please let me know the major differencies between Production
> Editions and Developer Edition. Do you think that we will notice any
> performance improvements moving to MS SQL Server Std./Ent. Edition?
> Thanks in advance
> // Björn|||"Björn Pettersson" <BjrnPettersson@.discussions.microsoft.com> wrote in
message news:21181F56-24A3-4E0A-8C9E-CEE43E91C5AA@.microsoft.com...
> Hi,
> I am not very knowledgable of the MS SQL Server 2000 product range, but
> according to a developing team we are in contact with, they have an
> application experiencing long query times when several users are
> performing
> queries against their MS SQL Server, which is a Developer Edition version
> of
> MS SQL. As we're soon going to go live with the application, I would like
> to
> know the differences between Developer Edition and any of the Production
> Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely
> to
> believe that a Production Edition have better performance, scalability and
> stability compared to the Developer Edition, but this is just my thoughts.
> Can someone please let me know the major differencies between Production
> Editions and Developer Edition. Do you think that we will notice any
> performance improvements moving to MS SQL Server Std./Ent. Edition?
>
No. Developer edition is exactly the same as Enterprise Edition, exept for
the license. If an app performs poorly on Developer Edition it will not
perform any better on Enterprise.
David

MS SQL Developer Edition vs MS SQL Production Edition

Hi,
I am not very knowledgable of the MS SQL Server 2000 product range, but
according to a developing team we are in contact with, they have an
application experiencing long query times when several users are performing
queries against their MS SQL Server, which is a Developer Edition version of
MS SQL. As we're soon going to go live with the application, I would like to
know the differences between Developer Edition and any of the Production
Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely to
believe that a Production Edition have better performance, scalability and
stability compared to the Developer Edition, but this is just my thoughts.
Can someone please let me know the major differencies between Production
Editions and Developer Edition. Do you think that we will notice any
performance improvements moving to MS SQL Server Std./Ent. Edition?
Thanks in advance
// Bj?rnWith the new SQL 2005 product, it's hard to find informations about SQL 2000
on Microsoft website.
Take a look:
http://www.mssqlcity.com/FAQ/Genera...00_editions.htm
And for the new SQL 2005, take a look here:
http://www.microsoft.com/sql/editions/default.mspx
Carlos A.
"Bj?rn Pettersson" wrote:

> Hi,
> I am not very knowledgable of the MS SQL Server 2000 product range, but
> according to a developing team we are in contact with, they have an
> application experiencing long query times when several users are performin
g
> queries against their MS SQL Server, which is a Developer Edition version
of
> MS SQL. As we're soon going to go live with the application, I would like
to
> know the differences between Developer Edition and any of the Production
> Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely t
o
> believe that a Production Edition have better performance, scalability and
> stability compared to the Developer Edition, but this is just my thoughts.
> Can someone please let me know the major differencies between Production
> Editions and Developer Edition. Do you think that we will notice any
> performance improvements moving to MS SQL Server Std./Ent. Edition?
> Thanks in advance
> // Bj?rn|||"Bjrn Pettersson" <BjrnPettersson@.discussions.microsoft.com> wrote in
message news:21181F56-24A3-4E0A-8C9E-CEE43E91C5AA@.microsoft.com...
> Hi,
> I am not very knowledgable of the MS SQL Server 2000 product range, but
> according to a developing team we are in contact with, they have an
> application experiencing long query times when several users are
> performing
> queries against their MS SQL Server, which is a Developer Edition version
> of
> MS SQL. As we're soon going to go live with the application, I would like
> to
> know the differences between Developer Edition and any of the Production
> Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely
> to
> believe that a Production Edition have better performance, scalability and
> stability compared to the Developer Edition, but this is just my thoughts.
> Can someone please let me know the major differencies between Production
> Editions and Developer Edition. Do you think that we will notice any
> performance improvements moving to MS SQL Server Std./Ent. Edition?
>
No. Developer edition is exactly the same as Enterprise Edition, exept for
the license. If an app performs poorly on Developer Edition it will not
perform any better on Enterprise.
David

MS SQL Developer Edition vs MS SQL Production Edition

Hi,
I am not very knowledgable of the MS SQL Server 2000 product range, but
according to a developing team we are in contact with, they have an
application experiencing long query times when several users are performing
queries against their MS SQL Server, which is a Developer Edition version of
MS SQL. As we're soon going to go live with the application, I would like to
know the differences between Developer Edition and any of the Production
Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely to
believe that a Production Edition have better performance, scalability and
stability compared to the Developer Edition, but this is just my thoughts.
Can someone please let me know the major differencies between Production
Editions and Developer Edition. Do you think that we will notice any
performance improvements moving to MS SQL Server Std./Ent. Edition?
Thanks in advance
// Bj?rn
With the new SQL 2005 product, it's hard to find informations about SQL 2000
on Microsoft website.
Take a look:
http://www.mssqlcity.com/FAQ/General...0_editions.htm
And for the new SQL 2005, take a look here:
http://www.microsoft.com/sql/editions/default.mspx
Carlos A.
"Bj?rn Pettersson" wrote:

> Hi,
> I am not very knowledgable of the MS SQL Server 2000 product range, but
> according to a developing team we are in contact with, they have an
> application experiencing long query times when several users are performing
> queries against their MS SQL Server, which is a Developer Edition version of
> MS SQL. As we're soon going to go live with the application, I would like to
> know the differences between Developer Edition and any of the Production
> Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely to
> believe that a Production Edition have better performance, scalability and
> stability compared to the Developer Edition, but this is just my thoughts.
> Can someone please let me know the major differencies between Production
> Editions and Developer Edition. Do you think that we will notice any
> performance improvements moving to MS SQL Server Std./Ent. Edition?
> Thanks in advance
> // Bj?rn
|||"Bjrn Pettersson" <BjrnPettersson@.discussions.microsoft.com> wrote in
message news:21181F56-24A3-4E0A-8C9E-CEE43E91C5AA@.microsoft.com...
> Hi,
> I am not very knowledgable of the MS SQL Server 2000 product range, but
> according to a developing team we are in contact with, they have an
> application experiencing long query times when several users are
> performing
> queries against their MS SQL Server, which is a Developer Edition version
> of
> MS SQL. As we're soon going to go live with the application, I would like
> to
> know the differences between Developer Edition and any of the Production
> Editions, ex. MS SQL Server Standard or Enterprise Edition. It is likely
> to
> believe that a Production Edition have better performance, scalability and
> stability compared to the Developer Edition, but this is just my thoughts.
> Can someone please let me know the major differencies between Production
> Editions and Developer Edition. Do you think that we will notice any
> performance improvements moving to MS SQL Server Std./Ent. Edition?
>
No. Developer edition is exactly the same as Enterprise Edition, exept for
the license. If an app performs poorly on Developer Edition it will not
perform any better on Enterprise.
David

Saturday, February 25, 2012

MS SQL 2005 and PDC Confusion

hello everyone, I am kind of confused with MS SQL 2005. I have friends who have been developing with MS SQL. They told me that in order to have a MS SQL Server, one need to have a PDC.

This is really a problem since I am behind a Unix box acting as a firewall/gateway. AFAIK, to install a PDC means that DHCP comes with it and DNS. This is really a problem...

Is it possible to have a MS SQL server without having to create a PDC? If so, how do I connect to my database on an MS SQL server. I develop in VB. I would appreciate any help/tips... TIA :D

You don′t need a PDC, you will need a domain only if you want to do WIndows authentication along with more than one computer. Otherwise you can use SQL Server authentication.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Monday, February 20, 2012

MS SQL - Professional Assistance required concerning Capacity.

Hi there,

We are currently developing a E-Com research site where subscribed members can conduct market research. The web site is developed and ready to go, however we are undecided what is required on the Database side and could do with some of your expert help.

Users will be conducting research on our MS SQL database. The database holds every product sale made by a select number of consumer good companies. The database holds 12 million records at any one time, however overall the database is very static and is not updated online. We intend to only store 1 months data, therefore on a weekly basis we delete old & add new records.

We are offering three categories of searches on the DB.
1. By Seller
2. By Category (i.e. Hair Care, Laundry etc)
3. By Sale.

The first two searches are not performance intensive as they are compiled and stored in the database - therefore no need for calculation online. Our main concern is the 3rd report. This report is where we allow the user to search for a specified search string. Therefore in the main table that holds all the sales, we have a full-text index for the field "Product Description".

What we are unclear on is the Capacity requirements regarding providing such functionality. I.e What server do we require?

We have researched many articles and have absorbed all the information regarding multiple disk controllers, lots of memory etc.. etc.. However we still have not been able to obtain an idea on what Server would serve our purposes. For example: would the following server do the job?

2 x 2.4Ghz Hyper-threading Xeon CPUs with 512Kb Cache and 400MHz System Bus
2GB Samsung RAMBUS 800-45 Memory (RIMMS / RDRAM)

A lot is determined by the usage, i.e. how many queries are executed per minute etc. At present we do not have a clear idea on the number of users. However we are not truely concerned about this as the 3rd report needs to execute and return within a short period of time. That is our main concern.

Therefore our question is as follows: If you were going to host a database that consisted of 12 million records & full-text indexing which had to be queried in a few seconds, what would you purchase?

We ask you to consider that funds are extremely tight and although the new latest server may do the job, it is most likely out of our budget. We are looking for the most cost effective solution but still statisfying the purpose.

Kind regards
AngusPerformance tuning isn't an exact science. Especially when there isn't a good test base where you can make and test your proposed changes, the whole thing is subject to a lot of opinion rather than fact.

In my opinion, your search will almost certainly be disk bound rather than CPU bound. Fast disk is important, but redundancy gets expensive fast... I'd suggest all of the RAM you can and the fastest drive subsystem that you can afford.

-PatP