Installing SQL Server 2005 Express Ed

Hi All,

I'm new to programming and I've got to develop a db for a uni project. However after downloading SQL Server 2005 express ed, I found that I could not find the command prompt to start writing scripts (black and white DOS screem). I only have the configuration tool option in my menu (within that server configuration manager, error & usage reporting and server surface area config).

How do I get started with creating my database, please help....................

I'm I not looking in the right place for the console (command prompt to run scripts) or have I not downloaded the right stuff.

I need help urgently!!!

Thanks, in advance

First thing, if you haven't already done so, download and install the Documentation and Samples for SQL Server 2005 Express Edition:

http://www.microsoft.com/downloads/details.aspx?familyid=9697AAAA-AD4B-416E-87A4-A8B154F92787&displaylang=en

There are a few ways to get started creating databases, run scripts, etc:

1. Install SQL Server Management Studio Express:

http://www.microsoft.com/downloads/details.aspx?familyid=82afbd59-57a4-455e-a2d6-1d4c98d40f6e&displaylang=en

2. Install a Visual Studio Express version

3. Open up a command shell and run sqlcmd -S <server\instance>

jeff.

|||

I downloaded SQL Server 2005 developers edition and in first go I could only install Server. The setup did not install client tools, BOL etc. I had to manually goto CD2 and setup.exe to install client tools and BOL.

|||

Thanks for the reply

I have installed the documentation and samples and the management studio, but when trying to work through the samples, I get this error message, for some reason I can't include the Adventure works db. What can I'm I not doing

1> SELECT name from sys.databases
2> Go
name

--

master

tempdb

model

msdb

1> CREATE DATABASE [AdventureWorks] ON
2> (AdventureWorks = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
< AdventureWorks>.mdf' ),
3> (AdventureWorks = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
< AdventureWorks>.ldf' )
4> FOR ATTACH ;
5> GO
Msg 153, Level 15, State 1, Server YOUR-V7OY5L24PG\SQLEXPRESS, Line 2
Invalid usage of the option AdventureWorks in the CREATE/ALTER DATABASE statemen
t.
1> USE [master]
2> GO
Changed database context to 'master'.
1> CREATE DATABASE [AdventureWorks] ON
2> (AdventureWorks = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
< AdventureWorks>.mdf' ),
3> (AdventureWorks = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
< AdventureWorks>.ldf' )
4> FOR ATTACH ;
5> GO
Msg 153, Level 15, State 1, Server YOUR-V7OY5L24PG\SQLEXPRESS, Line 2
Invalid usage of the option AdventureWorks in the CREATE/ALTER DATABASE statemen
t.
1> select name from sys.databases
2> go
name

--

master

tempdb

model

msdb

(4 rows affected)
1>

integrated development environment for Reporting Services

Is there a development environment for Reporting Services (2005) that is integrated with source control?

You can use Visual Studio to develop reports and place them under source control. But as far as I can tell, you cannot implement security, scheduling, etc. through Visual Studio. For these you can use a second environment, e.g. SQL Server Management Studio - but is this environment integrated with TFS?

In other words, is there a single development environment, integrated with TFS, where you can develop all aspects of Reporting Services reports?

I wouldn't get all excited about using SQL Server Management Studio for that second set of tasks, since they have pretty much indicated that they would prefer to concentrate on making Report Manager and Sharepoint the tools for this purpose in Katmai. I think the Management Studio snap-in approach didn't give them the flexibility they wanted, it's kind of rigid.

Please read below, from Brian Welcker's Weblog (http://blogs.msdn.com/bwelcker/ ) --

Meanwhile, remember that all the details you are actually configuring through either approach are actually in a database... So you do have ways of versioning them by taking snapshots of data.

I don't mean to make light of your concerns, and source control isn't directly integrated with the report management data that's in the database. As far as I know, it's aimed at scripting work (you can read this http://msdn2.microsoft.com/en-us/library/ms173550.aspx for information) .

But the data itself can be backed up on a regular, versioned basis and you can probably check the whole .BAK file into your source control repository if you want to (I don't know what you'd gain, but ReportServer DB's are metadata, they aren't going to be huge). If you created scripts for this purpose, you would of course have the integrated ability to version the scripts.

HTH -- see below for the Katmai information I was referring to...

>L<

(snip) - (http://blogs.msdn.com/bwelcker/ )

Watusi (SSRS Management Tools Changes for Katmai)

For Katmai we are considering the removal of namespace management (folders,
reports, data sources, models) from the Reporting Services Add-in for SQL
Server Management Studio (SSMS). In other words, we are considering removing
the 'Home' folder under the Reporting Server node in SSMS.

Why the change?

Customer feedback and usage data indicates that Report Manager and/or
SharePoint are the tools of choice for managing the Report Server namespace,
rather than the SSMS add-in. The design constraints of SSMS mean that any
new namespace functionality is significantly expensive to implement,
specifically adding support for the namespace in SharePoint integrated mode.
For Katmai we want to invest in SharePoint and Report Manager for namespace
management and focus on SSMS as a server-level management tool.

This means that the namespace management functions that are not available in
Report Manager (Model ClickThrough and Model Item Security) will be added to
Report Manager (they are already in SharePoint). Job Management, configuring
System properties, and administering Roles will be moved to SSMS. In
addition, SSMS will be updated to work in SharePoint mode.

If you have feedback about these changes, please feel free to comment.