MSSQL 2000 Developer Edition limit of connection ?

J.H wrote:
> Dear All,
> I've been searching the MSDN web for the MSSQL 2000 Developer connection
> limit.
> However, could not find any authentic documentation that says MSSQL 2000
> Developer
> connection information.
> With MSSQL 2000 Developer Edition, do we have any limitation of connection
> direct to
> database? We do have user connecting to this database through http/asp, an
d
> plus user connecting direct to database by 1433. However those users conne
ct
> direct to database by
> 1433 getting low performance, slow, sometimes got disconnection from the
> MSSQL 2000
> Developer Edition that we have.
> Our server is single Xeon enabled hyperthreading 2 logical map to 1 physic
al
> (this is another
> factor for slow performance), this server has MSSQL 2000 Developer Edition
> installed.
> Thanks for any input,
> JH
There is no connection limit specific to Dev Edition.
Make sure that you enable only 1 logical processor per physical
processor in SQL Server.
Note that Developer Edition is licensed for development and testing use
only.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--Hi David,
Is there any explaination why it is fast on clients that access from
HTTP/ASAP page and
slown performance/disconnection on client accessig database through ODBC
1433?
Thanks for any input,
JH
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1150828951.963023.188820@.g10g2000cwb.googlegroups.com...
> J.H wrote:
connection[vbcol=seagreen]
and[vbcol=seagreen]
connect[vbcol=seagreen]
physical[vbcol=seagreen]
Edition[vbcol=seagreen]
> There is no connection limit specific to Dev Edition.
> Make sure that you enable only 1 logical processor per physical
> processor in SQL Server.
> Note that Developer Edition is licensed for development and testing use
> only.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||Dear All,
I've been searching the MSDN web for the MSSQL 2000 Developer connection
limit.
However, could not find any authentic documentation that says MSSQL 2000
Developer
connection information.
With MSSQL 2000 Developer Edition, do we have any limitation of connection
direct to
database? We do have user connecting to this database through http/asp, and
plus user connecting direct to database by 1433. However those users connect
direct to database by
1433 getting low performance, slow, sometimes got disconnection from the
MSSQL 2000
Developer Edition that we have.
Our server is single Xeon enabled hyperthreading 2 logical map to 1 physical
(this is another
factor for slow performance), this server has MSSQL 2000 Developer Edition
installed.
Thanks for any input,
JH|||J.H wrote:
> Dear All,
> I've been searching the MSDN web for the MSSQL 2000 Developer connection
> limit.
> However, could not find any authentic documentation that says MSSQL 2000
> Developer
> connection information.
> With MSSQL 2000 Developer Edition, do we have any limitation of connection
> direct to
> database? We do have user connecting to this database through http/asp, an
d
> plus user connecting direct to database by 1433. However those users conne
ct
> direct to database by
> 1433 getting low performance, slow, sometimes got disconnection from the
> MSSQL 2000
> Developer Edition that we have.
> Our server is single Xeon enabled hyperthreading 2 logical map to 1 physic
al
> (this is another
> factor for slow performance), this server has MSSQL 2000 Developer Edition
> installed.
> Thanks for any input,
> JH
There is no connection limit specific to Dev Edition.
Make sure that you enable only 1 logical processor per physical
processor in SQL Server.
Note that Developer Edition is licensed for development and testing use
only.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Hi David,
Is there any explaination why it is fast on clients that access from
HTTP/ASAP page and
slown performance/disconnection on client accessig database through ODBC
1433?
Thanks for any input,
JH
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1150828951.963023.188820@.g10g2000cwb.googlegroups.com...
> J.H wrote:
connection[vbcol=seagreen]
and[vbcol=seagreen]
connect[vbcol=seagreen]
physical[vbcol=seagreen]
Edition[vbcol=seagreen]
> There is no connection limit specific to Dev Edition.
> Make sure that you enable only 1 logical processor per physical
> processor in SQL Server.
> Note that Developer Edition is licensed for development and testing use
> only.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>

MSSQL 2000 Developer Edition limit of connection ?

Dear All,
I've been searching the MSDN web for the MSSQL 2000 Developer connection
limit.
However, could not find any authentic documentation that says MSSQL 2000
Developer
connection information.
With MSSQL 2000 Developer Edition, do we have any limitation of connection
direct to
database? We do have user connecting to this database through http/asp, and
plus user connecting direct to database by 1433. However those users connect
direct to database by
1433 getting low performance, slow, sometimes got disconnection from the
MSSQL 2000
Developer Edition that we have.
Our server is single Xeon enabled hyperthreading 2 logical map to 1 physical
(this is another
factor for slow performance), this server has MSSQL 2000 Developer Edition
installed.
Thanks for any input,
JHJ.H wrote:
> Dear All,
> I've been searching the MSDN web for the MSSQL 2000 Developer connection
> limit.
> However, could not find any authentic documentation that says MSSQL 2000
> Developer
> connection information.
> With MSSQL 2000 Developer Edition, do we have any limitation of connection
> direct to
> database? We do have user connecting to this database through http/asp, and
> plus user connecting direct to database by 1433. However those users connect
> direct to database by
> 1433 getting low performance, slow, sometimes got disconnection from the
> MSSQL 2000
> Developer Edition that we have.
> Our server is single Xeon enabled hyperthreading 2 logical map to 1 physical
> (this is another
> factor for slow performance), this server has MSSQL 2000 Developer Edition
> installed.
> Thanks for any input,
> JH
There is no connection limit specific to Dev Edition.
Make sure that you enable only 1 logical processor per physical
processor in SQL Server.
Note that Developer Edition is licensed for development and testing use
only.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Hi David,
Is there any explaination why it is fast on clients that access from
HTTP/ASAP page and
slown performance/disconnection on client accessig database through ODBC
1433?
Thanks for any input,
JH
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1150828951.963023.188820@.g10g2000cwb.googlegroups.com...
> J.H wrote:
> > Dear All,
> >
> > I've been searching the MSDN web for the MSSQL 2000 Developer connection
> > limit.
> > However, could not find any authentic documentation that says MSSQL 2000
> > Developer
> > connection information.
> >
> > With MSSQL 2000 Developer Edition, do we have any limitation of
connection
> > direct to
> > database? We do have user connecting to this database through http/asp,
and
> > plus user connecting direct to database by 1433. However those users
connect
> > direct to database by
> > 1433 getting low performance, slow, sometimes got disconnection from the
> > MSSQL 2000
> > Developer Edition that we have.
> >
> > Our server is single Xeon enabled hyperthreading 2 logical map to 1
physical
> > (this is another
> > factor for slow performance), this server has MSSQL 2000 Developer
Edition
> > installed.
> >
> > Thanks for any input,
> > JH
> There is no connection limit specific to Dev Edition.
> Make sure that you enable only 1 logical processor per physical
> processor in SQL Server.
> Note that Developer Edition is licensed for development and testing use
> only.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>

