Diagrams NOT appearing in Enterprise Manager

Hi
I have XP Prof 2002 with SQL Client Tools installed,I can create and view
new diagrams but cannot open and view existing diagrams.
-ANON

Quote:

Originally posted by ANON
Hi
I have XP Prof 2002 with SQL Client Tools installed,I can create and view
new diagrams but cannot open and view existing diagrams.
-ANON

Were you able to figure this out? I am having the EXACT same problem.
Any help would be greatly appreciated.
Thanks,
Jeff

Developing a client server app using SQLServer - Steps

How do we go about setting a C/S application. Here are the steps.
1. Network Operating system.
2. SQL Server 2000 Installation on a Client / Server Network.
3. Install and setup Active Directory Services on a Client / Server
Network.
4. Concept of Domain Controller in a Windows Network.
5. Setup a Domain Model and Client / Server Model on a Network.
6. Secure Databases in Sql Server.
7. Setup and use Windows Authentication in Sql Server.
8. Setup and use SQL Server Authentication.
9. Create Logins in Sql Server.
10. Define Database Roles in Sql Server.
11. Define Server Roles in Sql Server.
12. Use the Enterprise Manager of Sql Server.
13. Use the Query Analyzer of Sql Server.
14. Create a Database.
15. Create a Table using SQL Script.
16. Create Primary Keys and Foreign Keys.
17. Create Indexes, Clustered and Non Clustered Indexes.
18. Establish Connection with SQL Server over a Network.
19. Create a Connection Object.
20. Create a Command Object, its Properties and Methods.
21. Create a Recordset Object in a Visual Basic ( VB ) application.
22. Access SQL Server Database using ADO.
23. Retreive Data From SQL Server Over a client server Network.
24. Create Multiple Command Objects using a Single Connection.
25. Specify a OLEDB data provider in Visual Basic ( VB ) for a client
server application.
26. Pass Connection Information to SQL Server over a network using
Visual Basic ( VB.).
27.Insert a New Record in SQL server using Visual Basic ( VB ).
28.Update and Delete a record using the Execute Method.
29.Execute a Stored Procedure using a Command Object.
30.Create a Input Parameter.
31.Create a Output Parameter.
32.Create Dynamic Recordsets, Keyset Recordsets, Static Recordsets,
Forward Only Recordsets.
33.Create Client Side Only Recordsets.
34.Assign a lock for Client Side Recordsets.
35.Navigate and Bind Controls to a Recordset.
36.Retrieve Fields of Recordsets.
37.Manually Populate Controls.
38.Add a new Record, Modify and Delete a Record.
39.Setup a DNS server.
40.Setup a DHCP Server.
41.Assign IP Address in a Client Server network.
42.Setup a Network Topology.
43.How to Create a Project.
44.How to Create a Menu.
45.SQL Server Security.
46.Standard Security Mode.
47.Setup a Integrated Security Mode.
48.Create Constants.
49.Relational Databases are used in a Client Server Accounting
application.
50.Implement relationships using Key Fields.
51.Client/Server Architecture.
52.Create a Class for developing a database application.
53.Object Oriented Programming is used in a VB/SQL Environment.
54.Use a Datagrid in a VB, Sql server accounting application.
55.Create and Use Standard Modules in a database application.
56.Design the database using SQL Server.
57.Program the Form_Load() event procedure.
58.Program the Form_Activate() event procedure.
59.Program the Cancelbutton.
60.Setup and Validate the data entered in the text box control.
61.Create and Add a Class using Visual basic ( VB ) for a client server
application.
62.How to write Property Procedures.
63.How to write Get Property Procedure.
Any questions email me. Before that you can have a look at the FAQ i
have collected and posted here http://www.vkinfotek.com/faq.html
Regards
MadhWha-a-a-a-t?
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<pedaammulu@.yahoo.com> wrote in message
news:1151489920.428568.278820@.x69g2000cwx.googlegroups.com...
> How do we go about setting a C/S application. Here are the steps.
> 1. Network Operating system.
> 2. SQL Server 2000 Installation on a Client / Server Network.
> 3. Install and setup Active Directory Services on a Client / Server
> Network.
> 4. Concept of Domain Controller in a Windows Network.
> 5. Setup a Domain Model and Client / Server Model on a Network.
> 6. Secure Databases in Sql Server.
> 7. Setup and use Windows Authentication in Sql Server.
> 8. Setup and use SQL Server Authentication.
> 9. Create Logins in Sql Server.
> 10. Define Database Roles in Sql Server.
> 11. Define Server Roles in Sql Server.
> 12. Use the Enterprise Manager of Sql Server.
> 13. Use the Query Analyzer of Sql Server.
> 14. Create a Database.
> 15. Create a Table using SQL Script.
> 16. Create Primary Keys and Foreign Keys.
> 17. Create Indexes, Clustered and Non Clustered Indexes.
> 18. Establish Connection with SQL Server over a Network.
> 19. Create a Connection Object.
> 20. Create a Command Object, its Properties and Methods.
> 21. Create a Recordset Object in a Visual Basic ( VB ) application.
> 22. Access SQL Server Database using ADO.
> 23. Retreive Data From SQL Server Over a client server Network.
> 24. Create Multiple Command Objects using a Single Connection.
> 25. Specify a OLEDB data provider in Visual Basic ( VB ) for a client
> server application.
> 26. Pass Connection Information to SQL Server over a network using
> Visual Basic ( VB.).
> 27.Insert a New Record in SQL server using Visual Basic ( VB ).
> 28.Update and Delete a record using the Execute Method.
> 29.Execute a Stored Procedure using a Command Object.
> 30.Create a Input Parameter.
> 31.Create a Output Parameter.
> 32.Create Dynamic Recordsets, Keyset Recordsets, Static Recordsets,
> Forward Only Recordsets.
> 33.Create Client Side Only Recordsets.
> 34.Assign a lock for Client Side Recordsets.
> 35.Navigate and Bind Controls to a Recordset.
> 36.Retrieve Fields of Recordsets.
> 37.Manually Populate Controls.
> 38.Add a new Record, Modify and Delete a Record.
> 39.Setup a DNS server.
> 40.Setup a DHCP Server.
> 41.Assign IP Address in a Client Server network.
> 42.Setup a Network Topology.
> 43.How to Create a Project.
> 44.How to Create a Menu.
> 45.SQL Server Security.
> 46.Standard Security Mode.
> 47.Setup a Integrated Security Mode.
> 48.Create Constants.
> 49.Relational Databases are used in a Client Server Accounting
> application.
> 50.Implement relationships using Key Fields.
> 51.Client/Server Architecture.
> 52.Create a Class for developing a database application.
> 53.Object Oriented Programming is used in a VB/SQL Environment.
> 54.Use a Datagrid in a VB, Sql server accounting application.
> 55.Create and Use Standard Modules in a database application.
> 56.Design the database using SQL Server.
> 57.Program the Form_Load() event procedure.
> 58.Program the Form_Activate() event procedure.
> 59.Program the Cancelbutton.
> 60.Setup and Validate the data entered in the text box control.
> 61.Create and Add a Class using Visual basic ( VB ) for a client server
> application.
> 62.How to write Property Procedures.
> 63.How to write Get Property Procedure.
> Any questions email me. Before that you can have a look at the FAQ i
> have collected and posted here http://www.vkinfotek.com/faq.html
> Regards
> Madh
>

