April 2005 CTP On Virtual PC 2004

Hello, I have installed the SQL Server 2005 april CTP on a Virtual PC running Win2003 standard edition. The Management Studio appears to be corrupted and it says that "no such interface supported". This happens only on the VPC. On the main workstation running XP the Management Studio is fine.

The same issue arises with the ISO i downloaded from MSDN as well as a copy of the DVD given out at a MS developer event in Reading, U.K recently.

Does this ring a bell with anyone? has this surfaced for anyone else?

TIA
BenjyFor a faster response I suggest you post this to the SQL Server Tools General forum.

Dan

Append To File - SQL Server 2005

Their appears to be a bug with the "Append to File" script option that is
available when scripting database objects in SQL Server 2005's SSMS. When I
set the "Append to File" option to false it still appends the script output
to what ever was in the file before. I am scripting all of my stored
procedures in a given database to a separate file for each object. The
first time I generate the files for the procs everything looks fine. When I
script them out a second time to the same location with the "Append to File"
option set to false the scripting engine erroneously appends the new script
output to the end of the existing file.
I saw a similar question in an MSDN posting.
What is the status on this problem.
Thanks!
Chris
Are you on the latest service pack? There were a lot of changes associated
with scripting and such in SP2 but I am not sure if that was one of them or
not. If you are on the latest SP I would delete all the files in that folder
first and post a bug on connect.
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:uVGT1d1tHHA.4844@.TK2MSFTNGP04.phx.gbl...
> Their appears to be a bug with the "Append to File" script option that is
> available when scripting database objects in SQL Server 2005's SSMS. When
> I set the "Append to File" option to false it still appends the script
> output to what ever was in the file before. I am scripting all of my
> stored procedures in a given database to a separate file for each object.
> The first time I generate the files for the procs everything looks fine.
> When I script them out a second time to the same location with the "Append
> to File" option set to false the scripting engine erroneously appends the
> new script output to the end of the existing file.
> I saw a similar question in an MSDN posting.
> What is the status on this problem.
> Thanks!
> Chris
>
|||Hi Chris,
As Andrew said, you may check if SQL Server 2005 SP2 had been installed on
your computer.
You can run SELECT @.@.VERSION to check if the version number is equal to or
larger than 9.00.3042 (initial SP2 version).
I performed a test under my SQL Server 2005 SP2 and everything worked fine.
The file will be replaced if I select "Append to File" as false.
If SQL Server 2005 SP2 had not been installed under your computer, please
install it to see if this issue persists. You can download the latest
service packs from:
Microsoft SQL Server 2005 Service Pack 2
http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-
8f0c-63fa18f26d3a&displaylang=en
Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at
different intervals than intended
http://support.microsoft.com/kb/933508
Hope this helps. If you have any other questions or concerns, please feel
free to let us know. Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

append backups and other mtn plan stuff

Hello:
I am editing a backup maintenance plan. For some reason, the plan is doing
an append backup. I realize that the word "Append" appears in the window.
But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas o
n
how to fix this so that it will do a full backup rather than an Append?
Also, what is the difference between "Target server connection" and "Local
server
connection" when configuring maintenance plans?
Upon reviewing the .bak files in Windows Explorer where the maintenance
plans are placing database backups, I noticed the letter "A" in the Attribut
e
column. Does this mean that the backup job was an "Append" job?
I temporarily disabled my maintenance plans and re-enabled them this AM. In
SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the en
d
of the name of my jobs. Why is that, and is that "bad"?
Thanks!
childofthe1980sHi
"childofthe1980s" wrote:

> Hello:
You don't give the version you are using, have you applied SP2 and the
hotfixes?

> I am editing a backup maintenance plan. For some reason, the plan is doin
g
> an append backup. I realize that the word "Append" appears in the window.
> But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas
on
> how to fix this so that it will do a full backup rather than an Append?
The append/overwrite option is applicable when you choose the file/files to
backup to rather than the directory option.
You can create a maintenance cleanup task to remove unwanted files.

> Also, what is the difference between "Target server connection" and "Local
> server
> connection" when configuring maintenance plans?
A new connection must have been created with this name look at the manage
connections option in the maintenance plan designer to see the properties of
each one.

> Upon reviewing the .bak files in Windows Explorer where the maintenance
> plans are placing database backups, I noticed the letter "A" in the Attrib
ute
> column. Does this mean that the backup job was an "Append" job?
No the A is the archive file attribute.

> I temporarily disabled my maintenance plans and re-enabled them this AM.
In
> SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the
end
> of the name of my jobs. Why is that, and is that "bad"?
Not sure but it will only be part of the job description.

> Thanks!
> childofthe1980s
HTH
John

append backups and other mtn plan stuff

Hello:
I am editing a backup maintenance plan. For some reason, the plan is doing
an append backup. I realize that the word "Append" appears in the window.
But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas on
how to fix this so that it will do a full backup rather than an Append?
Also, what is the difference between "Target server connection" and "Local
server
connection" when configuring maintenance plans?
Upon reviewing the .bak files in Windows Explorer where the maintenance
plans are placing database backups, I noticed the letter "A" in the Attribute
column. Does this mean that the backup job was an "Append" job?
I temporarily disabled my maintenance plans and re-enabled them this AM. In
SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the end
of the name of my jobs. Why is that, and is that "bad"?
Thanks!
childofthe1980sHi
"childofthe1980s" wrote:
> Hello:
You don't give the version you are using, have you applied SP2 and the
hotfixes?
> I am editing a backup maintenance plan. For some reason, the plan is doing
> an append backup. I realize that the word "Append" appears in the window.
> But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas on
> how to fix this so that it will do a full backup rather than an Append?
The append/overwrite option is applicable when you choose the file/files to
backup to rather than the directory option.
You can create a maintenance cleanup task to remove unwanted files.
> Also, what is the difference between "Target server connection" and "Local
> server
> connection" when configuring maintenance plans?
A new connection must have been created with this name look at the manage
connections option in the maintenance plan designer to see the properties of
each one.
> Upon reviewing the .bak files in Windows Explorer where the maintenance
> plans are placing database backups, I noticed the letter "A" in the Attribute
> column. Does this mean that the backup job was an "Append" job?
No the A is the archive file attribute.
> I temporarily disabled my maintenance plans and re-enabled them this AM. In
> SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the end
> of the name of my jobs. Why is that, and is that "bad"?
Not sure but it will only be part of the job description.
> Thanks!
> childofthe1980s
HTH
John

Appears to load 3.0 in emulator instead of 3.1

Here's what I did to a VS2005 Smart Device application.

1. Removed the reference to System.Data.SqlServerCe.dll.

2. Set a reference to C:\Program Files\Microsoft SQL Server Compact Edition\v3.1\SDK\bin\wce500\ System.Data.SqlServerCe.dll.

While it’s loading in the emulator I notice that it appears to still be loading SQLCE3.0 instead of 3.1.

Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce500\ARMV4i\sqlce30.ppc.wce5.armv4i.CAB'

Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce500\ARMV4i\sqlce30.repl.ppc.wce5.armv4i.CAB'

Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce500\ARMV4i\sqlce30.dev.enu.ppc.wce5.armv4i.CAB'

Do I need to set something else?

SQL Server CE 3.1 is a minor upgrade to 3.0. So, you wont see any change in the file names and file versions. If you are having file version as 3.0.5300, then you can be assured that you are using 3.1

Thanks,

Laxmi