MSSQL 2000 Developer connection limit & boolean connection

Dear All,
I've been searching the MSDN web for the MSSQL 2000 Developer connection
limit.
However, could not find any authentic documentation that says MSSQL 2000
Developer
connection information.
With MSSQL 2000 Developer Edition, do we have any limitation of connection
direct to
database? We do have user connecting to this database through http/asp, and
plus user connecting direct to database by 1433. However those users connect
direct to database by
1433 getting low performance, slow, sometimes got disconnection from the
MSSQL 2000
Developer Edition that we have.
Our server is single Xeon enabled hyperthreading 2 logical map to 1 physical
(this is another
factor for slow performance), this server has MSSQL 2000 Developer Edition
installed.
Thanks for any input,
JHHi,
there is no connection limit to SQL Server Dev Edition as there is none
for all the editions, this one for SQL Server MSDE isn=B4t actually a
limitation, its a trotteling of the engine, as the query governour will
keep track of the concurrent *queries* not connections.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Hi,
there is no connection limit to SQL Server Dev Edition as there is none
for all the editions, this one for SQL Server MSDE isn=B4t actually a
limitation, its a trotteling of the engine, as the query governour will
keep track of the concurrent *queries* not connections.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--

MSDNs Estimating the Size of a Table

I was hoping I can get some help regarding subject mater located at
http://msdn.microsoft.com/library/d...des_02_92k3.asp

MyTable has 23 fields with 100,000 records.
Field1 nvarchar 90
Field2 char 6
Field3 varchar 8000
Field4 nvarchar 200
Field5 nvarchar 200
Field6 nvarchar 200
Field7 nvarchar 200
Field8 nvarchar 200
Field9 char 30
Field10 char 30
Field11 nvarchar 200
Field12 nvarchar 200
Field13 float 8
Field14 datetime 8
Field15 datetime 8
Field16 datetime 8
Field17 nvarchar 200
Field18 nvarchar 200
Field19 varchar 8000
Field20 nvarchar 200
Field21 nvarchar 200
Field22 nvarchar 200
Field23 varchar 8000

Data Types:
nvarchar = Variable-length, Storage is 2 times the # of characters entered
char = Fixed-length. Storage is n bytes
varchar = Variable-length, Storage is actual length in bytes of data entered
float = Is float Fixed-length?, my precisions are 15 digits so 8 bytes.
datetime = Is datetime Fixed-length?, Storage is 8 bytes

I need the following blanks filled in for me, please :-)

Num_Rows 100,000
Num_Cols 23
Fixed_Data_Size
Num_Variable_Cols 16
Max_Var_Size
Null_Bitmap Int(2 + ((23 + 7) / 8)) = 5?
Variable_Data_Size
Row_Size
Rows_Per_Page
Free_Rows_Per_Page 100 (no clustered index created)
Num_Pages
Table Size"TZone" <TZone@.optus.com.au> wrote in message
news:3f2e4086$0$14563$afc38c87@.news.optusnet.com.a u...
> I was hoping I can get some help regarding subject mater located at
http://msdn.microsoft.com/library/d...des_02_92k3.asp

<snip
You're correct that float and datetime are fixed length, and both are indeed
8 bytes (for your float precision, as you noted), which seems to be your
main question. You just need to follow the formulas in the documentation.

One point you may need to consider is how full the average variable length
column will be - if you know that almost all data in an nvarchar(100) column
will be around 50 Unicode characters, ie. half the length of the field, then
you could count that as 100 bytes instead of 200 to get a more accurate
estimate. Or if the average will be around 75, then count 150 etc. But
you're the only person who knows what your data looks like, so you're the
best person to calculate the size of the table.

Simon|||After following formula in documentation I arrive at:

