Development tool for first time developer?

I am about to start developing a web app using MS SQL Server and was wondering whether there is any tool that I can use to test queries towards a remote server?

Something like a command line or an easy way I can write queries and run them straight away through the server and check results? It is my first time developing in SQL so I need something that allows me to play around with queries in the server and check results to quickly get a hang os MS SQL Server syntax, stored procedures and such.

Best Regards

Alethenorio

From the nature of your question, I assume that you are using SQL Server Express.

Yes, you can download the SQL Server Management Studio Express client tools for working with SQL Server Express.

SSMSE and other resources are available from these links:

SQL Server 2005 Express Edition (Advanced/SSMS/BI Toolkit)
http://tinyurl.com/yelwr9 (SSMSE)

SQL Server 2005 SSMS Express Tutorial
http://tinyurl.com/nqsca

SQL Server 2005 Express Books Online Express Edition
http://www.microsoft.com/downloads/details.aspx?FamilyId=BE6A2C5D-00DF-4220-B133-29C1E0B6585F

SQL Server 2005 Express Video Learning
http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx#1

|||

Thanks Arnie.

To be honest I am doing a project for a company and I have not yet got access to the web hotel but if express is the lower version of microsoft's SQl server I believe it is not the version they run here. They probably run the full capable version (Whatever that is).

Would you suggest the same tool for such or is there another tool better fit to handle higher versions of SQl server?

Regards

Alex

|||

You may wish to consider getting SQL Server Express for your own computer, and the client tools, for your learning process.

The version of SQL Server Management Studio (SSMSE) that works with SQL Express is very similar to the version provided with the 'paid' Editions.

Good luck as you get up to speed. I think you will enjoy learning about SQL Server.

Developing app that will use SQL Server Express on back end...

Hi...

I have the full version of SQL Server installed on my machine and am developing an app using BI DTS packages, VB.Net, SQL SPs, etc.. I will need to deploy this app w/SQL Server Express (SSE).

-Do I have to install SSE on my development machine for the purpose of creating the install package of my application? I am afraid that if I do install SSE on my machine, it may mess up my installation of the full version of SQL Server... will it?

-Can you point me to a link with information about how to do the development with the full version of SS, and create the installation package using the SSE?

Thanks for your help.

Steph
You cannot deployment SQL Server 2005 Integration Services packages in SQL Server Express because the runtime now comes with the server license. In SQL Server 2000 the DTS package comes with the runtime that changed in 2005. Hope this helps.|||Thanks for the response.

The way I posed my question was misleading. I'm sorry about that. I shouldn't even have mentioned the DTS packages.

The big picture of the app is this:

- Data resides in a datamart at a central office. The central office will be running the full SQL Server 2005 version (this is where the DTS packages reside and run).

- Satellite (very small) offices need to download updated information relating to them from the central office. I'm thinking of having these satellite offices run SQL Express.

I'm developing the code to update the satellite office data from the central office data. On my development system, I am running the full version of SQL Server 2005. Should I also install SQL Express on my development system ? Will it mess up my full SQL Server 2005 installation?

Thanks,

Steph
|||It is tricky but here is how you could do it legally create Asp.net application run it from your main office SQL Server create a job to execute the many versions of the package make your small offices destination. It will take more work but the alternative solution may cost you more hardware SQL Server Express can be a subscriber in replication so you can push the data with replication. You could always talk to your local Microsoft SQL Server contact person, in some areas there is regional contact person. Hope this helps

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 Express & Database issues

I Am developing a simple app with a database. All has been going fine until now, the following is occuring:

In Visual Web Developer 2005 Express if I connect to the database and view some table data I can do that fine but then as soon as I try to view a page in the browser I get the error:
Login failed for user 'MachineName\ASPNET'
If in web developer I go to the database explorer and close the connection to the database then refresh the page it all works fine.

Anyone have anyideas on how to correct this?

Thanks
Scott

