(Cancel this) Can’t paste into XML field in Management Studio.

Hi Folks,

It looks like Management Studio prevents pasting XML directly into a field of the type xml. Sometimes, it might be best to stay with varchar(max).

Original post below: >>

I want to paste some XML into an SQL Server 2005 xml type field, but the null is grayed out and paste simply does not work. What is going on?

Thanks,

Rob

Rob:

I see the same behavior. It appears to me that the COPY function is not active for the XML field and that you cannot directly modify it. You can copy from the XML field, but you cannot paste into it. I suggest that you use an XML query to update your field?

"visual studio is busy"

I keep getting this balloon message along with 'please contact microsoft if you continue to get this message' when using SSIS

Here's the news: I continually get the message so here I am 'contact MS'

There is no link in the balloon indicating quite how I should contact MS.

Any one else have this problem?Id be more than willing to help, but would need some more info. does this happen when you first open up the package? Sometimes this is caused by a long validation. If you can better explain the package this happens with/ when it happens maybe I can help|||

The package under development is very simple:

open an xls and put the data in a table

there are about 4 connection managers

that's it, the whole thing is only about 200k

|||Make sure that there isn't another window open that got sent to the background.

"visual studio is busy"

I keep getting this balloon message along with 'please contact microsoft if you continue to get this message' when using SSIS

Here's the news: I continually get the message so here I am 'contact MS'

There is no link in the balloon indicating quite how I should contact MS.

Any one else have this problem?Id be more than willing to help, but would need some more info. does this happen when you first open up the package? Sometimes this is caused by a long validation. If you can better explain the package this happens with/ when it happens maybe I can help|||

The package under development is very simple:

open an xls and put the data in a table

there are about 4 connection managers

that's it, the whole thing is only about 200k

|||Make sure that there isn't another window open that got sent to the background.

"Visual Studio 2005 Command Prompt" missing from SQL Server 2005 Express Toolkit insta

The program shortcut "Visual Studio 2005 Command Prompt" seems to be mising from the "Visual Studio 2005 Command Prompt" Start menu added by the current Microsoft SQL Server 2005 Express Edition Toolkit. Where is it? How to workaround?

I am trying to do Download details SQL Server 2005 Samples and Sample Databases (April 2006) -> GettingStartedWithSQLSamples.htm which says "a. Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt." but I can find no such command prompt within "Visual Studio Tools", only "Visual Studio 2005 Remote Debugger{, Configuration Wizard}".

What's wrong? How to fix or workaround? I'd install .NET SDK 2.0 to get it's Command Prompt but that's about 570MB merely for a command prompt!

Thanks for your help, -Mike Parker

I believe that the toolkit does not come with the command prompt and the instructions for the samples were written before Advanced was shipped.

What are you trying to do with the samples? If you don't have a copy of VS installed its going to be pretty hard to do anything with them. If you just want accesst to the SQL Server samples I don't think you need a command prompt.

"SQL Server Management Studio Express" install location

I just installed the "SQL Server Management Studio Express" but it didn't tell me where it was installed. How do I get the application started ?A short-cut should have been add to ALL Programs | Microsoft SQL Server 2005 | SQL Server Management Studio Express CTP.

Peter|||found it here

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe"

"Server type" is disabled in SQL Server Management Studio

Hi,

I'm trying to connect to a remote server using SQL Server management studio express.

But the "server type" field is disabled. I'm not able to select the server type. It is set to "Database Engine". Because of this (I Guess) the connection to the remote SQL server 2005 is failing giving the following error:

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)"

Please let me know how to solve this issue.

Thanks & Regards,
Bijesh

Hi there,

Is the remote server running either of SQL Server 2005 Express Edition or SQL Server 2005 Developer Edition?

The error mesasge you posted seems to indicate that the remote server won't accept a connection. I don't think this has anything to do with the value in the "Server Type" field.

If you're trying to connect to a remote instance of SQL Server 2005 Express or Developer Edition then remote connections are disabled by default & this would explain why you are unable to connect. If you perform the steps outlined in the below link on your remote server, you should be able to connect to the remote server:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Also check that the name you are providing for the remote server is correct. If the remote server is running a default instance then the name of the SQL Server is the name of the computer. If the remote server is running a named instance then the name of the SQL Server is <Computer Name>\<Instance Name>

Hope that helps a bit, but sorry if it doesn't
|||SQL Server Express can only connect to the relational engine - that's why server type is grayed out.|||

This means the client couldn't make a connection to the server. Most often, the cause is because the server is not configured to accept connections from other machines. Second most often, there is a firewall getting in the way.

Make sure the remote server is configured to accept named pipes connections. You can check this using the Surface Area Configuration tool.

If named pipes don't work for you, switch to using TCP/IP connections, make sure the server is configured to accept TCP/IP connections, and make sure the IP port used by SQL Server is open in your firewall (by default, this is port 1433).

Hope this helps,
Steve

"Select top (n) from <table>" missing from Management Studio

In sql 2000 one could right-click a table (under Enterprise Manager) and have it return the "top n" rows in the table. That feature seems to be missing from Management Studio. Am I correct or is it just hiding somewhere?

TIA,

Barkingdog

No, its definitely not there, you will have to tweak the SQL Statement by clicking the appropiate item in the iconbar.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

>>you will have to tweak the SQL Statement by clicking the appropiate item in the iconbar.
>>