Num_Rows = 100,000
Num_Cols = 23
Fixed_Data_Size = 98 bytes
Num_Variable_Cols = 16 fields
Max_Var_Size = 8000 bytes ** Field3 is varchar with length 8000, so is this
8000 bytes?***
Null_Bitmap = 5
Variable_Data_Size = 8034
Row_Size = 8141
Rows_Per_Page = (INT(8096/(Row_Size + 2)) ** is zero correct?**
Free_Rows_Per_Page = 100 (I have no clustered index)
Num_Pages = -1000 ** is this correct, a negative Num_Pages?**
Total Size (Mb) = -7.81

MyTable has 23 fields with 100,000 records.
Field1 nvarchar 90 * variable*
Field2 char 6 *fixed*
Field3 varchar 8000 *variable*
Field4 nvarchar 200 *variable*
Field5 nvarchar 200 *variable*
Field6 nvarchar 200 *variable*
Field7 nvarchar 200 *variable*
Field8 nvarchar 200 *variable*
Field9 char 30 *fixed*
Field10 char 30 *fixed*
Field11 nvarchar 200 *variable*
Field12 nvarchar 200 *variable*
Field13 float 8 *fixed*
Field14 datetime 8 *fixed*
Field15 datetime 8 *fixed*
Field16 datetime 8 *fixed*
Field17 nvarchar 200 *variable*
Field18 nvarchar 200 *variable*
Field19 varchar 8000 *variable*
Field20 nvarchar 200 *variable*
Field21 nvarchar 200 *variable*
Field22 nvarchar 200 *variable*
Field23 varchar 8000 *variable*

I'm going to assume all variable fields are close to maximum capacity.

Thanks for previous reply Simon!

"Simon Hayes" <sql@.hayes.ch> wrote in message
news:3f2ec4e7$1_1@.news.bluewin.ch...
> "TZone" <TZone@.optus.com.au> wrote in message
> news:3f2e4086$0$14563$afc38c87@.news.optusnet.com.a u...
> > I was hoping I can get some help regarding subject mater located at
http://msdn.microsoft.com/library/d...des_02_92k3.asp
> <snip>
> You're correct that float and datetime are fixed length, and both are
indeed
> 8 bytes (for your float precision, as you noted), which seems to be your
> main question. You just need to follow the formulas in the documentation.
> One point you may need to consider is how full the average variable length
> column will be - if you know that almost all data in an nvarchar(100)
column
> will be around 50 Unicode characters, ie. half the length of the field,
then
> you could count that as 100 bytes instead of 200 to get a more accurate
> estimate. Or if the average will be around 75, then count 150 etc. But
> you're the only person who knows what your data looks like, so you're the
> best person to calculate the size of the table.
> Simon

MSDN Version of SQLServer 2000 and SQLServer 2005

All,
From a SQLServer installation (both 2000 & 2005), is there a way to find out
if the installation is a MSDN installation. Select @.@.Version does not seem to
indicate anything to that effect.
The previous DBA did a SQLServer installation (2000 & 2005) and I could not
find the 32-bit version of the media. That leads me to believe that he might
have installed it from a MSDN CD/DVD.
Thanks,
rgnNo. You can only tell what edition you have installed.
Jonathan
rgn wrote:
> All,
> From a SQLServer installation (both 2000 & 2005), is there a way to find out
> if the installation is a MSDN installation. Select @.@.Version does not seem to
> indicate anything to that effect.
> The previous DBA did a SQLServer installation (2000 & 2005) and I could not
> find the 32-bit version of the media. That leads me to believe that he might
> have installed it from a MSDN CD/DVD.
> Thanks,
> rgn
>

MSDN version of SQL Server 2005 Connections

If I put an MSDN version of SQL Server 2005 on a server that has IIS
for testing does the IIS users get limited to 10 connections to SQL at
once or is it considered 1 connection?
I need to know so we can use it as a test platform of load testing of
several hundered 100 or so users before moving to the production
version of SQL...which is not here yet...I dont want to think any
problems of connections or timeouts are due to using the MSDN version
for testing and development.
Thanks, Ed,
No. Whether it's from MSDN or not has no bearing on the feature set, that
simply depends on what edition you use
(Dev/Standard/Enterprise/Workgroup/Express). What it does have a bearing on
is licensing.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131130353.177316.126630@.g14g2000cwa.googlegr oups.com...
> If I put an MSDN version of SQL Server 2005 on a server that has IIS
> for testing does the IIS users get limited to 10 connections to SQL at
> once or is it considered 1 connection?
> I need to know so we can use it as a test platform of load testing of
> several hundered 100 or so users before moving to the production
> version of SQL...which is not here yet...I dont want to think any
> problems of connections or timeouts are due to using the MSDN version
> for testing and development.
> Thanks, Ed,
>
|||Sorry, forgot to say
SQL 2005 "Enterprise Edition"
I know some MSDN things like OS limit to 10, worried that it will limit
me
Ed,
|||What I am wondering is if I use the MSDN Enterprise Edition of SQL for
the backend of my development web server will it only allow 10 people
to connect to my web pages that have codebehind accessing the database,
or get some type of connection error in my code after 10 users or will
it not limit me for my testing of over 100 web users?
All users connect via IIS, none have direct connections to SQL
Thansk again Jasper
|||No, there's no feature limitation (that I'm aware of) - it's purely a
licensing thing
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131146290.037020.56980@.g14g2000cwa.googlegro ups.com...
> What I am wondering is if I use the MSDN Enterprise Edition of SQL for
> the backend of my development web server will it only allow 10 people
> to connect to my web pages that have codebehind accessing the database,
> or get some type of connection error in my code after 10 users or will
> it not limit me for my testing of over 100 web users?
> All users connect via IIS, none have direct connections to SQL
> Thansk again Jasper
>
|||Thanks
|||Thanks

MSDN version of SQL Server 2005 Connections

