Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Moving The SQL Database

Our SQL DBAs want to move the current database from it's default location to one of their standard locations ( still local but on it's own drive ).

1. Can this be done?

2. What are the steps required to facilitate this? Basically the database is going to be moved from the C Drive to the E Drive.

Kind Regards

Find more posts tagged with

Accepted answers

All comments

solarwinds-admin

Hi Tony,

you sure can.

Stop the EminentWare service.

Install if you dont already have SQL Server Management Studio Express (or full).

Select the EminentWare instance.

Go to the EminentWare DB and say Detach.

In the file system, literally move the mdf/log files from the EminentWare\database folder to the new E drive location.

Ensure the permissions on this folder mirror the original EminentWare\database folder permissions.

Reattach the mdf file

Start the EminentWare service.

That should be it.

solarwinds-admin

Just to verify. The EminentWare Database can be moved to a different server SQL server? And can it be moved to SQL 2008 also?

One other question. We are looking to create a 'Approved Application List' for our workstations. We would like to run a report that would compare desktop software that we have verified as approved to all software that is currently installed. The report would then generate the differences. Can we access the Database with MS Report Services that insert a table for approved so that we can generate a new report in Eminentware Reporting for this functionallity? Or can we create our own GUI that can access the database and run this report?

solarwinds-admin

"MOVED" is a concept that needs to be further clarified. We do not currently have a documented procedure for migrating an active EminentWare Extension Pack Server, but if migration is needed, it can be arranged through Professional Services. The above procedure is provided to permit the relocation of the MDF and LDF files on the SAME SERVER, but in a different location of that server's filesystem (i.e. on a different volume of the same server).

The Extension Pack can be INSTALLED to SQL Server 2008, and using Advanced Deployment methods, the Management Role can be installed on a database server to faciliate the storage of inventory/reporting data in a central database server, as an alternative to storing the inventory/reporting data on the Primary Application Server. However, each individual Extension Pack role server still requires a locally installed copy of SQL Server. For Application Role servers and Automation Role servers, the installation of SQL Server 2005 Express Edition is more than sufficient.

You can access any Extension Pack report via SQL Server Reporting Services. All report definitions expose the raw SQL code used to build the dataset displayed in the Extension Pack Report Viewer. A datasource can be defined on the RS server to access the Extension Pack database and use the SQL code for that report. You can customize that SQL code to join tables across datasources (databases) in SSRS, or populate that data into an alternate database. The Extension Pack database schema is not formally documented, but the SQL code that is exposed can provide sufficient information to identify what tables or view data can be obtained from.

Additionally, all Extension Pack reports can be exported to Excel, Access, XML, and CSV formats. Those exports can also be used to populate data into a custom database (i.e. one containing your Approved Application List) from where custom reports can then be generated for comparison and compliance purposes.

We do not support modifications to the schema of the Extension Pack database, and the database schema is subject to change, without notice, as a result of any hotfix or service release.

solarwinds-admin

So what is your recommendation for the setup of the environment. Does the Extension Pack system need a 'full' reinstall on a system that already has a install of SQL 2008 enterprise? Could we install SQL 2008 enterprise to the existing system and configure the inventory reporting data to use SQL2k8 ent instead? If we decide to use a central database server on a different server that has sql2k8 ent installed are the Advanced Deployment method documented?

If we make no changes to the existing configuration how can we access the database with a RS? What is the connection infomation? Does the linking / joining of the datasouces add considerable time to the report generation?

It really comes down to this. Should the system be rebuilt and SQL2008 ent installed first or can this be added to the existing configuration?

Thx