developer edition vs standard edition

I have an application that a client would like to review.
They have the developer edition of SQL and would like to
try my app before buying the standard edition. Is there
anything they would not be able to do. I have a db that I
will attach with demo data, there are stored procedures,
views, etc.
Thanks in advanceThe Developer edition has the same functionality of the Enterprise =edition, so it can do everything that the Standard edition can do.
-- Keith
"max" <mshaneyfelt@.ciomsult.com> wrote in message =news:00fc01c3d3c5$b4915fb0$a501280a@.phx.gbl...
> I have an application that a client would like to review. > They have the developer edition of SQL and would like to > try my app before buying the standard edition. Is there > anything they would not be able to do. I have a db that I > will attach with demo data, there are stored procedures, > views, etc.
> > Thanks in advance|||In addition to Keith's comment, Dev Edition is meant for development
purposes only. You should not be using it for production.
http://www.microsoft.com/sql/howtobuy/development.asp
--
-oj
http://www.rac4sql.net
"max" <mshaneyfelt@.ciomsult.com> wrote in message
news:00fc01c3d3c5$b4915fb0$a501280a@.phx.gbl...
> I have an application that a client would like to review.
> They have the developer edition of SQL and would like to
> try my app before buying the standard edition. Is there
> anything they would not be able to do. I have a db that I
> will attach with demo data, there are stored procedures,
> views, etc.
> Thanks in advance|||oj, thanks. The client will not use it for production but
they already own the developer edition so this way they
can look at the application before laying out the funds
for a processor license.
>--Original Message--
>In addition to Keith's comment, Dev Edition is meant for
development
>purposes only. You should not be using it for production.
>http://www.microsoft.com/sql/howtobuy/development.asp
>--
>-oj
>http://www.rac4sql.net
>
>"max" <mshaneyfelt@.ciomsult.com> wrote in message
>news:00fc01c3d3c5$b4915fb0$a501280a@.phx.gbl...
>> I have an application that a client would like to
review.
>> They have the developer edition of SQL and would like to
>> try my app before buying the standard edition. Is there
>> anything they would not be able to do. I have a db that
I
>> will attach with demo data, there are stored procedures,
>> views, etc.
>> Thanks in advance
>
>.
>