If I put an MSDN version of SQL Server 2005 on a server that has IIS
for testing does the IIS users get limited to 10 connections to SQL at
once or is it considered 1 connection?
I need to know so we can use it as a test platform of load testing of
several hundered 100 or so users before moving to the production
version of SQL...which is not here yet...I dont want to think any
problems of connections or timeouts are due to using the MSDN version
for testing and development.
Thanks, Ed,No. Whether it's from MSDN or not has no bearing on the feature set, that
simply depends on what edition you use
(Dev/Standard/Enterprise/Workgroup/Express). What it does have a bearing on
is licensing.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131130353.177316.126630@.g14g2000cwa.googlegroups.com...
> If I put an MSDN version of SQL Server 2005 on a server that has IIS
> for testing does the IIS users get limited to 10 connections to SQL at
> once or is it considered 1 connection?
> I need to know so we can use it as a test platform of load testing of
> several hundered 100 or so users before moving to the production
> version of SQL...which is not here yet...I dont want to think any
> problems of connections or timeouts are due to using the MSDN version
> for testing and development.
> Thanks, Ed,
>|||Sorry, forgot to say
SQL 2005 "Enterprise Edition"
I know some MSDN things like OS limit to 10, worried that it will limit
me
Ed,|||What I am wondering is if I use the MSDN Enterprise Edition of SQL for
the backend of my development web server will it only allow 10 people
to connect to my web pages that have codebehind accessing the database,
or get some type of connection error in my code after 10 users or will
it not limit me for my testing of over 100 web users?
All users connect via IIS, none have direct connections to SQL
Thansk again Jasper|||No, there's no feature limitation (that I'm aware of) - it's purely a
licensing thing
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131146290.037020.56980@.g14g2000cwa.googlegroups.com...
> What I am wondering is if I use the MSDN Enterprise Edition of SQL for
> the backend of my development web server will it only allow 10 people
> to connect to my web pages that have codebehind accessing the database,
> or get some type of connection error in my code after 10 users or will
> it not limit me for my testing of over 100 web users?
> All users connect via IIS, none have direct connections to SQL
> Thansk again Jasper
>|||Thanks|||Thanks

MSDN version of SQL Server 2005 Connections

If I put an MSDN version of SQL Server 2005 on a server that has IIS
for testing does the IIS users get limited to 10 connections to SQL at
once or is it considered 1 connection?
I need to know so we can use it as a test platform of load testing of
several hundered 100 or so users before moving to the production
version of SQL...which is not here yet...I dont want to think any
problems of connections or timeouts are due to using the MSDN version
for testing and development.
Thanks, Ed,No. Whether it's from MSDN or not has no bearing on the feature set, that
simply depends on what edition you use
(Dev/Standard/Enterprise/Workgroup/Express). What it does have a bearing on
is licensing.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131130353.177316.126630@.g14g2000cwa.googlegroups.com...
> If I put an MSDN version of SQL Server 2005 on a server that has IIS
> for testing does the IIS users get limited to 10 connections to SQL at
> once or is it considered 1 connection?
> I need to know so we can use it as a test platform of load testing of
> several hundered 100 or so users before moving to the production
> version of SQL...which is not here yet...I dont want to think any
> problems of connections or timeouts are due to using the MSDN version
> for testing and development.
> Thanks, Ed,
>|||Sorry, forgot to say
SQL 2005 "Enterprise Edition"
I know some MSDN things like OS limit to 10, worried that it will limit
me
Ed,|||What I am wondering is if I use the MSDN Enterprise Edition of SQL for
the backend of my development web server will it only allow 10 people
to connect to my web pages that have codebehind accessing the database,
or get some type of connection error in my code after 10 users or will
it not limit me for my testing of over 100 web users?
All users connect via IIS, none have direct connections to SQL
Thansk again Jasper|||No, there's no feature limitation (that I'm aware of) - it's purely a
licensing thing
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131146290.037020.56980@.g14g2000cwa.googlegroups.com...
> What I am wondering is if I use the MSDN Enterprise Edition of SQL for
> the backend of my development web server will it only allow 10 people
> to connect to my web pages that have codebehind accessing the database,
> or get some type of connection error in my code after 10 users or will
> it not limit me for my testing of over 100 web users?
> All users connect via IIS, none have direct connections to SQL
> Thansk again Jasper
>|||Thanks|||Thanks

MSDN Version of SQL Server

Hi,
I have SQL Server 2000 standard edition from MSDN installed on what will now
become a production server. I have since purchased a 1 processor licence. My
question is there any reason not to continue using the MSDN version in
production? Or should I uninstall it and use the purchased version.
Thanks
NIsnt there a limit to the number of CPUs and RAM that MSDN copy can handle.
We had this problem once in SQLServer 7 and we eventually had to Backup
DB/uninstall MSDN version/Install Licensed Version and
Restore the Databases.
Whatever reason, you should always install a Licensed version in a
Production Version. What if you have to call PSS for some
reason ?
Gopi
"NH" <NH@.discussions.microsoft.com> wrote in message
news:4C998CC4-C4E9-41A2-BE48-197A5A4DDE8F@.microsoft.com...
> Hi,
> I have SQL Server 2000 standard edition from MSDN installed on what will
> now
> become a production server. I have since purchased a 1 processor licence.
> My
> question is there any reason not to continue using the MSDN version in
> production? Or should I uninstall it and use the purchased version.
> Thanks
> N|||For SQL7, MSDN came with Desktop Edition (not to be with what we no
w call Desktop Engine,
AKA MSDE). Desktop Edition has such restrictions.
For 2000, MSDN comes with Developer Edition which is identical to Enterprise
Edition, but you are
now allowed to run in production environment.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gopinath Rajee" <gopinathr@.healthasyst.com> wrote in message
news:urNSfT2DFHA.1396@.tk2msftngp13.phx.gbl...
> Isnt there a limit to the number of CPUs and RAM that MSDN copy can handle
.
> We had this problem once in SQLServer 7 and we eventually had to Backup DB
/uninstall MSDN
> version/Install Licensed Version and
> Restore the Databases.
> Whatever reason, you should always install a Licensed version in a Product
ion Version. What if you
> have to call PSS for some
> reason ?
> Gopi
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:4C998CC4-C4E9-41A2-BE48-197A5A4DDE8F@.microsoft.com...
>|||Also...

