Hi all, I just have a quick question. Aparently theres a 40 Gig limitation on any DB that you create with the Express edition that Microsoft Offers. My question is this, If i created a couple of diffirent databases say one to hold customer data, and another to hold pictures, and another to hold music files........ How hard is it to Integrate all three databases in a web app What are some of thine things i need too do in order to make that all work Any help on this would be great thanks! -Mike-
SQL Server Express Question
Hot Topic
- Poor performance when looping through table columns
- Unable to Migrate SSAS 2000 to SSAS 2005 with MigrationWizard.exe
- dynamic SQL function for string (or value) combining from relational table into a flat view
- Master-detail on the same dataset
- Reporting Services Setup Issue
- Cannot create a connection to data source !!!! SSRS 2005
- Digitally Signing
- Cart data row
- How do i Sort the scripts in my project?
- Could not complete cursor operation because the table schema changed
SQL Server
- SQLConnect to SQL Server fails when connection intialized from a service
- Getting data from Access database and copying to SQL Server dataset - Data Type problem
- ExecuteSQLTask
- Problem When From Sequence file insert into Oracle Destination table in SSIS Package
- Good SSIS Example tutorial - User Variables
- Can't install sql server 2005
- Anyone else finding this painful?
- Foreach loop doesn't loop
- Transactions HELL
- Help in Spliting a sentence into words
SQL Server Express Question
luweewu
Hello Mike,
i think the only thing what may change in your app if you upgrade to another Sql Server Version may be the connection string which you use. Nothing else.
But even this connection string can be the same, if you don't use features which exist in Sql Server Express only like User Instances, AttachDBFileName. I don't know how XCopy Deployment is in contradiction against updating to another version.
Markus
Moonshadow
Bjorn Isaksen
if you are planing a professional, scalable solution for your application and you already reached the 4GB (not 40) border two times since now, I would rather look for the full featured product of SQL Server where you don’t have to split the data up to three databases. Although this is possible I woul’n’t suggest it, because its hard to maintain and gurantee the integrity of the database through DRIs, you would have to do it with triggers rather than with relations.
HTH, Jens Suessmeyer.
---
http://www.sqlserver2005.de
---
RickShaw888
first of all, there is no prolem upgrading your version of SQL Server to a higher version of SQL Server. The simplest thing for me is to backup and restore the database that are stored on SQL Server Express and restore them on the new server. You could even do a detach / attach with the database files. Even if you are using features like AttachDBFileName you have no problems in higher versions, the function is there, but the behaviour of this features is a bit different than in SQLServerExpress, didn’t try that now to upgrade a database within this feature, but, as I said, the functionality is also in higher versions.
I would suggest after trying the implementation (like you already said) I would suggest using the backup / restore path, even because you don’t have that much data stored in there.
HTH, Jens Suessmeyer.
---
http://www.sqlserver2005.de
---
JohnyM