Developer Edition

Hi All,
I have a question regarding the usage of SQL Server 2005 Developer Edition.
Can I use it in a client - server architecture say I install Developer
edition on a server and install client tools(Management studio / profiler)
on desktops and acess as we use Enterprise Edition? The purpose is only
Development (no production work). I am asking this because ours is a small
Organization with major work is done on SQL Server 2000. Only 1 team is
gonna use 2005.
Thanks,
PradThe license for Developer Edition allows you to install the client tools on
any development computer you desire, and to have as many SQL Servers
installed as you might need, for example, a dev server, a test server, a QA
server, etc.
However, each person (developer or tester -or whoever) accessing the servers
covered with the Developer Edition license MUST have a proper license. (I
think that is currently about $50 (US) each.)
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Prad" <pradeepk@.healthasyst.com> wrote in message
news:%239TXiSY%23GHA.4320@.TK2MSFTNGP02.phx.gbl...
> Hi All,
> I have a question regarding the usage of SQL Server 2005 Developer
> Edition.
> Can I use it in a client - server architecture say I install Developer
> edition on a server and install client tools(Management studio / profiler)
> on desktops and acess as we use Enterprise Edition? The purpose is only
> Development (no production work). I am asking this because ours is a small
> Organization with major work is done on SQL Server 2000. Only 1 team is
> gonna use 2005.
> Thanks,
> Prad
>|||Arnie,
Thanks for replying soon.
I know that we can install Dev Edn on Desktops as you said.
My doubt is whether I can install it on only one server and the
clients(desktop mc/) access it. So that I need to update (run build) only on
the Server rather than updating every m/c.
If not possible, I will have to go for Standard Edn right? Hope you
understud my requirement.
Thanks,
Prad
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eywEjVY%23GHA.3348@.TK2MSFTNGP03.phx.gbl...
> The license for Developer Edition allows you to install the client tools
> on any development computer you desire, and to have as many SQL Servers
> installed as you might need, for example, a dev server, a test server, a
> QA server, etc.
> However, each person (developer or tester -or whoever) accessing the
> servers covered with the Developer Edition license MUST have a proper
> license. (I think that is currently about $50 (US) each.)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "Prad" <pradeepk@.healthasyst.com> wrote in message
> news:%239TXiSY%23GHA.4320@.TK2MSFTNGP02.phx.gbl...
>|||You can install SQL Server Developer Edition on any computer you desire. You
can install it on one or more servers to be accessed by other computers
acting as clients.
Each client that accesses the Developer Edition MUST have a Developer
Edition license. (And of course, they must properly qualify for the
Developer Edition license.)
No Cost for one or more Servers, Developer Edition license for each client
(user).
AS long as ALL the usage qualifies for the Developer Edition license.
Licensing -Developer Edition
My understanding of the Developers Edition license is that you are covered
for a Development server, an Integration/Staging server, even a QA/Test
server, local servers on the developers computer, etc. -as long as no one
except developers access those SQL Servers, and as long as each developer
and/or Tester has a Developer Edition License.
For a more definitive answer, check with the VL folks at: (800) 426-9400.
From: http://www.microsoft.com/sql/editio...er/default.mspx
Each license of SQL Server 2005 Developer Edition entitles one developer to
use the software on as many systems as necessary and additional developers
can use the software by purchasing additional licenses.
From:
http://download.microsoft.com/downl...censingv1.1.doc
DEVELOPER EDITION
SQL Server Developer Edition is a separate product and is used for
development and testing purposes only. It is licensed per developer or
tester (person).
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Prad" <pradeepk@.healthasyst.com> wrote in message
news:OA6SOtY%23GHA.4888@.TK2MSFTNGP04.phx.gbl...
> Arnie,
> Thanks for replying soon.
> I know that we can install Dev Edn on Desktops as you said.
> My doubt is whether I can install it on only one server and the
> clients(desktop mc/) access it. So that I need to update (run build) only
> on the Server rather than updating every m/c.
> If not possible, I will have to go for Standard Edn right? Hope you
> understud my requirement.
> Thanks,
> Prad
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:eywEjVY%23GHA.3348@.TK2MSFTNGP03.phx.gbl...
>|||Thanks a lot. Ive got my doubt cleared...
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eyyhfLZ%23GHA.3312@.TK2MSFTNGP02.phx.gbl...
> You can install SQL Server Developer Edition on any computer you desire.
> You can install it on one or more servers to be accessed by other
> computers acting as clients.
> Each client that accesses the Developer Edition MUST have a Developer
> Edition license. (And of course, they must properly qualify for the
> Developer Edition license.)
> No Cost for one or more Servers, Developer Edition license for each client
> (user).
> AS long as ALL the usage qualifies for the Developer Edition license.
> Licensing -Developer Edition
> My understanding of the Developers Edition license is that you are covered
> for a Development server, an Integration/Staging server, even a QA/Test
> server, local servers on the developers computer, etc. -as long as no one
> except developers access those SQL Servers, and as long as each developer
> and/or Tester has a Developer Edition License.
> For a more definitive answer, check with the VL folks at: (800) 426-9400.
> From: http://www.microsoft.com/sql/editio...er/default.mspx
> Each license of SQL Server 2005 Developer Edition entitles one developer
> to
> use the software on as many systems as necessary and additional developers
> can use the software by purchasing additional licenses.
> From:
> http://download.microsoft.com/downl...censingv1.1.doc
> DEVELOPER EDITION
> SQL Server Developer Edition is a separate product and is used for
> development and testing purposes only. It is licensed per developer or
> tester (person).
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "Prad" <pradeepk@.healthasyst.com> wrote in message
> news:OA6SOtY%23GHA.4888@.TK2MSFTNGP04.phx.gbl...
>