> Whatever reason, you should always install a Licensed version in a Product
ion Version. What if you
> have to call PSS for some
> reason ?
I couldn't agree more. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gopinath Rajee" <gopinathr@.healthasyst.com> wrote in message
news:urNSfT2DFHA.1396@.tk2msftngp13.phx.gbl...
> Isnt there a limit to the number of CPUs and RAM that MSDN copy can handle
.
> We had this problem once in SQLServer 7 and we eventually had to Backup DB
/uninstall MSDN
> version/Install Licensed Version and
> Restore the Databases.
> Whatever reason, you should always install a Licensed version in a Product
ion Version. What if you
> have to call PSS for some
> reason ?
> Gopi
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:4C998CC4-C4E9-41A2-BE48-197A5A4DDE8F@.microsoft.com...
>|||Thanks for the replies.
However, do you know if the MSDN version of SQL Standard Edition differs
from the one you purchase?
"Tibor Karaszi" wrote:

> Also...
>
> I couldn't agree more. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Gopinath Rajee" <gopinathr@.healthasyst.com> wrote in message
> news:urNSfT2DFHA.1396@.tk2msftngp13.phx.gbl...
>
>|||MSDN doesn't come with production licenses. It might some with SE as well as
EE and Dev Ed. But you
are still not allowed to run in production environment. See
http://msdn.microsoft.com/subscript...ng/default.aspx
A quote from above:
"MSDN Universal, MSDN Enterprise, MSDN Professional and MSDN Operating Syste
ms are licensed for
single users, and can only be used by licensed subscribers. All products tha
t ship in MSDN
Subscriptions are for development and test purposes only, and cannot be used
in a live production
environment."
You also might find something valuable at :
http://msdn.microsoft.com/subscript...lt.aspx#support
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"NH" <NH@.discussions.microsoft.com> wrote in message
news:19D4DE6A-4093-48EB-B900-7606C7F42A16@.microsoft.com...
> Thanks for the replies.
> However, do you know if the MSDN version of SQL Standard Edition differs
> from the one you purchase?
> "Tibor Karaszi" wrote:
>|||Hi,
I realise MSDN versions of SQL Standard are "not allowed to run in
production environment". But what I am asking is does MSDN version of SQL
Standard differ from the version you would buy (OEM type). Are there
restrictions on RAM, connections etc etc?
"Tibor Karaszi" wrote:

> MSDN doesn't come with production licenses. It might some with SE as well
as EE and Dev Ed. But you
> are still not allowed to run in production environment. See
> http://msdn.microsoft.com/subscript...ng/default.aspx
> A quote from above:
> "MSDN Universal, MSDN Enterprise, MSDN Professional and MSDN Operating Sys
tems are licensed for
> single users, and can only be used by licensed subscribers. All products t
hat ship in MSDN
> Subscriptions are for development and test purposes only, and cannot be us
ed in a live production
> environment."
>
> You also might find something valuable at :
> http://msdn.microsoft.com/subscript...lt.aspx#support
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:19D4DE6A-4093-48EB-B900-7606C7F42A16@.microsoft.com...
>
>|||> Are there
> restrictions on RAM, connections etc etc?
No.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"NH" <NH@.discussions.microsoft.com> wrote in message
news:D3D585A4-1C12-4203-9640-8ED39685B371@.microsoft.com...
> Hi,
> I realise MSDN versions of SQL Standard are "not allowed to run in
> production environment". But what I am asking is does MSDN version of SQL
> Standard differ from the version you would buy (OEM type). Are there
> restrictions on RAM, connections etc etc?
> "Tibor Karaszi" wrote:
>|||Thanks for your help.
N
"Tibor Karaszi" wrote:

> No.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:D3D585A4-1C12-4203-9640-8ED39685B371@.microsoft.com...
>
>

MSDN Subscription SQL Server 2000

If we purchase a new MSDN Professional subscription, does it come with SQL Server 2000 developer license?Hi,

SQL Server is only not included in the MSDN Operation System and library subscriptions. For the rest a SQL Server Developer version is included, since now I am able to see 2005, 2000 and 6.5 in the download area.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Thanks a lot.

MSDN Subscription Level for latest Yukon CTP

I'm working on some research that requires me to have access to the
latest CTP of Yukon, and I know it's available via MSDN subscription.
Can anyone tell me the minimum subscription level required to have
download access to the CTP?
Thanks
AllenSearch for SQL ServerT 2005 within
http://msdn.microsoft.com/subscript...ackinglist.aspx
It looks like it is included with MSDN Professional.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:825fv05697ud46c5iqrm63r9gl8fhep73e@.
4ax.com...
> I'm working on some research that requires me to have access to the
> latest CTP of Yukon, and I know it's available via MSDN subscription.
> Can anyone tell me the minimum subscription level required to have
> download access to the CTP?
> Thanks
> Allen|||Thanks, Kieth, but in the shipment lists in all levels it only shows
Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
is available for download on the web site at least at the Universal
level. I'm looking to find out the minimum level at which it's
available.
Allen
On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
<sqlguy.back2u@.comcast.net> wrote:

>Search for SQL ServerT 2005 within
>http://msdn.microsoft.com/subscript...ackinglist.aspx
>It looks like it is included with MSDN Professional.|||My point is:
If it ships with version x of the MSDN Subscription then it should be
available via the download center.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:lm6fv0h1d1r4mdjmjeiedsro5g2nbe9jnp@.
4ax.com...
> Thanks, Kieth, but in the shipment lists in all levels it only shows
> Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
> is available for download on the web site at least at the Universal
> level. I'm looking to find out the minimum level at which it's
> available.
> Allen
> On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
> <sqlguy.back2u@.comcast.net> wrote:
>
>|||Keith Kratochvil wrote:

