Attach database fails

Folks, i had a database with data and log file on seperate disks. After reboot, i've lost the log file; now i am trying to attache the data file using EM and QA, i get the following error; plz guide:

sp_attach_single_file_db 'production', 'd:\production_data.mdf'

Server: Msg 1813, Level 16, State 2, Line 1
Could not open new database 'production'. CREATE DATABASE is aborted.
Device activation error. The physical file name 'D:\production_log.LDF' may be incorrect.

Howdy!try this...creat an empty database with that name...then detach it, and then try you attach|||Hi Brett, same error. If i give the logfile for newly created database(as u suggested) i get the error can not associate files from different databases.

Howdy!

Atlernative to SQL Server Management Studio (i.e. garbage) . Any suggestions?

Folks I have recently had the misfortune of moving to SQL Server Managment Studio as per our upgrade to SQL 2005. There is no doubt that SQL Server Management is a major disappoinment compared to Enterprise manager.

The UI is the biggest disaster I have ever seen. Getting rid of the SQL Query analyzer tool was aTERRIBLE idea. The UI is buggy and unfriendly. It is a major POS. I hope someone in the SQL Dev team is listening / reading this post (hellooooo anybody homeee.....)

Now that I have vented my frustration ...

I wanted to know any atlernatives to the SQL Server Management Studio. There are plenty of 3rd Party tools out there I wanted to find out from this forum which popular 3rd Party tools are most developers using

Thanks for bearing with me.

If all you're after is query analyzer type functionality the free SQL Scripter fromhttp://www.sqlscripter.com/ is worth a look.

|||

There's a bunch of them. Some of them free, some paid. Do a google search and you will find them - SQL Edit, Toad etc.

|||

A colleague found this reference on line yesterday. None of us have tried it out, but it looks reasonable.

http://www.albahari.com/queryexpress.html

|||

That's quite odd actually, I use it every day, and have yet to really stumble across a major issue with it. It's nice having one single app to be able to do all the functionality of the old enterprise manager (Yuck!), query analyzer, and (insert some database project tool that wasn't shipped with 2000). It is however pretty memory hungry, so I feel sorry for those trying to develop on really low end machines.

Really, the only complaint I have with it, is that I wish it's "script to..." functionality for insert/update/delete would default to placing parameters in the placeholders, or even better generate a VB.NET/C# SqlCommand for it (including creating the parameters, with datatypes). Obviously a minor complaint considering that it isn't part of the VB.NET/C# programming tools.

Or perhaps you've overlooked that you can right click any database, choose "New query", and it opens a new tab that acts very similiar to the old query analyzer?

|||

Motley:

That's quite odd actually, I use it every day, and have yet to really stumble across a major issue with it. It's nice having one single app to be able to do all the functionality of the old enterprise manager (Yuck!), query analyzer, and (insert some database project tool that wasn't shipped with 2000). It is however pretty memory hungry, so I feel sorry for those trying to develop on really low end machines.

Really, the only complaint I have with it, is that I wish it's "script to..." functionality for insert/update/delete would default to placing parameters in the placeholders, or even better generate a VB.NET/C# SqlCommand for it (including creating the parameters, with datatypes). Obviously a minor complaint considering that it isn't part of the VB.NET/C# programming tools.

Or perhaps you've overlooked that you can right click any database, choose "New query", and it opens a new tab that acts very similiar to the old query analyzer?

Well after using enterprise manager for a very long time I liked the fact that Query Analyzer open by itself. I realize now that it simply is intergated into the application via tabbed windows. Some how I just do not like that structure of UI design. But that this the least of my issues. In addition to the issue you mentioned there are several other issues.

When I try to open 2 or more db connection in my object explorer items not appear in my summary window. For example if i click on stored procs under programmability it shows me there are x number of items on the top right by the main screen is blank.

Frequently I get invalid errors when trying to browse items in the object explorer (error says invalid index)

When I ask it to remember my password for object explorer or for a new query it does not remember the password the next time

Additionally the UI is poorly designed and does not flow very well from a usability standpoint. (I wish the SQL team would pay more attention to this and not take UI so lightly. UI it is an after thought for developers BUT it is the first impression you make on the user, and that IMO is crucial)

I thought that I was the only person on my team not liking SQL Mgmt studio but 4/5 develpers including our DBA are not at all happy with the product...

|||

Well it seems to me that you are using portions of the studio, that I don't think I've ever used. I don't think I've had the Object Explorer Details window open for more than 2 seconds ever.

As for the UI design, it's probably a matter of taste. The paned view (Objects on left, middle as a work area, right is properties, etc) is used by a number of differing products (Visual Studio, Dreamweaver, Photoshop, etc etc). I'd hardly call it a poorly designed UI, but it's a matter of opinion and what you are trying to accomplish with the tool.

|||

Motley:

Well it seems to me that you are using portions of the studio, that I don't think I've ever used. I don't think I've had the Object Explorer Details window open for more than 2 seconds ever.

As for the UI design, it's probably a matter of taste. The paned view (Objects on left, middle as a work area, right is properties, etc) is used by a number of differing products (Visual Studio, Dreamweaver, Photoshop, etc etc). I'd hardly call it a poorly designed UI, but it's a matter of opinion and what you are trying to accomplish with the tool.

Most of my problems are with SQL Mgmt Studio UI whose is very different from the Visual Studio's UI (I find VS2005 to be quite good actually). I did intially think it was a matter of personal taste but what can I can when 4/5 folks on my team have the same complains.

Believe you me I did not give up on this after a day of working with it. I have been using it for the last 2 months.

Assigning Colors to bar charts

Hi there folks,

Would really appreciate it if i could get some help on this matter,

I have a bar chart that displays 3 bars. 3 separate colors have been assigned to each bar depending on the group it represents.

The problem is each time there is different data being pumped into the graph the assigned color of each bar keeps getting switched. Is there anyway that we could permanently assign a color to a bar ??

Thanking you in advance for your help.Hi,

When you say the colours have been assigned to a specific bar do you mean through the Chart Colour Format Expert? If you do then I would suggest you play around with which field or value you are using within the parameters.

If you dont then go to: Right-click chart> Chart Expert> Untick Automatically set chart options> Options Tab> Chart Colour Format Button.

In here (it is very similar to the Select Expert) you can assign a specific colour to a given parameter (i.e. if {SO_Header.SO_No} in 10000 to 20000 then the bar will appear red and so on)

If you have tried this and it still goes screwy when the values change then I would suggest building in a tollerance. So instead of saying if {woteva} = 10 then woteva, build in a comfort zone by using the <in to> operators as above.

Hope this helps. Please post results for other users and for any more help.

Take it easy

RobV