Re: Opening large databases in Query Analyzer

I am confused here. Are you using SSMS or SSIS? SSIS standars for SQL
Server Integration Services and helps in Data Transfer Services. I am not
sure if SSIS has any 'edit table' kind of support. If you were indeed
referring to SSMS, I would definitely be interested in how the database is
getting corrupted. So far I have not seen a database getting corrupted for
such simple operations in v3.1 or v3.5. Can you please give more details on
how everything is done to make a database corrupted. Also if possible can
you contact us at our team blog http://blogs.msdn.com/sqlservercompact/ and
choose 'Contact Us' option. So that we really can nail down the issue.

Thanks,
Laxmi


"djlucas" <djlucas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:750C9239-3336-4337-A7CA-24031F0A90C8@xxxxxxxxxxxxxxxx
That hasn't worked out too well for me. I've found that SSIS consistently
corrupts my SQL Server Compact Edition databases when I use it to edit
them.
Simply updating one field in one record damages it.

Thanks anyway.

"Laxmi Narsimha Rao Oruganti [MSFT]" wrote:

Unfortunately, Query Analyzer does not have any menu to take extra
connection string parameters like "Max Database Size" in this case.
Please
copy over the database to desktop and use VS IDE or SSMS to open the
database.

Thanks,
Laxmi

"djlucas" <djlucas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8FB86F4E-8076-47B6-952C-20445DB58D38@xxxxxxxxxxxxxxxx
Is it possible to open a Compact Edition database larger than 128 MB in
SQL
Server Compact Edition Query Analyzer on a handheld device? Whenever I
try
to, I get the error: "The database file is larger than the configured
maximum
database size. This setting takes effect on the first concurrent
database
connection only. [Required Max Database Size (in MB; 0 if
unknown),,,,,]".
I
know how to overcome this in scenarios where I can specify a connection
string, but so far I haven't been able to find any documentation on how
to
overcome this in Query Analyzer on the device.

TIA.





.

Relevant Pages

  • SSIS Error: transport-level error...
    ... Fellow SSIS Users: ... Backup a database. ... The point is that when the package gets to step 5 (after step ... It sounds like a connection error. ...
    (microsoft.public.sqlserver.dts)
  • Re: Opening large databases in Query Analyzer
    ... I meant SSMS. ... I create a database in SQL Server 2000. ... Server Compact Edition (deployed to another version of the same application ...
    (microsoft.public.sqlserver.ce)
  • RE: ODBC Imports of entire Database
    ... Using SSIS it does not give me the option of importing the entire database. ... package so that we can maintain the SQL base and not have to recreate it at ...
    (microsoft.public.sqlserver.dts)
  • RE: ODBC Imports of entire Database
    ... I am using SSIS but it does not allow me to choose by tables. ... option I can bring up is to create a query to bring in the information. ... another SQL database to current Sql 2005. ... ODBC Imports of entire Database ...
    (microsoft.public.sqlserver.dts)
  • RE: ODBC Imports of entire Database
    ... In every database there is a system view called sys.tables. ... When I run the wizard it does not give me the option to copy the entire ... I can schedule SSIS packages but can't get them to just import the data ... Creating Packages Using the SQL Server Import and Export Wizard ...
    (microsoft.public.sqlserver.dts)