>My point is:
>If it ships with version x of the MSDN Subscription then it should be
>available via the download center.
>
>
Yes, but the converse is not true. The download center provides much more
than what is shipped. The CTP builds of SQL Server, not the Beta releases,
are what the poster asked about, and they are not included in any MSDN
shipments, so the shipment lists won't help answer the question.
I believe the two CTP builds released so far are available to all
MSDN subscribers, regardless of subscription level. At least that's
what it says at
http://www.microsoft.com/presspass/...erLowCostPR.asp
I haven't heard anyone complain that they are an MSDN
subscriber but couldn't get the CTP, either. For the record,
the December CTP of the Express version (the SQL engine
with some limitations and no tools) is available to anyone,
MSDN subscriber or not, here:
http://lab.msdn.microsoft.com/express/sql/
Steve Kass
Drew University|||Thanks
Keith|||Thanks, Steve. That linked helped a lot.
Allen
On Wed, 26 Jan 2005 09:35:31 -0500, Steve Kass <skass@.drew.edu> wrote:

>
>Keith Kratochvil wrote:
>
>Yes, but the converse is not true. The download center provides much more
>than what is shipped. The CTP builds of SQL Server, not the Beta releases,
>are what the poster asked about, and they are not included in any MSDN
>shipments, so the shipment lists won't help answer the question.
>I believe the two CTP builds released so far are available to all
>MSDN subscribers, regardless of subscription level. At least that's
>what it says at
>http://www.microsoft.com/presspass/...om/express/sql/
>Steve Kass
>Drew University

MSDN Subscription Level for latest Yukon CTP

I'm working on some research that requires me to have access to the
latest CTP of Yukon, and I know it's available via MSDN subscription.
Can anyone tell me the minimum subscription level required to have
download access to the CTP?
Thanks
Allen
Search for SQL ServerT 2005 within
http://msdn.microsoft.com/subscripti...ckinglist.aspx
It looks like it is included with MSDN Professional.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:825fv05697ud46c5iqrm63r9gl8fhep73e@.4ax.com...
> I'm working on some research that requires me to have access to the
> latest CTP of Yukon, and I know it's available via MSDN subscription.
> Can anyone tell me the minimum subscription level required to have
> download access to the CTP?
> Thanks
> Allen
|||Thanks, Kieth, but in the shipment lists in all levels it only shows
Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
is available for download on the web site at least at the Universal
level. I'm looking to find out the minimum level at which it's
available.
Allen
On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
<sqlguy.back2u@.comcast.net> wrote:

>Search for SQL ServerT 2005 within
>http://msdn.microsoft.com/subscripti...ckinglist.aspx
>It looks like it is included with MSDN Professional.
|||My point is:
If it ships with version x of the MSDN Subscription then it should be
available via the download center.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:lm6fv0h1d1r4mdjmjeiedsro5g2nbe9jnp@.4ax.com...
> Thanks, Kieth, but in the shipment lists in all levels it only shows
> Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
> is available for download on the web site at least at the Universal
> level. I'm looking to find out the minimum level at which it's
> available.
> Allen
> On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
> <sqlguy.back2u@.comcast.net> wrote:
>
|||Keith Kratochvil wrote:

>My point is:
>If it ships with version x of the MSDN Subscription then it should be
>available via the download center.
>
>
Yes, but the converse is not true. The download center provides much more
than what is shipped. The CTP builds of SQL Server, not the Beta releases,
are what the poster asked about, and they are not included in any MSDN
shipments, so the shipment lists won't help answer the question.
I believe the two CTP builds released so far are available to all
MSDN subscribers, regardless of subscription level. At least that's
what it says at
http://www.microsoft.com/presspass/p...rLowCostPR.asp
I haven't heard anyone complain that they are an MSDN
subscriber but couldn't get the CTP, either. For the record,
the December CTP of the Express version (the SQL engine
with some limitations and no tools) is available to anyone,
MSDN subscriber or not, here:
http://lab.msdn.microsoft.com/express/sql/
Steve Kass
Drew University
|||Thanks
Keith
|||Thanks, Steve. That linked helped a lot.
Allen
On Wed, 26 Jan 2005 09:35:31 -0500, Steve Kass <skass@.drew.edu> wrote:

>
>Keith Kratochvil wrote:
>Yes, but the converse is not true. The download center provides much more
>than what is shipped. The CTP builds of SQL Server, not the Beta releases,
>are what the poster asked about, and they are not included in any MSDN
>shipments, so the shipment lists won't help answer the question.
>I believe the two CTP builds released so far are available to all
>MSDN subscribers, regardless of subscription level. At least that's
>what it says at
>http://www.microsoft.com/presspass/p...rLowCostPR.asp
>I haven't heard anyone complain that they are an MSDN
>subscriber but couldn't get the CTP, either. For the record,
>the December CTP of the Express version (the SQL engine
>with some limitations and no tools) is available to anyone,
>MSDN subscriber or not, here:
>http://lab.msdn.microsoft.com/express/sql/
>Steve Kass
>Drew University

MSDN Subscription Level for latest Yukon CTP

