MMSQL 7.0 on MMC

Hi all,

I'm facing an inconvinience with an MSSQL 7.0 installation, regarding it's accessibility in MMC. The case is as such:

When accessing the installation instance, I can navigate wihthin the tree without problems; accessing and viewing all the database, the tables, users etc within each databse. However, when highlighting a database, when it should display a summary on the right panel, it instead displays "an error occurred when trying to access the database information". Note that the puzzling thing is that accessing the database tables, users, rules etc is perfectly fine, and there is no problem with the application using the database either, in terms of accessing it.

There are also no error logged under Applications in the Event Viewer.

If you must know, an MSDE as been installed into the same machine after the MSSQL 7.0 installation.

I have not been able to find any resources on fixing this, and would appreciate if anyone can help on this matter.

Thanks.

Hi all,

Some progress report, and updates on what I've tried so far...

I've been searching and comparing this faulty MMC with a working one, and everything (setting wise) seem to be in order. I've checked registry settings, and config.ini files in the MSSQL directory, they look the same. I've even tried replacing the MSSQLServer.msc file in hopes that it was corrupted. Nothing.

I've also tried registering said MSDE into the MMC. The result? The same problem. Database, user and otherwise full access without problems. Except for the summary page when I have the database highlighted and the "Access Error" is shown. There should be none, since I can still access the database tables, users, etc by simply navigating down the explorer tree.

I would like to know though, if anyone can point me to where I might be able to see the MMC log files? Does one exist? Can I activate logging somewhere? I've been unable to find it, and am quite surmised that there is no such thing, but the programmer in me feels that something is not quite right to that. There has to be some form of logging somewhere for to troubleshoot from.

Is there a known version incompatibility between SQL7.0 and MSDE? With certain MMC/OD version? Patch levels?

Would appreciate if anyone can provide new insights.

Thanks.

Mixed bag questions (only 13)

Hi everyone,

Ok guys, I’ve summarized doubts regarding SSIS as well as odd behaviour that sometimes I suffer for my lack of knowledge or for other reasons.

So this way, I’m a pain and bore individual only one time…

Question 1:

When you have a ForEach container, i.e using as enumeraton ADO and you are debugging and seeing how is going everything, whats tasks are executing and so on, you never knows if those that were in green (executed succesfully) now are executing again or not.

Well, I’ll try to explain better: In every iteration of the loop, tasks previously executed keep its colour (green) instead of turn into white.

Question 2:

Parameter Size property is a new property for Sql Task when you have installed sp2. Well, what is it for really? I mean I’ve got some .dtsx with Sql Tasks and its values are simply -1

Question 3:

When you’re debugging a dtsx you have in the bottom locals showing you variables and so on. Problems come when you have more than 40 variables… is there any search tool? Ok, you can use

Question 4:

Outline for the tasks is lost all the time. What a nuisance! Concretely it happens in workstations running either sp1 or sp2. Amazingly it works fine in a server (2003). Memory is not related, I’m afraid, in all the scenarios 2Gb.

Question 5:

Is it possible disallow math case for variables?

Sometimes when you’re using lots of variables, it’s easy commit errors when you write code.

Question 6:

Assemblies 1.0/1.1 will be allow in VSA in a future?

Question 7:

Is it possible to change the scope for a variable in run-time? Devious question, I admit…

Question 8:

When you’re writing a Script Task you can export the script into VB extension and then be imported from a project or whatever.

What does make sense?

Question 9:

ScriptTask_32dcba2feae9428386d768f38922e162 (that’s an example) is really stored anywhere? (When you save a script task inside the IDE)

Root NameSpace is too symbolic?

Question 10:

I’m developing against Windows 2003 english version. The whole Sql25k too. No spanish at all but sometimes I receive spanish messages related with SSIS.

I don’t understand how it can be.

Nothing to do with for the fact I’m using Terminal Server, I guess.

Question 11:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1518311&SiteID=1&mode=1

Question 12:

In a foreseeable future C# will be welcomed to SSIS?

Question 13:

Is it true that there is a separate Framework 2.0 for SSIS?

Thanks indeed for the patience!!!

enric vives wrote:

Hi everyone,

Ok guys, I’ve summarized doubts regarding SSIS as well as odd behaviour that sometimes I suffer for my lack of knowledge or for other reasons.

So this way, I’m a pain and bore individual only one time…

Question 1:

When you have a ForEach container, i.e using as enumeraton ADO and you are debugging and seeing how is going everything, whats tasks are executing and so on, you never knows if those that were in green (executed succesfully) now are executing again or not.