What "item" are you referring to? The only way I can see to do this is open a new Query Editor pane and type the sql directly.

TIA,

Barkingdog

|||If you open a table you will have an icon with "SQL" written on it, you can change to the SQL Statement whcih was executed to have the data displayed, which is normally SELECT * From SomeTable and can change it the way you want to query the data.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

"Remember Password" feature behaves like child with Attention Deficit Disorder

In Sql Server Management Studio, when you connect to a server using SQL Server authentication, there is a checkbox "Remember Password". This is really really annoying and causing me great frustration. We have passwords which are very long and have numeric and alpha and symbol characters. They are easy to type wrong. As a developer, my workstation has been secured by other means. I wish to make use of "Remember Password" so that I can more quickly DO MY WORK. For months now, whenever our network connections were severed but we were connected already, the next time we tried to connect, the freakin password would be cleared out. This is like Alzheimer's Disease. So, I've learned not to attempt to connect again or execute queries or navigate around in the property tree. I just wait until transient network problem goes away. Then I make my next connection, of course I have to re-type this incredibly long password again, RE-check the "Remember Password" box, get connected, then quit Sql Server Management Studio. This seems to be the only way for it to truely REMEMBER it. Then I restart Sql Server Management Studio, reconnect, and voila, the password has already been filled in for me. NOW, however things are different. There are NO network transient problems. Instead what we have going on here is more like a child with Attention Deficit Disorder. SQL Server Management Studio is FORCING me to retype the password upon every NEW execution. I swear, sometimes when I encounter this problem it totally removes my ability to perform my work. Instead, I picture grabbing the developers who were responsible for making this tool by the neck and like a bobble-head doll, shake them until their head's roll off. That's how frustrating this problem has become for me. Of course, there's going to be some people who read this and chuckle.. well.. it is kind of funny how I've described my frustrations, but really I'd like to SOLVE the problem somehow without having to read ten tons of documentation somewhere ridden with superfluous jargon written by someone who'd rather spread words in a flower garden than get to the freakin' point. Does anyone know how to solve this problem? hmmm... perhaps I should change the password to an empty string? Yeah, that would be appropriate for this problem where Sql Server Management Studio has a zero memory retention skill (ADD), but.. oh... lest we forget, that would cause a security risk now wouldn't it?

Could you please file a defect report for this on http://connect.microsoft.com/sqlserver? Issues reported on the Connect site are automatically ported into our internal issue tracking system so we don't lose any of the information you provide there.

We run in a Windows Domain here at work, so for our day-to-day work we almost universally use Windows Authentication logins and we never have to explicitly provide a password to SQL Server. If you are running in a Windows Domain, IMHO that's the easiest workaround for your problem. This is also the safest route with respect to security - any saved password is a potential security threat. Note that even in workgroup environments you can use Windows Authentication with local Windows logins if Management Studio is running on the same machine as the server.

As another work-around to the problem, you can save off a copy of your local c:\Documents and Settings\{you}\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell\mru.dat file. When management studio overwrites your saved password with an empty string like you describe, you could close management studio and then copy your backup mru.dat file over the more recent one. This will reset the saved settings of the connection dialog and other "most recently used" items in the UI to their saved values.

Management Studio does encrypt saved passwords, but no encryption is unbreakable. Be sure to restrict access to your saved mru.dat file to help prevent unauthorized access to your server.

Hope this helps,

Steve

|||

For the sake of followup I will mark thread as sticky.

Joe

Have you reported in the connect site as per Steve's reference?

|||

I actually don't understand, even as long as the description is, because I don't see this behavior at all.

Let me put in some very simple and straightforward things, as you've asked for.

Open Registered Server, create a new registration, check the save password box, and save the registration. From that point forward, you can ALWAYS right click on a registered server and select Connect | New Query or Connect | Object Explorer. I have NEVER seen it lose one of these passwords for any reason and I've done this in over 100 different customer environments, spanning a couple hundred different workstations.

Now, to the other part. If you are launching a query window from the object browser, the server has to be highlighted for SSMS to have a valid context to launch the query window against. If you launch a query window by using the New Query button and you get a dialog box to login, then it could not find a context, which means that you didn't have the server or a node underneath the server highlighted when you hit the button.

As far as the Remember Password checkbox in the connect dialog goes, I've never used it and have no plans at all to ever use it. I save everything in the Resgistered Servers, so I can always get to what I need without using this piece of the Connect dialog.

So, you wanted a valid workaround for any situation whatsoever, here it is. Use the Regsitered Servers task pane. If you have a query window open when you lose the connection, launch a new query window from the Registered Servers task pane, and then copy/paste the contents of the query window into the new one you just launched. It isn't pretty, but it will work 100% of the time.

|||This guy is completely right.

Let me explain how I first got to this forum.

For the last two years of using SQL Server Management Studio I have constantly been asked for my password whenever I leave my home and connect my laptop at work, or go home and connect my laptop to my home network.

Today was the breaking point for me, and I decided to type this topic into google and "get lucky".

Voila, here I am, and I can attest to this behavior of SSMS. I believe we're both addressing the issue concerning the login prompt when SSMS loads--not the "Registered Servers" pane.

It just behave like a kid with ADD and this behavior is so annoying it makes me pull my hair out and want to use Enterprise Manager, which I thought I would never say, but its true. At least EM saved my passwords...

The context switching is also very annoying.

