Backing up SQL Server 2005 Express

How can I back up existing SQL Server 2005 Express tables? I'm presently developing on a 4 year old laptop which is toooo sloooow and need to transfer the tables and data to a desktop system.

Copy the MyDatabase.mdf and MyDatabase.ldf files to the new system.

In the new system, use Attach... from SQL studio, to connect to the copied database.

Background replication

We are developing a embedded system based on Windows CE 5 and SQL Server CE 3 in C++ where we need to do merge replication in background while the front end application still need to perform operations on the database. A solution would be to run the merge replication on a separate thread while the application thread still can access the database to do inserts and updates. I have been researching if it is possible to access the database with queries during a merge replication, but I can not find an answere. Does anyone have experience of this and generally know if it is possible to implement with SQL Server CE 3 in the native API?

Best regards

Johan Johansson

This article may help you understand the implications of a user trying to access SQL Mobile while merge replication is happening.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5mobilesynch.asp

Darren

|||

Thanks Darren, this is exactly what I was looking for.

Best regards

Johan

Back Button in RS 2000?

Hello.
I'm developing reports in Reporting Services 2000 and Visual Studio 2003. I
have a "drill-through" report. Upon drilling through to the report, and then
clicking the back button to return to the main report, the report doesn't
even render. However, while developing the report and previewing it in VS
2003, there is a back button supplied there that works perfectly every time.
My question is this: is there a way to tell Reporting Services to include a
back button like the one in the report designer on the deployed report?
Alternatively, is there a way to provide a hyperlink in the drill-through
report that takes the user back to the original report (with all parameters
included in the link)?
Thanks!
JohnA small Back button is available in 2005. If it is not a parameter report
then it would have been easy, but since the main report is parameter based,
you can have a back button link and once you click; it comes back to the
main page and waits for parameter. So really it doesn;t serves your purpose.
But if the main page can wait for the input then you can use this method.
Amarnath
"JohnJohn" wrote:
> Hello.
> I'm developing reports in Reporting Services 2000 and Visual Studio 2003. I
> have a "drill-through" report. Upon drilling through to the report, and then
> clicking the back button to return to the main report, the report doesn't
> even render. However, while developing the report and previewing it in VS
> 2003, there is a back button supplied there that works perfectly every time.
> My question is this: is there a way to tell Reporting Services to include a
> back button like the one in the report designer on the deployed report?
> Alternatively, is there a way to provide a hyperlink in the drill-through
> report that takes the user back to the original report (with all parameters
> included in the link)?
> Thanks!
> John

Avoiding ASPNETDB SQL database?

Hello.

I have been developing a small site that has two backend SQL Server databases. One for my application data and one for the ASPNETDB database that is created by the ASP .NET Configuration utility.

Is it possible to configure the ASP .NET Configuration tool to use my custom database instead of creating a second database called ASPNETDB?

Thanks in advance.

Kev

You first step would be to create the required ASP.NET required tables and objects. You would need to run the aspnet_regsql.exe tool located in the C:\<WindowsDir>\Framework\<frameworkversion> folder.

After that you need to change the connectionstrings section of you Web.Config.

|||

Thanks for the swift response jguadagno - much appreciated.

I ran the aspnet_regsql.exe utility and updated the connection string in the web.config file and that works perfectly.

Thanks again.