I'm working on some research that requires me to have access to the
latest CTP of Yukon, and I know it's available via MSDN subscription.
Can anyone tell me the minimum subscription level required to have
download access to the CTP?
Thanks
AllenSearch for SQL ServerT 2005 within
http://msdn.microsoft.com/subscriptions/index/packinglist.aspx
It looks like it is included with MSDN Professional.
--
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:825fv05697ud46c5iqrm63r9gl8fhep73e@.4ax.com...
> I'm working on some research that requires me to have access to the
> latest CTP of Yukon, and I know it's available via MSDN subscription.
> Can anyone tell me the minimum subscription level required to have
> download access to the CTP?
> Thanks
> Allen|||Thanks, Kieth, but in the shipment lists in all levels it only shows
Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
is available for download on the web site at least at the Universal
level. I'm looking to find out the minimum level at which it's
available.
Allen
On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
<sqlguy.back2u@.comcast.net> wrote:
>Search for SQL ServerT 2005 within
>http://msdn.microsoft.com/subscriptions/index/packinglist.aspx
>It looks like it is included with MSDN Professional.|||My point is:
If it ships with version x of the MSDN Subscription then it should be
available via the download center.
--
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:lm6fv0h1d1r4mdjmjeiedsro5g2nbe9jnp@.4ax.com...
> Thanks, Kieth, but in the shipment lists in all levels it only shows
> Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
> is available for download on the web site at least at the Universal
> level. I'm looking to find out the minimum level at which it's
> available.
> Allen
> On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
> <sqlguy.back2u@.comcast.net> wrote:
> >Search for SQL ServerT 2005 within
> >http://msdn.microsoft.com/subscriptions/index/packinglist.aspx
> >It looks like it is included with MSDN Professional.
>|||Keith Kratochvil wrote:
>My point is:
>If it ships with version x of the MSDN Subscription then it should be
>available via the download center.
>
>
Yes, but the converse is not true. The download center provides much more
than what is shipped. The CTP builds of SQL Server, not the Beta releases,
are what the poster asked about, and they are not included in any MSDN
shipments, so the shipment lists won't help answer the question.
I believe the two CTP builds released so far are available to all
MSDN subscribers, regardless of subscription level. At least that's
what it says at
http://www.microsoft.com/presspass/press/2004/dec04/12-03ServerLowCostPR.asp
I haven't heard anyone complain that they are an MSDN
subscriber but couldn't get the CTP, either. For the record,
the December CTP of the Express version (the SQL engine
with some limitations and no tools) is available to anyone,
MSDN subscriber or not, here:
http://lab.msdn.microsoft.com/express/sql/
Steve Kass
Drew University|||Thanks
--
Keith|||Thanks, Steve. That linked helped a lot.
Allen
On Wed, 26 Jan 2005 09:35:31 -0500, Steve Kass <skass@.drew.edu> wrote:
>
>Keith Kratochvil wrote:
>>My point is:
>>If it ships with version x of the MSDN Subscription then it should be
>>available via the download center.
>>
>Yes, but the converse is not true. The download center provides much more
>than what is shipped. The CTP builds of SQL Server, not the Beta releases,
>are what the poster asked about, and they are not included in any MSDN
>shipments, so the shipment lists won't help answer the question.
>I believe the two CTP builds released so far are available to all
>MSDN subscribers, regardless of subscription level. At least that's
>what it says at
>http://www.microsoft.com/presspass/press/2004/dec04/12-03ServerLowCostPR.asp
>I haven't heard anyone complain that they are an MSDN
>subscriber but couldn't get the CTP, either. For the record,
>the December CTP of the Express version (the SQL engine
>with some limitations and no tools) is available to anyone,
>MSDN subscriber or not, here:
>http://lab.msdn.microsoft.com/express/sql/
>Steve Kass
>Drew University

MSDN SQL 2k Enterprise CD

Anybody know if the SQL 2k Enterprise Edition that comes on the MSDN DVD/CD
subscription is crippled in any way? I am wondering if there is a processor
limit, memory limit, concurrent user connection limit, etc. Thanks. Want
to run it on a duplicate data center.
EricAs long as it isn't actually the developer edition you should be OK but for
what it sounds like your doing requires an actual license.
--
Andrew J. Kelly
SQL Server MVP
"Eric Sabine" <mopar41@.hhhotmail.com> wrote in message
news:3f099700$0$845$39cecf19@.news.twtelecom.net...
> Anybody know if the SQL 2k Enterprise Edition that comes on the MSDN
DVD/CD
> subscription is crippled in any way? I am wondering if there is a
processor
> limit, memory limit, concurrent user connection limit, etc. Thanks. Want
> to run it on a duplicate data center.
> Eric
>|||This sounds like a licensing issue, not a functionality issue. I don't
think what you're planning on doing is legal... the license that comes with
MSDN is for development and testing only, not for redundancy / clustering /
load balancing...
"Eric Sabine" <mopar41@.hhhotmail.com> wrote in message
news:3f099700$0$845$39cecf19@.news.twtelecom.net...
> Anybody know if the SQL 2k Enterprise Edition that comes on the MSDN
DVD/CD
> subscription is crippled in any way? I am wondering if there is a
processor
> limit, memory limit, concurrent user connection limit, etc. Thanks. Want
> to run it on a duplicate data center.
> Eric
>|||Sorry for not being clear. This is not how you interpreted it, it was my
fault. We have 2 data centers. One live one, one for testing, attacking,
alternate deployment schemas, etc. That second installation of sql2k is for
an upcoming load test under various raid configs. The plan is to have
numerous clients in a test environment network hammer the server. I was
wondering if the install from the MSDN disks had limitations and thus would
not yield legitimate results.
Do you and Aaron believe this type of testing requires a license too? That
is important to know.
Thanks!
Eric
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eQeLckKRDHA.3144@.tk2msftngp13.phx.gbl...
> As long as it isn't actually the developer edition you should be OK but
for
> what it sounds like your doing requires an actual license.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Eric Sabine" <mopar41@.hhhotmail.com> wrote in message
> news:3f099700$0$845$39cecf19@.news.twtelecom.net...
> > Anybody know if the SQL 2k Enterprise Edition that comes on the MSDN
> DVD/CD
> > subscription is crippled in any way? I am wondering if there is a
> processor
> > limit, memory limit, concurrent user connection limit, etc. Thanks.
Want
> > to run it on a duplicate data center.
> >
> > Eric
> >
> >
>|||That sounds like the MSDN version should be fine without the need for a
license other than the MSDN one. There should not be any limitations that
you have to worry about, it is just like the fully licensed version.
--
Andrew J. Kelly
SQL Server MVP
"Eric Sabine" <mopar41@.microsoft's hot mail . com> wrote in message
news:oMjOa.177401$_w.7595224@.twister.southeast.rr.com...
> Sorry for not being clear. This is not how you interpreted it, it was my
> fault. We have 2 data centers. One live one, one for testing, attacking,
> alternate deployment schemas, etc. That second installation of sql2k is
for
> an upcoming load test under various raid configs. The plan is to have
> numerous clients in a test environment network hammer the server. I was
> wondering if the install from the MSDN disks had limitations and thus
would
> not yield legitimate results.
> Do you and Aaron believe this type of testing requires a license too?
That
> is important to know.
> Thanks!
> Eric
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eQeLckKRDHA.3144@.tk2msftngp13.phx.gbl...
> > As long as it isn't actually the developer edition you should be OK but
> for
> > what it sounds like your doing requires an actual license.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "Eric Sabine" <mopar41@.hhhotmail.com> wrote in message
> > news:3f099700$0$845$39cecf19@.news.twtelecom.net...
> > > Anybody know if the SQL 2k Enterprise Edition that comes on the MSDN
> > DVD/CD
> > > subscription is crippled in any way? I am wondering if there is a
> > processor
> > > limit, memory limit, concurrent user connection limit, etc. Thanks.
> Want
> > > to run it on a duplicate data center.
> > >
> > > Eric
> > >
> > >
> >
> >
>

