Showing posts with label particular. Show all posts
Showing posts with label particular. Show all posts

Thursday, March 29, 2012

Drag & Drop Multiple Query Files Into Management Studio

In SQL Server 2000, you could have a Query Analyzer (QA) query window open to a particular database, and drag and drop a group of query files from Windows Explorer on it. QA would then open a query window for each of the files, and automatically default it to that database.

I am trying to get the same functionality in SQL Server 2005 Management Studio, but it nags me with the "Connect to Database Engine" dialog box for every file. Worse still, it will not default to the same database being used by the query window on which it was dropped. And to add insult to injury, it makes you click the options button to change to other than the default database. The behavior is the same in both the tabbed and MDI environment.

I have looked for settings that would affect this behavior, but didn't notice any. Does anyone know if this behavior is possible with 2005? If so, how to you implement it? Thanks.

Kevin

Did you find an answer to your problem? I have just started using SQL Server 2005 and I am having the same problem.

Thanks

Danny

|||

Even if I use "open file" to open saved queries I get asked each time to connect to the database engine. What am I doing wrong?

Thanks

Danny

|||Unfortunately I still have not found a way around the problem. I assume it's something we will have to live with.|||

One of the solutions would be to create a SQL Project with connection info and the related query files as members of a the project. This is similar to the VS project model

You can have multiple projects with different connection settings in a solution.
You may also be able to leverage the new SQLCMD internal commands to embed the connect statement within your scripts.

Thanks,
Ramesh

|||There must be an easier solution to this. Shocking!|||

Please raise a suggestion at the product feedback centre

http://lab.msdn.microsoft.com/ProductFeedback

|||Added a suggestion - http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackId=FDBK48385

Drag & Drop Multiple Query Files Into Management Studio

In SQL Server 2000, you could have a Query Analyzer (QA) query window open to a particular database, and drag and drop a group of query files from Windows Explorer on it. QA would then open a query window for each of the files, and automatically default it to that database.

I am trying to get the same functionality in SQL Server 2005 Management Studio, but it nags me with the "Connect to Database Engine" dialog box for every file. Worse still, it will not default to the same database being used by the query window on which it was dropped. And to add insult to injury, it makes you click the options button to change to other than the default database. The behavior is the same in both the tabbed and MDI environment.

I have looked for settings that would affect this behavior, but didn't notice any. Does anyone know if this behavior is possible with 2005? If so, how to you implement it? Thanks.

Kevin

Did you find an answer to your problem? I have just started using SQL Server 2005 and I am having the same problem.

Thanks

Danny

|||

Even if I use "open file" to open saved queries I get asked each time to connect to the database engine. What am I doing wrong?

Thanks

Danny

|||Unfortunately I still have not found a way around the problem. I assume it's something we will have to live with.|||

One of the solutions would be to create a SQL Project with connection info and the related query files as members of a the project. This is similar to the VS project model

You can have multiple projects with different connection settings in a solution.
You may also be able to leverage the new SQLCMD internal commands to embed the connect statement within your scripts.

Thanks,
Ramesh

|||There must be an easier solution to this. Shocking!|||

Please raise a suggestion at the product feedback centre

http://lab.msdn.microsoft.com/ProductFeedback

|||Added a suggestion - http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackId=FDBK48385

Sunday, February 26, 2012

Dont get component choices during installation. Installation finishes without db en iis re

Hallo,
I've tried several times installing RS on a particular machine. The
installation finishes without error messages and without installing the RS
components.
During RS installation on a member server (Win2003, SQL2000 Std SP3a, RS
2000 Std) i dont get the usual Server Components choices and so on. The
usual warning about Visual Studio apperas. But then as i click "Next" in the
warning box the installation just continues on. The box "To continue please
click next" appears but i dont get a chance to click next as the
installation just goes on "automatically". The installation rolls on and on
but after it says it finished successfully the IIS mappings and the RS DBs
arent there.
In this newsgroup I found someone (Johan - post: RS Installation fail
without message) with the same issue, although MS (Brad Syputa) took a look
at it, it did not seem resolved.
Does anybody know what to do about this?
Mike van DuijnDon't know for sure if this is your problem but we had the same issue
when we were trying to install RS on a couple development laptops.
Turned out, we *thought* we were running SQL Server developer on those
laptops. We were actually running SQL Server Personal. If there's any
disagreement between the versions, it won't show you the server
components.
Confirm your SQL Version and the version of your RS CD. My guess is
that you are trying to install Reporting Services Developer on SQL
Server Standard or something like that.
Hope this helps,
Tim
mike wrote:
> Hallo,
> I've tried several times installing RS on a particular machine. The
> installation finishes without error messages and without installing the RS
> components.
> During RS installation on a member server (Win2003, SQL2000 Std SP3a, RS
> 2000 Std) i dont get the usual Server Components choices and so on. The
> usual warning about Visual Studio apperas. But then as i click "Next" in the
> warning box the installation just continues on. The box "To continue please
> click next" appears but i dont get a chance to click next as the
> installation just goes on "automatically". The installation rolls on and on
> but after it says it finished successfully the IIS mappings and the RS DBs
> arent there.
> In this newsgroup I found someone (Johan - post: RS Installation fail
> without message) with the same issue, although MS (Brad Syputa) took a look
> at it, it did not seem resolved.
> Does anybody know what to do about this?
> Mike van Duijn

Friday, February 17, 2012

Doesn't like a particular namespace