I could rant for days about the UI fricition in SSMS, such as how the tabbed document layout's file names are so narrow in width that file names become unreadable, the MDI environment forces me to play the "resize window game", and how the summary name column gets resized to default every time you view a new object in the object explorer, but I'll save those bits for another thread.

|||

Here here!

I've had this problem myself ever since I started using SSMS. It's really obnoxious, because I love pretty much every other feature (except for the pummeling that DTS has undergone, but that's more a beef with SQL than SSMS), but this one bug alone has me very close to switching back to Enterprise Manager.

Any way, if you have managed to come up with a solution to this, I'd love to hear it. For me there doesn't even seem to be any rhyme or reason. It will remember my password for two or three connections, maybe four if I'm particularly luck, then spontaneously forget it again. And what's really awful is I'm regularly connecting to six or so different SQL servers, each with long, very strong passwords, that I have to go look up every third or so time I connect to them. I've just been dealing with it until today, when I finally broke down and decided that this was a stupid enough bug that there simply must be an easy fix for it. And after five pages of Google search results, I've drawn the conclusion that a lot of people seem to have this problem, but nobody has a fix for it.

Attention MS: Please please please please please fix this bug and release a patch!

|||Well, you can't use Enterprise Manager. It does not work against SQL Server 2005 instances. Don't know on the connection dialog when you launch SSMS. The very first thing that I configure is to launch SSMS into a blank environment so that I can choose what I want to do from there instead of always launching a query window. As for a workaround, that's 3 posts up, use the Registered Servers task pane.|||

Or Microsoft could just fix SSMS...

"Remember Password" feature behaves like child with Attention Deficit Disorder

In Sql Server Management Studio, when you connect to a server using SQL Server authentication, there is a checkbox "Remember Password". This is really really annoying and causing me great frustration. We have passwords which are very long and have numeric and alpha and symbol characters. They are easy to type wrong. As a developer, my workstation has been secured by other means. I wish to make use of "Remember Password" so that I can more quickly DO MY WORK. For months now, whenever our network connections were severed but we were connected already, the next time we tried to connect, the freakin password would be cleared out. This is like Alzheimer's Disease. So, I've learned not to attempt to connect again or execute queries or navigate around in the property tree. I just wait until transient network problem goes away. Then I make my next connection, of course I have to re-type this incredibly long password again, RE-check the "Remember Password" box, get connected, then quit Sql Server Management Studio. This seems to be the only way for it to truely REMEMBER it. Then I restart Sql Server Management Studio, reconnect, and voila, the password has already been filled in for me. NOW, however things are different. There are NO network transient problems. Instead what we have going on here is more like a child with Attention Deficit Disorder. SQL Server Management Studio is FORCING me to retype the password upon every NEW execution. I swear, sometimes when I encounter this problem it totally removes my ability to perform my work. Instead, I picture grabbing the developers who were responsible for making this tool by the neck and like a bobble-head doll, shake them until their head's roll off. That's how frustrating this problem has become for me. Of course, there's going to be some people who read this and chuckle.. well.. it is kind of funny how I've described my frustrations, but really I'd like to SOLVE the problem somehow without having to read ten tons of documentation somewhere ridden with superfluous jargon written by someone who'd rather spread words in a flower garden than get to the freakin' point. Does anyone know how to solve this problem? hmmm... perhaps I should change the password to an empty string? Yeah, that would be appropriate for this problem where Sql Server Management Studio has a zero memory retention skill (ADD), but.. oh... lest we forget, that would cause a security risk now wouldn't it?

Could you please file a defect report for this on http://connect.microsoft.com/sqlserver? Issues reported on the Connect site are automatically ported into our internal issue tracking system so we don't lose any of the information you provide there.

We run in a Windows Domain here at work, so for our day-to-day work we almost universally use Windows Authentication logins and we never have to explicitly provide a password to SQL Server. If you are running in a Windows Domain, IMHO that's the easiest workaround for your problem. This is also the safest route with respect to security - any saved password is a potential security threat. Note that even in workgroup environments you can use Windows Authentication with local Windows logins if Management Studio is running on the same machine as the server.

As another work-around to the problem, you can save off a copy of your local c:\Documents and Settings\{you}\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell\mru.dat file. When management studio overwrites your saved password with an empty string like you describe, you could close management studio and then copy your backup mru.dat file over the more recent one. This will reset the saved settings of the connection dialog and other "most recently used" items in the UI to their saved values.

Management Studio does encrypt saved passwords, but no encryption is unbreakable. Be sure to restrict access to your saved mru.dat file to help prevent unauthorized access to your server.

Hope this helps,

Steve

|||

For the sake of followup I will mark thread as sticky.

Joe

Have you reported in the connect site as per Steve's reference?

|||

I actually don't understand, even as long as the description is, because I don't see this behavior at all.

Let me put in some very simple and straightforward things, as you've asked for.

Open Registered Server, create a new registration, check the save password box, and save the registration. From that point forward, you can ALWAYS right click on a registered server and select Connect | New Query or Connect | Object Explorer. I have NEVER seen it lose one of these passwords for any reason and I've done this in over 100 different customer environments, spanning a couple hundred different workstations.

Now, to the other part. If you are launching a query window from the object browser, the server has to be highlighted for SSMS to have a valid context to launch the query window against. If you launch a query window by using the New Query button and you get a dialog box to login, then it could not find a context, which means that you didn't have the server or a node underneath the server highlighted when you hit the button.

As far as the Remember Password checkbox in the connect dialog goes, I've never used it and have no plans at all to ever use it. I save everything in the Resgistered Servers, so I can always get to what I need without using this piece of the Connect dialog.

So, you wanted a valid workaround for any situation whatsoever, here it is. Use the Regsitered Servers task pane. If you have a query window open when you lose the connection, launch a new query window from the Registered Servers task pane, and then copy/paste the contents of the query window into the new one you just launched. It isn't pretty, but it will work 100% of the time.

|||This guy is completely right.

Let me explain how I first got to this forum.

For the last two years of using SQL Server Management Studio I have constantly been asked for my password whenever I leave my home and connect my laptop at work, or go home and connect my laptop to my home network.

Today was the breaking point for me, and I decided to type this topic into google and "get lucky".

Voila, here I am, and I can attest to this behavior of SSMS. I believe we're both addressing the issue concerning the login prompt when SSMS loads--not the "Registered Servers" pane.

It just behave like a kid with ADD and this behavior is so annoying it makes me pull my hair out and want to use Enterprise Manager, which I thought I would never say, but its true. At least EM saved my passwords...

The context switching is also very annoying.

I could rant for days about the UI fricition in SSMS, such as how the tabbed document layout's file names are so narrow in width that file names become unreadable, the MDI environment forces me to play the "resize window game", and how the summary name column gets resized to default every time you view a new object in the object explorer, but I'll save those bits for another thread.

|||

Here here!

I've had this problem myself ever since I started using SSMS. It's really obnoxious, because I love pretty much every other feature (except for the pummeling that DTS has undergone, but that's more a beef with SQL than SSMS), but this one bug alone has me very close to switching back to Enterprise Manager.

Any way, if you have managed to come up with a solution to this, I'd love to hear it. For me there doesn't even seem to be any rhyme or reason. It will remember my password for two or three connections, maybe four if I'm particularly luck, then spontaneously forget it again. And what's really awful is I'm regularly connecting to six or so different SQL servers, each with long, very strong passwords, that I have to go look up every third or so time I connect to them. I've just been dealing with it until today, when I finally broke down and decided that this was a stupid enough bug that there simply must be an easy fix for it. And after five pages of Google search results, I've drawn the conclusion that a lot of people seem to have this problem, but nobody has a fix for it.

Attention MS: Please please please please please fix this bug and release a patch!

|||Well, you can't use Enterprise Manager. It does not work against SQL Server 2005 instances. Don't know on the connection dialog when you launch SSMS. The very first thing that I configure is to launch SSMS into a blank environment so that I can choose what I want to do from there instead of always launching a query window. As for a workaround, that's 3 posts up, use the Registered Servers task pane.|||

Or Microsoft could just fix SSMS...

"Override Default" button in Properties->Parameters section

I wrote a report in Visual Studio with some parameters that I gave default values to in the report definition. I deployed it out to the report server and when I look at the report Properties, Parameters section to see the default values. Instead of seeing all of the default values, I see a bunch of "Override Default" buttons. When you click the buttons, you get a blank text box in which to enter a new value.

Someone before me created a report with default values and the parameters section of that report has text boxes with the default values in them.

Does anyone know how to have the default values show up rather than those "Override Default" buttons?

Thanks.

Somebody must know what I am talking about...|||

I have a hard time believing no one knows about this...

Is my problem not clear? Somebody please ask a question if you don't understand!

|||

I know what you are talking about, but I don't think there is a setting to have it show the values.

Jarret

|||

That makes it seem like random behavior then, which is not really an acceptable explanation.

I'm looking at one report that was written a little while back that will show you the default values in text boxes you can edit, and then there's this other report that I just wrote that will only show you the "Override Default" buttons. When you click them, then you get editable text boxes, but it won't show you what the original default value was.

Is there anyone else out there that can take a stab at it please? Thank you.

|||

Hmmmm...

I just created a simple report with a default parameter and it showed the correct default value instead of the 'Override Default' button. Maybe it has something to do with which version of RS you created the report under (RS2000, RS2005 RTM, SP1, SP2) versus which version you're trying to view it under.

Like you, I have seen this before.

Jarret

|||

I think that it is not "random behavior". As I know the behavior is:

1. If default value isn't query-based and not an expression - you will see original default value

2. If default value isn't query-based but an expression - you will see "Override Default" button instead of expression result

3. If default value is query-based - you will see text "Query Based"

|||

Alright, now we're talking. This is the kind of answer I was looking for, someone who knows the behavior!

So in the past I have had the default values be expressions. For this particular report, I just plugged in numbers. However, I put them in the following format: =2.0. Would that be considered an expression instead of just a value?

|||

miguelito928 wrote:

Alright, now we're talking. This is the kind of answer I was looking for, someone who knows the behavior!

So in the past I have had the default values be expressions. For this particular report, I just plugged in numbers. However, I put them in the following format: =2.0. Would that be considered an expression instead of just a value?

I'm pretty sure you just have to select a default value in the parameters option. I can check when I get to work if you don't confirm this to be true until then

Here's how I believe it works:

-> Add a new parameter called CategoryId, for example;

-> In the values list I'm guessing you'll retrieve them from a query that returns at least an Id and a Label;

-> In the option below the values list you have the option to add a default value, which can also be returned by a query.

Basicly what this 3 item list means is that let's imagin you have a query that returns these values:

1 - Meat

2 - Fish

3 - Fruit

It's a perfect query for your values list! Now, for the default value selection you would want it to be something like:

SELECT C.Id, C.Alias FROM Categories C WHERE C.Default = 1;

This query would return you the default category to use in your report parameter. Something like this:

1 - Meat

Best regards,

Ahkaru

|||

No, your post wasn't helpful at all. I'm not getting my default values from queries.

I am setting the default value of my parameter to "=2.0". This seems to be a non-queried expression, which would explain why I am getting an "Override Default" button instead of a text box with the value in it. The type of my parameters are floats by the way. I just noticed that the report written by someone else has strings and the default values are entered in without the equals sign in front.

So I decided to try and remove the equals signs and now it is showing that there are no default values. Is there no way to enter non-expression non-queried values from the Visual Studio report builder?

|||Ok, I get it to work if you leave all the default values blank and then fill them in through the Report Manager console after you deploy the report. The only way to deploy the report with default values is using expressions and putting equals signs in front, which causes "Override Default" buttons. Thank you to Andrey for his knowledge of the behavior.

"Override Default" button in Properties->Parameters section

I wrote a report in Visual Studio with some parameters that I gave default values to in the report definition. I deployed it out to the report server and when I look at the report Properties, Parameters section to see the default values. Instead of seeing all of the default values, I see a bunch of "Override Default" buttons. When you click the buttons, you get a blank text box in which to enter a new value.

Someone before me created a report with default values and the parameters section of that report has text boxes with the default values in them.

Does anyone know how to have the default values show up rather than those "Override Default" buttons?

Thanks.

Somebody must know what I am talking about...|||

I have a hard time believing no one knows about this...

Is my problem not clear? Somebody please ask a question if you don't understand!

|||

I know what you are talking about, but I don't think there is a setting to have it show the values.

Jarret

|||

That makes it seem like random behavior then, which is not really an acceptable explanation.

I'm looking at one report that was written a little while back that will show you the default values in text boxes you can edit, and then there's this other report that I just wrote that will only show you the "Override Default" buttons. When you click them, then you get editable text boxes, but it won't show you what the original default value was.

Is there anyone else out there that can take a stab at it please? Thank you.

|||

Hmmmm...

I just created a simple report with a default parameter and it showed the correct default value instead of the 'Override Default' button. Maybe it has something to do with which version of RS you created the report under (RS2000, RS2005 RTM, SP1, SP2) versus which version you're trying to view it under.

Like you, I have seen this before.

Jarret

|||

I think that it is not "random behavior". As I know the behavior is:

1. If default value isn't query-based and not an expression - you will see original default value

2. If default value isn't query-based but an expression - you will see "Override Default" button instead of expression result

3. If default value is query-based - you will see text "Query Based"

|||

Alright, now we're talking. This is the kind of answer I was looking for, someone who knows the behavior!

So in the past I have had the default values be expressions. For this particular report, I just plugged in numbers. However, I put them in the following format: =2.0. Would that be considered an expression instead of just a value?

|||

miguelito928 wrote:

Alright, now we're talking. This is the kind of answer I was looking for, someone who knows the behavior!

So in the past I have had the default values be expressions. For this particular report, I just plugged in numbers. However, I put them in the following format: =2.0. Would that be considered an expression instead of just a value?

I'm pretty sure you just have to select a default value in the parameters option. I can check when I get to work if you don't confirm this to be true until then

Here's how I believe it works:

-> Add a new parameter called CategoryId, for example;

-> In the values list I'm guessing you'll retrieve them from a query that returns at least an Id and a Label;

-> In the option below the values list you have the option to add a default value, which can also be returned by a query.

Basicly what this 3 item list means is that let's imagin you have a query that returns these values:

1 - Meat

2 - Fish

3 - Fruit

It's a perfect query for your values list! Now, for the default value selection you would want it to be something like:

SELECT C.Id, C.Alias FROM Categories C WHERE C.Default = 1;

This query would return you the default category to use in your report parameter. Something like this:

1 - Meat

Best regards,

Ahkaru

|||

No, your post wasn't helpful at all. I'm not getting my default values from queries.

I am setting the default value of my parameter to "=2.0". This seems to be a non-queried expression, which would explain why I am getting an "Override Default" button instead of a text box with the value in it. The type of my parameters are floats by the way. I just noticed that the report written by someone else has strings and the default values are entered in without the equals sign in front.

So I decided to try and remove the equals signs and now it is showing that there are no default values. Is there no way to enter non-expression non-queried values from the Visual Studio report builder?

|||Ok, I get it to work if you leave all the default values blank and then fill them in through the Report Manager console after you deploy the report. The only way to deploy the report with default values is using expressions and putting equals signs in front, which causes "Override Default" buttons. Thank you to Andrey for his knowledge of the behavior.

"Override Default" button in Properties->Parameters section

I wrote a report in Visual Studio with some parameters that I gave default values to in the report definition. I deployed it out to the report server and when I look at the report Properties, Parameters section to see the default values. Instead of seeing all of the default values, I see a bunch of "Override Default" buttons. When you click the buttons, you get a blank text box in which to enter a new value.

Someone before me created a report with default values and the parameters section of that report has text boxes with the default values in them.

Does anyone know how to have the default values show up rather than those "Override Default" buttons?

Thanks.

Somebody must know what I am talking about...|||

I have a hard time believing no one knows about this...

Is my problem not clear? Somebody please ask a question if you don't understand!

|||

I know what you are talking about, but I don't think there is a setting to have it show the values.

Jarret

|||

That makes it seem like random behavior then, which is not really an acceptable explanation.

I'm looking at one report that was written a little while back that will show you the default values in text boxes you can edit, and then there's this other report that I just wrote that will only show you the "Override Default" buttons. When you click them, then you get editable text boxes, but it won't show you what the original default value was.

Is there anyone else out there that can take a stab at it please? Thank you.

|||

Hmmmm...

I just created a simple report with a default parameter and it showed the correct default value instead of the 'Override Default' button. Maybe it has something to do with which version of RS you created the report under (RS2000, RS2005 RTM, SP1, SP2) versus which version you're trying to view it under.

Like you, I have seen this before.

Jarret

|||

I think that it is not "random behavior". As I know the behavior is:

1. If default value isn't query-based and not an expression - you will see original default value

2. If default value isn't query-based but an expression - you will see "Override Default" button instead of expression result

3. If default value is query-based - you will see text "Query Based"

|||

Alright, now we're talking. This is the kind of answer I was looking for, someone who knows the behavior!

So in the past I have had the default values be expressions. For this particular report, I just plugged in numbers. However, I put them in the following format: =2.0. Would that be considered an expression instead of just a value?

|||

miguelito928 wrote:

Alright, now we're talking. This is the kind of answer I was looking for, someone who knows the behavior!

So in the past I have had the default values be expressions. For this particular report, I just plugged in numbers. However, I put them in the following format: =2.0. Would that be considered an expression instead of just a value?

I'm pretty sure you just have to select a default value in the parameters option. I can check when I get to work if you don't confirm this to be true until then

Here's how I believe it works:

-> Add a new parameter called CategoryId, for example;

-> In the values list I'm guessing you'll retrieve them from a query that returns at least an Id and a Label;

-> In the option below the values list you have the option to add a default value, which can also be returned by a query.

Basicly what this 3 item list means is that let's imagin you have a query that returns these values:

1 - Meat

2 - Fish

3 - Fruit

It's a perfect query for your values list! Now, for the default value selection you would want it to be something like:

SELECT C.Id, C.Alias FROM Categories C WHERE C.Default = 1;

This query would return you the default category to use in your report parameter. Something like this:

1 - Meat

Best regards,

Ahkaru

|||

No, your post wasn't helpful at all. I'm not getting my default values from queries.

I am setting the default value of my parameter to "=2.0". This seems to be a non-queried expression, which would explain why I am getting an "Override Default" button instead of a text box with the value in it. The type of my parameters are floats by the way. I just noticed that the report written by someone else has strings and the default values are entered in without the equals sign in front.

So I decided to try and remove the equals signs and now it is showing that there are no default values. Is there no way to enter non-expression non-queried values from the Visual Studio report builder?

|||Ok, I get it to work if you leave all the default values blank and then fill them in through the Report Manager console after you deploy the report. The only way to deploy the report with default values is using expressions and putting equals signs in front, which causes "Override Default" buttons. Thank you to Andrey for his knowledge of the behavior.

"Open Table" NOT WORKING in Management Studio

When I open a database and right click and select "Open Table" I get the error message "Object reference not set to...". What could the issue be. I have loaded the adventure works db and tried it also and still get the same error. Could someone at MS please respond to this. Also when open table works can I directly edit values in the result pane like I did in Sql Server 2000?

This forum is for Analysis Services -related questions. Try posting on "SQL Server Tools General" forum.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Open Table" NOT WORKING in Management Studio

When I open a database and right click and select "Open Table" I get the error message "Object reference not set to...". What could the issue be. I have loaded the adventure works db and tried it also and still get the same error. Could someone at MS please respond to this. Also when open table works can I directly edit values in the result pane like I did in Sql Server 2000?

This forum is for Analysis Services -related questions. Try posting on "SQL Server Tools General" forum.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Open Table" NOT WORKING in Management Studio

When I open a database and right click and select "Open Table" I get the error message "Object reference not set to...". What could the issue be. I have loaded the adventure works db and tried it also and still get the same error. Could someone at MS please respond to this. Also when open table works can I directly edit values in the result pane like I did in Sql Server 2000?

David,

I will do some research on "Object reference not set to" error. You can edit data directly from the results pane.

Thanks!

|||

David,

We need more information about this error. Are you still able to reproduce this error?

Thanks!

|||

I have never been able to explain why it happened. When I would try to do "open table" I would always get the "object ref not set" error. I did uninstall and when I re-installed the install locked up on "Setting File Security". I had seen that error before and knew to unplug the network connection. After I reinstalled the error went away.

I wanted to know if we can get behahivior similiar to 2000 where a user could enter a sql select and then edit the results in results pane. The open table helps but when you want to quickly change a value the edit of a few rows is easier than finding a row in a large result set. Also I noticed when I unistalled I had to uninstall each component separately. Can the uninstall of sql server 2005 uninstall all components.

thanks

|||

Sounds like "object ref not set" error might have been due to corrupted installation. Please let us know if you encounter that error again.

Current SQL Editor does not allow you to edit directly from the results grid as you've noticed. You can choose Open Table and bring up SQL Pane from the Query Designer by either clicking on a toolbar icon (a whitebox with SQL text in it) or hitting CTRL+3. Then edit the SQL syntax to bring up a sub-set of records for editing.

For uninstallation issue, please provide your feedback through http://lab.msdn.microsoft.com/productfeedback/Default.aspx. All feedbacks received via our Product Feedback center are reviewed by the team and we treat them seriously.

Hope this helps.

Thanks!

|||

Can you give us the logic behind why you can't edit the result set of a query?!?!

I am, frankly, astonished that this feature was removed. It is truly one of the most useful features for a quick edit of data.

On that note, the workaround is that you "open the table"? Am I missing something that doing an "open table" produces all data in the table? So, we have to burden the machine with potentially thousands upon thousands of records just to edit a single field? Crazy!

Also, using a join query after "opening" the table results in read only!

The other way around is to find the right record ID, then write an update query?

Seriously, is there any explanation because it sounds completely ludicrous to me? What was the point of this?

/sorry to seem so annoyed, but so many people rely on this feature. I know I'm not the only one.

"Open Table" NOT WORKING in Management Studio

When I open a database and right click and select "Open Table" I get the error message "Object reference not set to...". What could the issue be. I have loaded the adventure works db and tried it also and still get the same error. Could someone at MS please respond to this. Also when open table works can I directly edit values in the result pane like I did in Sql Server 2000?

David,

I will do some research on "Object reference not set to" error. You can edit data directly from the results pane.

Thanks!

|||

David,

We need more information about this error. Are you still able to reproduce this error?

Thanks!

|||

I have never been able to explain why it happened. When I would try to do "open table" I would always get the "object ref not set" error. I did uninstall and when I re-installed the install locked up on "Setting File Security". I had seen that error before and knew to unplug the network connection. After I reinstalled the error went away.

I wanted to know if we can get behahivior similiar to 2000 where a user could enter a sql select and then edit the results in results pane. The open table helps but when you want to quickly change a value the edit of a few rows is easier than finding a row in a large result set. Also I noticed when I unistalled I had to uninstall each component separately. Can the uninstall of sql server 2005 uninstall all components.

thanks

|||

Sounds like "object ref not set" error might have been due to corrupted installation. Please let us know if you encounter that error again.

Current SQL Editor does not allow you to edit directly from the results grid as you've noticed. You can choose Open Table and bring up SQL Pane from the Query Designer by either clicking on a toolbar icon (a whitebox with SQL text in it) or hitting CTRL+3. Then edit the SQL syntax to bring up a sub-set of records for editing.

For uninstallation issue, please provide your feedback through http://lab.msdn.microsoft.com/productfeedback/Default.aspx. All feedbacks received via our Product Feedback center are reviewed by the team and we treat them seriously.

Hope this helps.

Thanks!

|||

Can you give us the logic behind why you can't edit the result set of a query?!?!

I am, frankly, astonished that this feature was removed. It is truly one of the most useful features for a quick edit of data.

On that note, the workaround is that you "open the table"? Am I missing something that doing an "open table" produces all data in the table? So, we have to burden the machine with potentially thousands upon thousands of records just to edit a single field? Crazy!

Also, using a join query after "opening" the table results in read only!

The other way around is to find the right record ID, then write an update query?

Seriously, is there any explanation because it sounds completely ludicrous to me? What was the point of this?

/sorry to seem so annoyed, but so many people rely on this feature. I know I'm not the only one.

"Open Table" NOT WORKING in Management Studio

When I open a database and right click and select "Open Table" I get the error message "Object reference not set to...". What could the issue be. I have loaded the adventure works db and tried it also and still get the same error. Could someone at MS please respond to this. Also when open table works can I directly edit values in the result pane like I did in Sql Server 2000?

David,

I will do some research on "Object reference not set to" error. You can edit data directly from the results pane.

Thanks!

|||

David,

We need more information about this error. Are you still able to reproduce this error?

Thanks!

|||

I have never been able to explain why it happened. When I would try to do "open table" I would always get the "object ref not set" error. I did uninstall and when I re-installed the install locked up on "Setting File Security". I had seen that error before and knew to unplug the network connection. After I reinstalled the error went away.

I wanted to know if we can get behahivior similiar to 2000 where a user could enter a sql select and then edit the results in results pane. The open table helps but when you want to quickly change a value the edit of a few rows is easier than finding a row in a large result set. Also I noticed when I unistalled I had to uninstall each component separately. Can the uninstall of sql server 2005 uninstall all components.

thanks

|||

Sounds like "object ref not set" error might have been due to corrupted installation. Please let us know if you encounter that error again.

Current SQL Editor does not allow you to edit directly from the results grid as you've noticed. You can choose Open Table and bring up SQL Pane from the Query Designer by either clicking on a toolbar icon (a whitebox with SQL text in it) or hitting CTRL+3. Then edit the SQL syntax to bring up a sub-set of records for editing.

For uninstallation issue, please provide your feedback through http://lab.msdn.microsoft.com/productfeedback/Default.aspx. All feedbacks received via our Product Feedback center are reviewed by the team and we treat them seriously.

Hope this helps.

Thanks!

|||

Can you give us the logic behind why you can't edit the result set of a query?!?!

I am, frankly, astonished that this feature was removed. It is truly one of the most useful features for a quick edit of data.

On that note, the workaround is that you "open the table"? Am I missing something that doing an "open table" produces all data in the table? So, we have to burden the machine with potentially thousands upon thousands of records just to edit a single field? Crazy!

Also, using a join query after "opening" the table results in read only!

The other way around is to find the right record ID, then write an update query?

Seriously, is there any explanation because it sounds completely ludicrous to me? What was the point of this?

/sorry to seem so annoyed, but so many people rely on this feature. I know I'm not the only one.

"Logon failure: unknown user name or bad password"

First, I checked all the obvious problems. The password is right and the login works perfectly.
Here is the output from Developer Studio when trying to deploy/process a cube:

Performing an incremental deployment of the 'MaxMinManufacturingDM' database to the 'localhost' server.
Generating deployment script...
Process Database MaxMinManufacturingDM
Done
Sending deployment script to the server...
Error -1056899072 : The following system error occurred: Logon failure: unknown user name or bad password. .
Error -1055784860 : Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Max Min Manufacturing DM', Name of 'Max Min Manufacturing DM'.
Error -1054932980 : Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Manufacturing Fact', Name of 'Dim Time' was being processed.
Error -1054932979 : Errors in the OLAP storage engine: An error occurred while the 'Year Of Manufacture' attribute of the 'Dim Time' dimension from the 'MaxMinManufacturingDM' database was being processed.

My Analysis Services project (or Business Intelligence project) has only one Data Source, "Max Min Manufacturing DM.ds". I'm using a SQL Server login with a saved password.

I double click the data source to get to the "Data Source Designer" dialog and see the following connection string:

Provider=SQLNCLI.1;Data Source=localhost;Persist Security Info=True;Password=**********;User ID=MaxMinUser;Initial Catalog=MaxMinManufacturingDM

I click "Edit" and "Test Connection" and get "Test connection succeeded". The "Save my password" option is checked. The password is fine and the login should works perfectly. Developer Studio can obviously connect to the database since I've done all the design through it. I can't imagine why I'm getting this error.

I'm using:

Windows XP (dev machine)
Relational Data Mart is using SQL Server 2000 SP4 (I can't upgrade to SQL Server 2005 for business reasons beyond my control)
Visual Studio Studio 2005
SQL Server Analysis Services 2005 (I believe I put SP1 on this).

Any idea?

Hello. Are you running the SQL Server services and the SSAS2005 services with the same or different accounts?

When you process a cube the SSAS2005 must have permissions to read data from the source database. If you run SSAS2005 on a separate machine than the sourec database and the SSAS2005 service account is running as "local system" this server have no permissions on other servers/machines.

You can check this is the SQL Server Configuration manager(for SSAS2005).

Also, try the default impersonation mode for the data source connection.

HTH

Thomas Ivarsson

|||Great!!! Setting the "impersonation mode" to default worked. I guess I should read up on that so I understand what the difference between the impersonation mode and the database login is.

Yes, everything is running on the same server (it's a development box): SSAS2005, MSSQL2000, and Visual Studio.

"lenght cannot be less than zero. Parameter name : lenght"

I'm using Visual Studio 2005, and when i try to drop a table from a data source( SQL Mobile database), to a new or existing form, always occors the error ""lenght cannot be less than zero. Parameter name : lenght"" , my project has more than one forms.
If i make the same steps on a new project with only one form, i can drop the same table without problems.
Anyone can help with this problem?

best regards,

Pedro Nogueira

Pedro,

It sounds like you are using the drag and drop data binding in a Windows Forms application using SQL Mobile as the data source?

First I recommend ensuring that you are running VS2005 Service Pack 1. If you are or still have this issue after upgrading, to recreate

this, we would need some insight into your database schema and how you are doing the drag and drop onto the form (are you dropping

the whole table? are you bound to a datagrid or to another control, etc)

What I'm saying is that I don't hear of anyone having problems with drag & drop of SQL Mobile/SQL CE tables onto forms with

VS2005 SP1, so you either have a bad install or have indeed found a bug. Happy to help you with that but would need more info

on your database and how you're doing the binding.

Darren Shaffer

"Hang" when deploying SSAS solution?

I've noticed that BI Studio seems to 'hang' when I do a Build -> Deploy Solution. The output window will just say "Sending deployment script to the server" and the Deployment Progress window will just churn, with no commands listed. It's been running for nearly ~ 1 hr without feedback - how can I tell if AS is working or not? CPU on the AS instance is idle.

The one workaround I've noticed is to open the database directly in BI Studio, and make the changes there, but this is obviously less than ideal for multiple reasons.

hello,

i'd suggest to check what's the deployment server specified in your project and whether it's as expected. right click on the project node in solution explorer, and go to Properties->Deployment, Target->Server.

also, it should be possible to use SQL Server Profiler to start a trace for the specific AS server, and see what happens on the server when you do a Build->Deploy Solution...

hope this helps,

|||The target server is just "localhost" (which is correct). When I put profiler on it, I can see the large XMLA deployment script, but it doesn't reveal anything about the current status..|||Ok. I created a fresh, new, import from 9.0 project, and made my changes there. Now when I tried to deploy it actually looks like it's doing something (i.e. there's activity in profiler, and the deployment progress tab actually shows what dimensions/measure groups are being processed..)

Very weird.|||Restart the Analysis Services Service on the target deployment server (if possible) before you try to deploy the roject again and see what happens. Seems like something may be hanging up the service when this happens.