Media Manager on a box running SQL Server

dugo wrote on 5/28/2005, 7:19 PM
Howdy

I just installed Vegas 6, and mid-install it went and installed this Media Manager beast without any previous indication of what it included, or where I might like it to go.

Colour me surprised.

Unfortunately, my box is also running SQL Server - so now it has two SQL Server Instances on it. (One being MSDE as installed by Vegas as part of Media Manager)

My questions are:

1) How are MSDE and SQL Server going to interact?
2) Can I get rid of the MSDE install and have Media Manager run against SQL Server instead (thereby getting back the several dozen MB of memory it's using)
3) Is Media Manager going to be confused by the two instances?
4) Microsoft Baseline Security Analyzer shows a number of vulnerabilities in this install; should this worry me?
5) How do I hook up my SQL Server Manager and other SQL Server tools to this instance?
6) If I run the uninstaller, will it only take out MSDE?

I've scanned the release notes and the docs and I can't see any mention of MSDE being installed, or customizing how/where Media Manager stores data.

Does anyone have experience of this configuration? Do I have anything to worry about? :-o

Thanks

Doug

Comments

JohnnyRoy wrote on 5/29/2005, 4:24 AM
The Media Manager uses the desktop SQL engine which has a different way of connecting clients than the SQL server engine so I believe you need both installed. Sony has been asked if the Media Manager could use the SQL server engine and the answer was, “no but we’ll consider it as a future feature”. So I would say you are stuck with two instances for now.

You have to admit it is an odd setup to have a desktop NLE system running SQL server. Ideally, this should be running on a dedicated server somewhere in your network on a PC that no one uses as a workstation.

~jr
ForumAdmin wrote on 5/31/2005, 8:47 AM
SQL Server supports up to 16 "instances" on a single PC. This is done because different programs may have very different configuration requirements for SQL Server itself (not just per database).

Each instance is completely independent of each other. Getting rid of one instance really won't save you much memory because if they both happen to be running, they will have completely separate databases loaded. The physical memory pages used for the code will be shared between the two processes due to Win32 virtual memory mapping.

We don't currently support hosting the media manager databases on just any SQL Server with a custom connection string. We connect to the SONY_MEDIAMGR instance using the shared memory connection and do not install the networking libraries to reduce exposure. We are evaluating this area for future versions, but no specific feature commitments have been made.

We also don't support using the SQL Server tools at this point. You can try to use them, but since they do not come with MSDE they are unsupported. In the Media Manager options dialog, we offer the ability for Vegas & ACID to automatically start/stop the MSDE service to reduce resource usage when you are not running Vegas or ACID if you are resource constrained. The MSDE service is also configured to not auto start with Windows on a reboot (Vegas or ACID will start it as needed).

If you use the Media Manager to back up your media library, the library indices are rebuilt and database free space recovered during this process so there really isn't much need for a separate management tool for our use of MSDE.