Hi,
Can someone try and replicate an error for me. Follow these steps:
1) Create a new package
2) Place a Sequence container in it
3) Create a variable called User::ContainerStartTime scoped to the package
4) Create a variable called User::ContainerStartTime scoped to the sequence container
5) Change the namespaces of the 2 variables from "User" to "Metadata"

You get an error on step 5 saying another object in the collection already has that name yet it doesn't mind them when they're both called User::ContainerStartTime

Why?
-JamieOk, I also got an error following those steps... Weird.
Could it be that the scopes only exists in the user namespace?
|||Yes Jamie, I replicated it as well. I am on Sep CTP. I agree it should complain for User namespace as well as Metadata. Why is Metadata namespace different?|||

Samuel L wrote:

Ok, I also got an error following those steps... Weird.
Could it be that the scopes only exists in the user namespace?

Seems that way. If that's true I'd say its a bug!

-Jamie|||

Sutha Thiru wrote:

Yes Jamie, I replicated it as well. I am on Sep CTP. I agree it should complain for User namespace as well as Metadata. Why is Metadata namespace different?

It actually happens for any user-defined namespace (e.g. change "Metadata" to "Foo") (Confusingly the User namespace isn't a user-defined namespace!!!)

-Jamie|||The problem is that scopes are not part of the qualified name. Whilst the inner variable should override the outer, they are obviously hitting a problem during variable access or enumertion whereby the inner object can still see the outer variables.

At runtime when reading the value, you would only get the value of the inner variable, and there is no way to request the outer, as you can only use the qualfied name, not scope or id, and the name is the same.

I hit the same problem myself during some development, you get more variables than you expect, the scope is different, but the qualified name is the same. By design apparently, although clearly there is a bug in the UI.|||Yep, this is a bug. What's interesting is if you change the order of renaming, it doesn't happen. Looks like there is an order of execution bug.
Change the local scoped variable first and then the outer scoped variable and it won't repro.
Please open a bug.
Thanks,
K|||OK. 209356710|||The bug has been closed apparently cos it can't be reproduced. Which I find strange seeing as 4 people on this thread repro'd it and I have just now repro'd it on RTM.

https://beta.microsoft.com/source/BPBugDetails.asp?TrackID=209356710&ProgID=969000000&FormID=2718&BPW=141044
Apologies for being a bit blunt but what's the point in us raising bugs if they're ignored?|||

Hi Jamie,

Yes, but we had already found and fixed it for SP1 and that is what it is being tested on for repro and closure, since we are no longer testing on RTM. A better resolution would have been no longer repro and comments should have been given as to why it was closed but the problem has been addressed. Thanks for reporting this issue, we appreciate your feedback.

Matt

|||Fair enough Matt. Thanks for the reply!

-Jamie

Doesn't like a particular namespace

Hi,
Can someone try and replicate an error for me. Follow these steps:
1) Create a new package
2) Place a Sequence container in it
3) Create a variable called User::ContainerStartTime scoped to the package
4) Create a variable called User::ContainerStartTime scoped to the sequence container
5) Change the namespaces of the 2 variables from "User" to "Metadata"

You get an error on step 5 saying another object in the collection already has that name yet it doesn't mind them when they're both called User::ContainerStartTime

Why?
-JamieOk, I also got an error following those steps... Weird.
Could it be that the scopes only exists in the user namespace?
|||Yes Jamie, I replicated it as well. I am on Sep CTP. I agree it should complain for User namespace as well as Metadata. Why is Metadata namespace different?|||

Samuel L wrote:

Ok, I also got an error following those steps... Weird.
Could it be that the scopes only exists in the user namespace?

Seems that way. If that's true I'd say its a bug!

-Jamie|||

Sutha Thiru wrote:

Yes Jamie, I replicated it as well. I am on Sep CTP. I agree it should complain for User namespace as well as Metadata. Why is Metadata namespace different?

It actually happens for any user-defined namespace (e.g. change "Metadata" to "Foo") (Confusingly the User namespace isn't a user-defined namespace!!!)

-Jamie|||The problem is that scopes are not part of the qualified name. Whilst the inner variable should override the outer, they are obviously hitting a problem during variable access or enumertion whereby the inner object can still see the outer variables.

At runtime when reading the value, you would only get the value of the inner variable, and there is no way to request the outer, as you can only use the qualfied name, not scope or id, and the name is the same.

I hit the same problem myself during some development, you get more variables than you expect, the scope is different, but the qualified name is the same. By design apparently, although clearly there is a bug in the UI.|||Yep, this is a bug. What's interesting is if you change the order of renaming, it doesn't happen. Looks like there is an order of execution bug.
Change the local scoped variable first and then the outer scoped variable and it won't repro.
Please open a bug.
Thanks,
K|||OK. 209356710|||The bug has been closed apparently cos it can't be reproduced. Which I find strange seeing as 4 people on this thread repro'd it and I have just now repro'd it on RTM.

https://beta.microsoft.com/source/BPBugDetails.asp?TrackID=209356710&ProgID=969000000&FormID=2718&BPW=141044
Apologies for being a bit blunt but what's the point in us raising bugs if they're ignored?|||

Hi Jamie,

Yes, but we had already found and fixed it for SP1 and that is what it is being tested on for repro and closure, since we are no longer testing on RTM. A better resolution would have been no longer repro and comments should have been given as to why it was closed but the problem has been addressed. Thanks for reporting this issue, we appreciate your feedback.

Matt

|||Fair enough Matt. Thanks for the reply!

-Jamie