MSDN SQL 2005 versions

I'm a MSDN subscriber and recently installed SQL 2005 developer edition and
noticed it installed a version of visual studio. I'd prefer to install VS
pro edition seperate from SQL 2005. Should I install SQL 2005 Standard
version instead of developer edition and then install Visual Studio Pro
edition?
I couldn't find in the SQL 2005 developer edition install options where to
choose not to install the visual studio version.If you do not want the VS part to be installed, during installation, you can
opt out of installing the Business Intelligence Development Studio. But, you
can install this becuase it gives you access to SSIS, SQLCLR, Analysis
Services projects. Once you install the VS 2005 version, you can use either
of them to do your work.
--
HTH,
SriSamp
Email: srisamp@.gmail.com
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
"Scott" <sbailey@.mileslumber.com> wrote in message
news:%23Mc5DHY8FHA.4076@.tk2msftngp13.phx.gbl...
> I'm a MSDN subscriber and recently installed SQL 2005 developer edition
> and noticed it installed a version of visual studio. I'd prefer to install
> VS pro edition seperate from SQL 2005. Should I install SQL 2005 Standard
> version instead of developer edition and then install Visual Studio Pro
> edition?
> I couldn't find in the SQL 2005 developer edition install options where to
> choose not to install the visual studio version.
>|||"SriSamp" <ssampath@.sct.co.in> wrote in
news:ucxBvVY8FHA.3952@.TK2MSFTNGP12.phx.gbl:

> If you do not want the VS part to be installed, during installation,
> you can opt out of installing the Business Intelligence Development
> Studio. But, you can install this becuase it gives you access to SSIS,
> SQLCLR, Analysis Services projects.
Actually, I do not believe the VS isntalled with SQL Server gives you
access to the SQLCLR projects - I'm not 100% though.
Niels
****************************************
**********
* Niels Berglund
* http://staff.develop.com/nielsb
* nielsb@.no-spam.develop.com
* "A First Look at SQL Server 2005 for Developers"
* http://www.awprofessional.com/title/0321180593
****************************************
**********|||Niels Berglund <nielsb@.develop.com> wrote in
news:Xns9719520FAE996nielsbdevelopcom@.20
7.46.248.16:

> Actually, I do not believe the VS isntalled with SQL Server gives you
> access to the SQLCLR projects - I'm not 100% though.
I am. You cannot open SQLCLR projects with BIDS.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging|||Sorry about that. Since what SQL Server installs is anyways BI related, I
guess SQLCLR is not allowed.
--
HTH,
SriSamp
Email: srisamp@.gmail.com
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
"Ole Kristian Bangs" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns971961B226E4Dolekristianbangaas@.
207.46.248.16...
> Niels Berglund <nielsb@.develop.com> wrote in
> news:Xns9719520FAE996nielsbdevelopcom@.20
7.46.248.16:
>
> I am. You cannot open SQLCLR projects with BIDS.
> --
> Ole Kristian Bangs
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging|||If I install VS 2005 1st, will SQL 2005 pick up on that and not install it's
VS version?
"SriSamp" <ssampath@.sct.co.in> wrote in message
news:ucxBvVY8FHA.3952@.TK2MSFTNGP12.phx.gbl...
> If you do not want the VS part to be installed, during installation, you
> can opt out of installing the Business Intelligence Development Studio.
> But, you can install this becuase it gives you access to SSIS, SQLCLR,
> Analysis Services projects. Once you install the VS 2005 version, you can
> use either of them to do your work.
> --
> HTH,
> SriSamp
> Email: srisamp@.gmail.com
> Blog: http://blogs.sqlxml.org/srinivassampath
> URL: http://www32.brinkster.com/srisamp
> "Scott" <sbailey@.mileslumber.com> wrote in message
> news:%23Mc5DHY8FHA.4076@.tk2msftngp13.phx.gbl...
>|||"Scott" <sbailey@.mileslumber.com> wrote in message
news:uCaM73d8FHA.2644@.TK2MSFTNGP10.phx.gbl...
> If I install VS 2005 1st, will SQL 2005 pick up on that and not install
> it's VS version?
>
Yes, and vice versa. Both products share the VS shell and just install
different components.
David