Well, I’ll try to explain better: In every iteration of the loop, tasks previously executed keep its colour (green) instead of turn into white.

What's the question? This has been discussed in a couple of threads. Because the dev environment responds to events from from the running package, it is possible that it will not reflect the exact order of execution. And if you have tasks in your loop that take sufficent time, you will notice that they do go to yellow while they execute, and then green again when they finish.

enric vives wrote:

Question 2:

Parameter Size property is a new property for Sql Task when you have installed sp2. Well, what is it for really? I mean I’ve got some .dtsx with Sql Tasks and its values are simply -1

It's to allow you to specify the length of string parameters when they are output parameters from stored procedures. -1 is the default - it tells SSIS to use the defaults from the provider.

enric vives wrote:

Question 4:

Outline for the tasks is lost all the time. What a nuisance! Concretely it happens in workstations running either sp1 or sp2. Amazingly it works fine in a server (2003). Memory is not related, I’m afraid, in all the scenarios 2Gb.

What outline are you referring too?

enric vives wrote:

Question 5:

Is it possible disallow math case for variables?

Sometimes when you’re using lots of variables, it’s easy commit errors when you write code.

Again, not sure what you are asking for.

enric vives wrote:

Question 7:

Is it possible to change the scope for a variable in run-time? Devious question, I admit…

No.

enric vives wrote:

Question 9:

ScriptTask_32dcba2feae9428386d768f38922e162 (that’s an example) is really stored anywhere? (When you save a script task inside the IDE)

Root NameSpace is too symbolic?

It's stored in the .dtsx package.

enric vives wrote:

Question 12:

In a foreseeable future C# will be welcomed to SSIS?

Yes.

enric vives wrote:

Question 13:

Is it true that there is a separate Framework 2.0 for SSIS?

If you are refering to the .NET framework, it has it's own assemblies, but it still uses the same .NET framework as everything else.

|||

John answered most. I'll take the ones he skipped.

enric vives wrote:

Question 3:

When you’re debugging a dtsx you have in the bottom locals showing you variables and so on. Problems come when you have more than 40 variables… is there any search tool? Ok, you can use

Not that I know of. This sounds like a request for Visul Studio rather than SSIS. Got to http://connect.microsoft.com/visualstudio

enric vives wrote:

Question 6:

Assemblies 1.0/1.1 will be allow in VSA in a future?

I very much doubt it.

enric vives wrote:

Question 8:

When you’re writing a Script Task you can export the script into VB extension and then be imported from a project or whatever.

What does make sense?

Sorry Enric, not quite sure what you're asking here.

enric vives wrote:

Question 10:

I’m developing against Windows 2003 english version. The whole Sql25k too. No spanish at all but sometimes I receive spanish messages related with SSIS.

I don’t understand how it can be.

Nothing to do with for the fact I’m using Terminal Server, I guess.

Well there must be something on your machine that defines you as being Spanish. There MUST be. Otherwise how would it know? I think you can answer this one better than we can.

enric vives wrote:

Question 11:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1518311&SiteID=1&mode=1

Looks like Jay has answered this for you.

-Jamie

|||

enric vives wrote:

Question 5:

Is it possible disallow math case for variables?

Sometimes when you’re using lots of variables, it’s easy commit errors when you write code.

No. Variable names in SSIS are case sensitives so you have to deal with that.

|||

In the first place thanks a lot for your information.

Regarding 8:

I meant, you obtain class and then you can import from a Visual Basic .Net project.

4:

For all the tasks, either of them. I understand it's not problem related with memory.

|||

enric vives wrote:

In the first place thanks a lot for your information.

Regarding 8:

I meant, you obtain class and then you can import from a Visual Basic .Net project.

4:

For all the tasks, either of them. I understand it's not problem related with memory.

You can write dotnet assemblies in VB.Net and call them from the SSIS Script Task. Is that what you mean?

-Jamie

|||

No, just in reverse mode, I meant you can write classes from SSIS Script task and call them from the Visual Studio.

|||No, you can't. Why would you want to?|||

enric vives wrote:

No, just in reverse mode, I meant you can write classes from SSIS Script task and call them from the Visual Studio.

Like John said, no you can't. If you want to put "stuff" into an assembly that can be shared between SSIS and other things...you need to build the assembly in Visual Studio, not in SSIS (or the SSIS Script Task).

Does that answer the question?

-Jamie

|||Yes, thanks for that.