Database Export Wizard for ASP.net and SQL Server

A step wizard for ASP.net to export database objects to CSV, TXT, HTML, XML, or SQL. it guides users through a few simple steps to choose a database object (table, view, or query), select columns, and export the data in any of the standard formats CSV, HTML, XML, or SQL.

I'm trying to get used to sql server 2008 having been
forced to upgrade by my isp. I need to back up my key db on a weekly
remote schedule, so have been trying to use ssms to export data from my
remote db to a local copy.

Firstly I created a new empty db on
the local machine. Then I scripted the structure of the db on the
remote machine and ran the resulting query on the local machin

There is a credential on MOJITO defined for CBMIWEB\johna. There is a proxy on MOJITO that uses that credential. The job has one step and in the properties I have set the RUN AS value for the job to be the name of the Proxy. The proxy is established for
SSIS jobs.

The "owner" of the job is also CBMIWEB\johna which is a domain userid in the local Administrators group of each machine (both TUNA and MOJITO). This userid has been granted the permission to
Logon as a Batch Job on both servers.

TUNA is a Windows 2000 standalone server; MOJITO is Windows 2003. I can logon to each server as CBMIWEB\johna.

Whenever I try to import or export data using SQL Server Import And Export Wizard, everything is great until I click on the "Finish" button.

The wizard gets to the "Setting Source Connection" step and at 0% complete, I get the message "SQL Server Import and Export Wizard Has Encountered A Problem And Needs To Close." This happens every time I run the Wizard, whether it be from SSMS, BIDS,
or the file manager. It doesn't matter what type of database table/file I import to or export from.

If I select to Debug, I get this message: "Windows Has Triggered A Breakpoint In DTSWizard.exe. This may be due to a corruption of the heap, and indicates a bug in DTSWizard.exe or any of the DLL's it has loaded. The output window may have
more diagnostic information." Here is the output:

As you all know moving the database from one server(2000, 2005, 2008) to (2000, 20005, 20008) is not a big deal and can be done in many ways like backup-restore, attcah-detach, and most easy (some time very complex:-)).

Here i wanna discuss an issue which i have faced.

I have two instances of SQL server 2008, i have created a new database Test in one instance, created few logins and mapped to Test database with some permissions for this Test database.

Now i used copy database wizard to copy this test database to other instance, i sucessfully went through the wizard and selected SQL server object method to copy the Test database in other instance then i followed the remaing wizard, i selected the logins which i have created for the Test database and finnaly i reached the finish button i clicked finished and the copy of database completed sucessfully. I verified that Test dabase was there in other instance with the logins which i have created. So easy i was happy:-)

Problem: Some other day i wanted to copy AdventureWork database to the other instance of SQl server i was happy that its a very easy task i followed the same steps above(to copy the Test database ) and every thing went in the same way and i clicked finish to complete the wizard it took some time

I'm trying to setup SSRS using the Reporting Services Configuration Manager. Everything seems to be working except the database creation. When I click on the Database (3rd option down) then Change Database I run through the wizard. Put
in proper SA credentials. Accept the defaults clicking next through and when it gets to running the script to create the data base I get the Error I pasted below. We do not have a G drive so I went into SSMS and changed the Default Database settings
to point to the F drive (where our other DBs reside) - I got that tip off of this forum but it didn't fix my issue. Any ideas what to try next? Do I need to stop and restart a service or something? Thanks for any help you guys can offer.

System.Data.SqlClient.SqlException: Directory lookup for the file "G:\mssql\data\ReportServer.mdf" failed with the operating system error 3(The system cannot find the path specified.).

If you use the Enterprise Architect edition of Microsoft Visio for data modeling regularly, then there is a good chance that at some point you've wanted to export just the table names into Excel. You might want to do this to map logical ERD entities to physical data model tables, track project status by entity, or track overlap between database versions.

If you ever wanted to restore your database from a SQL backup file (.bak), but there are still users connected to your database, the backup operation will fail causing the error: Exclusive access could not be obtained because the database is in use.

A transaction is a group of SQL commands executed together as a single component of work to be accomplished. If all of these commands succeed, then a transaction is committed - the changes to the data are made final. If any of the commands within a transaction fail, then the entire transaction is cancelled, or in SQL Server terms, the transaction will be rolled back.

Transactions are one of the things that keep your data safe, but they're not necessarily easy to understand. Here's some help:

For my MCTS 70 -433 examination, I recently installed sql server 2008 and installed the sample databases too. but my issue is, in that book they have mentioned a database called "AdventureWorks2008" and the nice thing is I don't have a such a database with me in my sql server 2008.

SQL Server 2000 Meta Data Services is a repository technology that stores and manages metadata for SQL Server. Instead of building database schemas over and over, Meta Data Services allows you to freeze an entire schema for use in other projects. You can also use these schemas for training, testing, or debugging. In this article, the authors will review the various components of Meta Data Services and show how it can be programmed using a Visual Basic client, XML, and XSLT. They will also show you how to manage and manipulate your metadata by generating a simple database schema using a SQL Server repository.