Developer Edition

Hi All,
I have a question regarding the usage of SQL Server 2005 Developer Edition.
Can I use it in a client - server architecture say I install Developer
edition on a server and install client tools(Management studio / profiler)
on desktops and acess as we use Enterprise Edition? The purpose is only
Development (no production work). I am asking this because ours is a small
Organization with major work is done on SQL Server 2000. Only 1 team is
gonna use 2005.
Thanks,
PradThe license for Developer Edition allows you to install the client tools on
any development computer you desire, and to have as many SQL Servers
installed as you might need, for example, a dev server, a test server, a QA
server, etc.
However, each person (developer or tester -or whoever) accessing the servers
covered with the Developer Edition license MUST have a proper license. (I
think that is currently about $50 (US) each.)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Prad" <pradeepk@.healthasyst.com> wrote in message
news:%239TXiSY%23GHA.4320@.TK2MSFTNGP02.phx.gbl...
> Hi All,
> I have a question regarding the usage of SQL Server 2005 Developer
> Edition.
> Can I use it in a client - server architecture say I install Developer
> edition on a server and install client tools(Management studio / profiler)
> on desktops and acess as we use Enterprise Edition? The purpose is only
> Development (no production work). I am asking this because ours is a small
> Organization with major work is done on SQL Server 2000. Only 1 team is
> gonna use 2005.
> Thanks,
> Prad
>|||Arnie,
Thanks for replying soon.
I know that we can install Dev Edn on Desktops as you said.
My doubt is whether I can install it on only one server and the
clients(desktop mc/) access it. So that I need to update (run build) only on
the Server rather than updating every m/c.
If not possible, I will have to go for Standard Edn right? Hope you
understud my requirement.
Thanks,
Prad
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eywEjVY%23GHA.3348@.TK2MSFTNGP03.phx.gbl...
> The license for Developer Edition allows you to install the client tools
> on any development computer you desire, and to have as many SQL Servers
> installed as you might need, for example, a dev server, a test server, a
> QA server, etc.
> However, each person (developer or tester -or whoever) accessing the
> servers covered with the Developer Edition license MUST have a proper
> license. (I think that is currently about $50 (US) each.)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "Prad" <pradeepk@.healthasyst.com> wrote in message
> news:%239TXiSY%23GHA.4320@.TK2MSFTNGP02.phx.gbl...
>> Hi All,
>> I have a question regarding the usage of SQL Server 2005 Developer
>> Edition.
>> Can I use it in a client - server architecture say I install Developer
>> edition on a server and install client tools(Management studio /
>> profiler) on desktops and acess as we use Enterprise Edition? The purpose
>> is only Development (no production work). I am asking this because ours
>> is a small Organization with major work is done on SQL Server 2000. Only
>> 1 team is gonna use 2005.
>> Thanks,
>> Prad
>|||You can install SQL Server Developer Edition on any computer you desire. You
can install it on one or more servers to be accessed by other computers
acting as clients.
Each client that accesses the Developer Edition MUST have a Developer
Edition license. (And of course, they must properly qualify for the
Developer Edition license.)
No Cost for one or more Servers, Developer Edition license for each client
(user).
AS long as ALL the usage qualifies for the Developer Edition license.
Licensing -Developer Edition
My understanding of the Developers Edition license is that you are covered
for a Development server, an Integration/Staging server, even a QA/Test
server, local servers on the developers computer, etc. -as long as no one
except developers access those SQL Servers, and as long as each developer
and/or Tester has a Developer Edition License.
For a more definitive answer, check with the VL folks at: (800) 426-9400.
From: http://www.microsoft.com/sql/editions/developer/default.mspx
Each license of SQL Server 2005 Developer Edition entitles one developer to
use the software on as many systems as necessary and additional developers
can use the software by purchasing additional licenses.
From:
http://download.microsoft.com/download/e/c/a/ecafe5d1-b514-48ab-93eb-61377df9c5c2/SQLServer2005Licensingv1.1.doc
DEVELOPER EDITION
SQL Server Developer Edition is a separate product and is used for
development and testing purposes only. It is licensed per developer or
tester (person).
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Prad" <pradeepk@.healthasyst.com> wrote in message
news:OA6SOtY%23GHA.4888@.TK2MSFTNGP04.phx.gbl...
> Arnie,
> Thanks for replying soon.
> I know that we can install Dev Edn on Desktops as you said.
> My doubt is whether I can install it on only one server and the
> clients(desktop mc/) access it. So that I need to update (run build) only
> on the Server rather than updating every m/c.
> If not possible, I will have to go for Standard Edn right? Hope you
> understud my requirement.
> Thanks,
> Prad
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:eywEjVY%23GHA.3348@.TK2MSFTNGP03.phx.gbl...
>> The license for Developer Edition allows you to install the client tools
>> on any development computer you desire, and to have as many SQL Servers
>> installed as you might need, for example, a dev server, a test server, a
>> QA server, etc.
>> However, each person (developer or tester -or whoever) accessing the
>> servers covered with the Developer Edition license MUST have a proper
>> license. (I think that is currently about $50 (US) each.)
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>> You can't help someone get up a hill without getting a little closer to
>> the top yourself.
>> - H. Norman Schwarzkopf
>>
>> "Prad" <pradeepk@.healthasyst.com> wrote in message
>> news:%239TXiSY%23GHA.4320@.TK2MSFTNGP02.phx.gbl...
>> Hi All,
>> I have a question regarding the usage of SQL Server 2005 Developer
>> Edition.
>> Can I use it in a client - server architecture say I install Developer
>> edition on a server and install client tools(Management studio /
>> profiler) on desktops and acess as we use Enterprise Edition? The
>> purpose is only Development (no production work). I am asking this
>> because ours is a small Organization with major work is done on SQL
>> Server 2000. Only 1 team is gonna use 2005.
>> Thanks,
>> Prad
>>
>|||Thanks a lot. Ive got my doubt cleared...
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eyyhfLZ%23GHA.3312@.TK2MSFTNGP02.phx.gbl...
> You can install SQL Server Developer Edition on any computer you desire.
> You can install it on one or more servers to be accessed by other
> computers acting as clients.
> Each client that accesses the Developer Edition MUST have a Developer
> Edition license. (And of course, they must properly qualify for the
> Developer Edition license.)
> No Cost for one or more Servers, Developer Edition license for each client
> (user).
> AS long as ALL the usage qualifies for the Developer Edition license.
> Licensing -Developer Edition
> My understanding of the Developers Edition license is that you are covered
> for a Development server, an Integration/Staging server, even a QA/Test
> server, local servers on the developers computer, etc. -as long as no one
> except developers access those SQL Servers, and as long as each developer
> and/or Tester has a Developer Edition License.
> For a more definitive answer, check with the VL folks at: (800) 426-9400.
> From: http://www.microsoft.com/sql/editions/developer/default.mspx
> Each license of SQL Server 2005 Developer Edition entitles one developer
> to
> use the software on as many systems as necessary and additional developers
> can use the software by purchasing additional licenses.
> From:
> http://download.microsoft.com/download/e/c/a/ecafe5d1-b514-48ab-93eb-61377df9c5c2/SQLServer2005Licensingv1.1.doc
> DEVELOPER EDITION
> SQL Server Developer Edition is a separate product and is used for
> development and testing purposes only. It is licensed per developer or
> tester (person).
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "Prad" <pradeepk@.healthasyst.com> wrote in message
> news:OA6SOtY%23GHA.4888@.TK2MSFTNGP04.phx.gbl...
>> Arnie,
>> Thanks for replying soon.
>> I know that we can install Dev Edn on Desktops as you said.
>> My doubt is whether I can install it on only one server and the
>> clients(desktop mc/) access it. So that I need to update (run build) only
>> on the Server rather than updating every m/c.
>> If not possible, I will have to go for Standard Edn right? Hope you
>> understud my requirement.
>> Thanks,
>> Prad
>> "Arnie Rowland" <arnie@.1568.com> wrote in message
>> news:eywEjVY%23GHA.3348@.TK2MSFTNGP03.phx.gbl...
>> The license for Developer Edition allows you to install the client tools
>> on any development computer you desire, and to have as many SQL Servers
>> installed as you might need, for example, a dev server, a test server, a
>> QA server, etc.
>> However, each person (developer or tester -or whoever) accessing the
>> servers covered with the Developer Edition license MUST have a proper
>> license. (I think that is currently about $50 (US) each.)
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>> You can't help someone get up a hill without getting a little closer to
>> the top yourself.
>> - H. Norman Schwarzkopf
>>
>> "Prad" <pradeepk@.healthasyst.com> wrote in message
>> news:%239TXiSY%23GHA.4320@.TK2MSFTNGP02.phx.gbl...
>> Hi All,
>> I have a question regarding the usage of SQL Server 2005 Developer
>> Edition.
>> Can I use it in a client - server architecture say I install Developer
>> edition on a server and install client tools(Management studio /
>> profiler) on desktops and acess as we use Enterprise Edition? The
>> purpose is only Development (no production work). I am asking this
>> because ours is a small Organization with major work is done on SQL
>> Server 2000. Only 1 team is gonna use 2005.
>> Thanks,
>> Prad
>>
>>
>

Determining the OS Version that SQL is running on

I am writing a client application that offers an UI that allows an administrator to remotely add/delete/update user accounts accross many different SQL Servers running on XP and up.

When the operating system is W2K3 or higher I want to take advantage of the "check_expiration, check_policy, must_change' arguments to create login and exclude those features when the host OS does not support them.

Is there an easy way to determine if those arguments are supported?

Thanks

Mark

The OS version information is returned with @.@.VERSION. You will have to parse it a bit to find the Version, Edition, and Build -but it's all there.|||

or you can try this .. in sql server 2005 you have some limitation with XP_Cmdshell ... it may not be enabled by default...

EXEC master..xp_cmdshell 'netsh diag SHOW os /p'

for more details refer this link : http://www.sqlmag.com/Article/ArticleID/46062/sql_server_46062.html

Madhu

|||

Also exec xp_msver will return the OS version (I think it is line 15 in the result set)

hth,

-Steven Gott

S/DET

SQL Server

|||

exec xp_msver is exactly what I am looking for

Thanks!