This is a frequently asked issue The login 'MachineName\ASPNET' is used by IIS when your website trying to connect to SQL with Window Authentication (Integrated Security=SSPI). So in this case just add the account to SQL Server Logins with proper database permissions, which can be easily done in Management Studio: go to Security->Logins->right clich and choose add login->add the Windows account 'MachineName\ASPNET' and give it permissions (or simply add it to sysadmin server role). You can download Management Studio Express from here:

http://msdn.microsoft.com/vstudio/express/sql/download/

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 / Desktop Edition

I'm developing a windows (c#) application that currently uses SQL 2000. I've
developed the app using Developer Edition on my laptop.
The requirements of the app, are such that when the user is not at the
office, they can still use the application on thier laptop, but use a local
copy of the database. So I thought..ok just provide Desktop Edition with the
application.
Can I install Desktop Edition on my development machine with out messing up
the Developer Edition installation? What I'm concerned with is hosing my
currently installed DE.
As part of the application, I want the user to be able to use a Desktop
version of the database so when not at the office, the user can still use th
e
application.Jeff,
The short answer is yes you can do this. Is Developer Edition currently
installed as the default instance? If so, MSDE would have to be a named
instance. Honestly, I've never had a need to do this, so I'm not 100% sure
about exact installation needs. But I know 100% it is supported. You'll find
some good info if you google
install sql MSDE named instance
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Jeff" <nowhere@.nowhere.com> wrote in message
news:507FB9A4-80E6-4099-AEBD-E248434965B0@.microsoft.com...
> I'm developing a windows (c#) application that currently uses SQL 2000.
I've
> developed the app using Developer Edition on my laptop.
> The requirements of the app, are such that when the user is not at the
> office, they can still use the application on thier laptop, but use a
local
> copy of the database. So I thought..ok just provide Desktop Edition with
the
> application.
> Can I install Desktop Edition on my development machine with out messing
up
> the Developer Edition installation? What I'm concerned with is hosing my
> currently installed DE.
>
>
>
>
>
> As part of the application, I want the user to be able to use a Desktop
> version of the database so when not at the office, the user can still use
the
> application.

Developer Edition / Desktop Edition

I'm developing a windows (c#) application that currently uses SQL 2000. I've
developed the app using Developer Edition on my laptop.
The requirements of the app, are such that when the user is not at the
office, they can still use the application on thier laptop, but use a local
copy of the database. So I thought..ok just provide Desktop Edition with the
application.
Can I install Desktop Edition on my development machine with out messing up
the Developer Edition installation? What I'm concerned with is hosing my
currently installed DE.
As part of the application, I want the user to be able to use a Desktop
version of the database so when not at the office, the user can still use the
application.
Jeff,
The short answer is yes you can do this. Is Developer Edition currently
installed as the default instance? If so, MSDE would have to be a named
instance. Honestly, I've never had a need to do this, so I'm not 100% sure
about exact installation needs. But I know 100% it is supported. You'll find
some good info if you google
install sql MSDE named instance
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Jeff" <nowhere@.nowhere.com> wrote in message
news:507FB9A4-80E6-4099-AEBD-E248434965B0@.microsoft.com...
> I'm developing a windows (c#) application that currently uses SQL 2000.
I've
> developed the app using Developer Edition on my laptop.
> The requirements of the app, are such that when the user is not at the
> office, they can still use the application on thier laptop, but use a
local
> copy of the database. So I thought..ok just provide Desktop Edition with
the
> application.
> Can I install Desktop Edition on my development machine with out messing
up
> the Developer Edition installation? What I'm concerned with is hosing my
> currently installed DE.
>
>
>
>
>
> As part of the application, I want the user to be able to use a Desktop
> version of the database so when not at the office, the user can still use
the
> application.

Developer Edition / Desktop Edition

