Is the June CTP compatible with Visual Studio Beta 2

Different versions of .Net 2.0, maybe other files...

It is compatible, there are instructions with the June CTP as what you need to do but basically uninstall .Net then install SQL June CTP.

-Euansql

is sql 7.0 scheduled to be retired

In e-Week (Dec 15, 2003 pg 8) an article mentioned that Windows 98, sql
server 7.0 and a number of versions of office 2000 are scheduled to be
retired by Dec 23 as part of the agreement with Sun over the Java lawsuit.
Can anyone point me to a press release or list of products that are
scheduled to be retired as part of this agreement?> In e-Week (Dec 15, 2003 pg 8) an article mentioned that Windows 98, sql
> server 7.0 and a number of versions of office 2000 are scheduled to be
> retired by Dec 23 as part of the agreement with Sun over the Java lawsuit.
I believe there are certain products that will no longer be available, e.g.
to download from the MSDN Subscriber Downloads site. But that does not mean
the product is "retired" depending on how you define "retired"; it will
still follow its product life cycle. For example, according to
http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeSrvr
SQL Server 7.0 will "die," in different senses, on 12/31/2005, and
12/31/2007.
Here is a snippet from an announcement to MSDN subscribers, which highlights
the other products which will no longer be available directly:
> Due to a settlement agreement reached in January 2001, the following
> products are being phased out and will no longer available to customers
> through MSDN Subscriber Downloads or other channels at Microsoft. These
> products will be removed from MSDN Subscriber Downloads as of December
15th,
> 2003.
> Office XP Developer
> Visio 2000
> BackOffice Server 2000
> Office 2000 Developer
> Office 2000 Tools
> Office 2000 Multilingual
> Office 2000 Premium SR-1
> Office 2000 Service Pack 2
> Outlook 2000
> Project 2000
> SQL Server 7
> SQL Server 7 Service Pack 3
> Embedded Visual Tools 3.0
> Visual Studio 6 MSDE
> IE 5.5
> MapPoint 2002
> Visual Studio 6.0 SP3 and SP5
> Windows 98
> Windows 98 Y2K
> Windows 98 Resource Kit
> Windows 98 SP1 (all win98 except SE)
> Windows NT 4.0
> ISA Server 2000
> Visual Basic for (Alpha Systems)
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

Is Point in time recovery the same in all versions of SQL Server 2005?

Hello everyone,

Our company will be using SQL Server 2005 Enterprise on our main server and either SQL Server Express or workgroup for our disconnected users. Our users will be syncing their local database with the main server using replication.

The question that was brought up is about the PIT recovery in SQL Server Express and workgroup. Please correct me if I am wrong. From what I understood, Point in time recovery is the same in both the Express and the WG editions. The database restores the full backup then incremental backups (if any) then the transactional logs. The only exception is that WG edition supports log shipping. Am I right?

I also watch one of the sql server 2005 webcasts series that talked about the online piecemeal recovery. From my understanding, online restore feature is an enterprise edition feature which allows the server to restore backup and logs, server goes online then roll back uncommited transactions. My question is if we are to use Express or WG, can we restore filegroups or pages (offline)? In another word, can we restore specific tables to point in time instead of the whole database.

Thanks a lot.

Point in time recovery is the same in all versions of sql2005.

Minor point: we do not support incremental backup. I'm sure you are refering to differential backups.

As far as I know, log shipping is only supported by the enterprise edition. That refers to our automatic tools to setup and maintain the log shipping.

The underlying engine supports log shipping in all versions, but you'd have to "roll your own" automated procedures.

Regarding piecemeal restore: we only support online restore in the enterprise edition. File/fileGroup/Page restore is offline in all other editions.

It is not possible to restore filegroups (and the tables they contain) to different points in time. The only way to perform a table restore:

- perform a partial restore to a working database. Just restore the filegroups containing the tables of interest.

- then export the tables (or sets of rows) of interest and merge them back into your online database. It is possible that referential integrity constraints will require more work than just inserting the rows of interest (you may have to delete/update other tables to maintain consistency).

Hope that helps.