I'm developing a windows (c#) application that currently uses SQL 2000. I've
developed the app using Developer Edition on my laptop.
The requirements of the app, are such that when the user is not at the
office, they can still use the application on thier laptop, but use a local
copy of the database. So I thought..ok just provide Desktop Edition with the
application.
Can I install Desktop Edition on my development machine with out messing up
the Developer Edition installation? What I'm concerned with is hosing my
currently installed DE.
As part of the application, I want the user to be able to use a Desktop
version of the database so when not at the office, the user can still use the
application.Jeff,
The short answer is yes you can do this. Is Developer Edition currently
installed as the default instance? If so, MSDE would have to be a named
instance. Honestly, I've never had a need to do this, so I'm not 100% sure
about exact installation needs. But I know 100% it is supported. You'll find
some good info if you google
install sql MSDE named instance
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Jeff" <nowhere@.nowhere.com> wrote in message
news:507FB9A4-80E6-4099-AEBD-E248434965B0@.microsoft.com...
> I'm developing a windows (c#) application that currently uses SQL 2000.
I've
> developed the app using Developer Edition on my laptop.
> The requirements of the app, are such that when the user is not at the
> office, they can still use the application on thier laptop, but use a
local
> copy of the database. So I thought..ok just provide Desktop Edition with
the
> application.
> Can I install Desktop Edition on my development machine with out messing
up
> the Developer Edition installation? What I'm concerned with is hosing my
> currently installed DE.
>
>
>
>
>
> As part of the application, I want the user to be able to use a Desktop
> version of the database so when not at the office, the user can still use
the
> application.

determining who is logged into database server

Hi,
There used to be a command in mssql 6.5 that would tell
return the login names of users who had the database open,
ie, they were still in the app that connects to the db. I
think the command was something like @.@.who. Is there and
equivalent command in SQL 7 and 2k?
Also, is it possible to run sql 6.5 on a win2k server? It
keeps telling me the app is not loaded when I try to run
the service pack.
Thanks,
MikeI think you are looking for the system stored procedures
sp_who and sp_who2.
-Sue
On Mon, 3 Nov 2003 18:29:51 -0800, "Mike Stefani"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>There used to be a command in mssql 6.5 that would tell
>return the login names of users who had the database open,
>ie, they were still in the app that connects to the db. I
>think the command was something like @.@.who. Is there and
>equivalent command in SQL 7 and 2k?
>Also, is it possible to run sql 6.5 on a win2k server? It
>keeps telling me the app is not loaded when I try to run
>the service pack.
>Thanks,
>Mike|||Hi,
I think you are referring to SP_WHO system stored procedure. You can use the
same procedure in SQL 7.0 and SQL 2k from Query analyzer to identify
all the current processes (Users) connected to SQL server.
You can defenetely run SQL 6.5 is Win2k server , but as you said there is
lots of problems. Microsoft recommends not to run SQL 6.5 in Win2k.
Thanks
Hari
MCDBA
"Mike Stefani" <anonymous@.discussions.microsoft.com> wrote in message
news:0b1a01c3a27b$862eff90$a101280a@.phx.gbl...
> Hi,
> There used to be a command in mssql 6.5 that would tell
> return the login names of users who had the database open,
> ie, they were still in the app that connects to the db. I
> think the command was something like @.@.who. Is there and
> equivalent command in SQL 7 and 2k?
> Also, is it possible to run sql 6.5 on a win2k server? It
> keeps telling me the app is not loaded when I try to run
> the service pack.
> Thanks,
> Mike|||its sp_who
--
Shaju Thomas
"Mike Stefani" <anonymous@.discussions.microsoft.com> wrote in message
news:0b1a01c3a27b$862eff90$a101280a@.phx.gbl...
> Hi,
> There used to be a command in mssql 6.5 that would tell
> return the login names of users who had the database open,
> ie, they were still in the app that connects to the db. I
> think the command was something like @.@.who. Is there and
> equivalent command in SQL 7 and 2k?
> Also, is it possible to run sql 6.5 on a win2k server? It
> keeps telling me the app is not loaded when I try to run
> the service pack.
> Thanks,
> Mike