Is it possible to import a backup

Had sql database on a dual boot machine... backed up the sql database ...
now put sql on the windows 2003 server... not sure how to import the databas
e to the new sql server... any suggestions or links would be appreciated."Vincent Keller" <anonymous@.discussions.microsoft.com> wrote in message
news:E69894D4-2385-4242-A34A-016B2AA94462@.microsoft.com...
> Had sql database on a dual boot machine... backed up the sql database
... now put sql on the windows 2003 server... not sure how to import the
database to the new sql server... any suggestions or links would be
appreciated.
>
RESTORE DATABASE dbname
FROM wherever
WITH MOVE logical_name TO 'C:\data\whatever.mdf'
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.647 / Virus Database: 414 - Release Date: 29/03/2004sql

Is it possible to get MSDE & SQL Server 2005 Express run on the same machine?

Hi guys,

I'm just wondering if the MSDE & SQL Server 2005 Express can run on the same machine(winxp) without conflicts. Because I need both the reporting services & the publication functionality of replication.

Thanks in advance.

Hi,

yes running both instances on the same system is possible.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Hi,

Yes as said you can run both on same machine without any problem, my machine have both installed on it.

Hemantgiri S. Goswami

|||Thanks guys. I appreciate ur time. :)

Is it Possible to download mails?

Hi,
I have a mail box in one machine. I just want to download all the mails
from that machine to the server which is running SQL Server 2000 and store
them in the database. Is this Possible? If so, let me know how this can be
done efficiently.
I would like to download mails automatically from that machine to the
server whenever the mails arrive.
Regards,
Sevugan.CYOu could use the XP xp_readmail, descriptions are written in the BOl for
that. For further control over the mails you should use another technology,
like something coding on your own in .NET to query the mailbox with Webdav
or something like that.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Sevugan" <Sevugan@.discussions.microsoft.com> schrieb im Newsbeitrag
news:DBD4354E-5A4A-4B1E-8747-CBF0FF913C95@.microsoft.com...
> Hi,
> I have a mail box in one machine. I just want to download all the mails
> from that machine to the server which is running SQL Server 2000 and store
> them in the database. Is this Possible? If so, let me know how this can be
> done efficiently.
> I would like to download mails automatically from that machine to the
> server whenever the mails arrive.
> Regards,
> Sevugan.C|||Hi,
xp_readmail Reads a mail message from the Microsoft? SQL Server? mail
inbox. How do I bring all the mails from the mail client(Microsoft Outlook)
to
sql server mail box. How can I see the mails in the SQL Server mail box.
Can u give me a small examle? This will be very helpful for me.
I am new to SQL Server mails.
Regards,
Sevugan.C
"Jens Sü?meyer" wrote:

> YOu could use the XP xp_readmail, descriptions are written in the BOl for
> that. For further control over the mails you should use another technology
,
> like something coding on your own in .NET to query the mailbox with Webdav
> or something like that.
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Sevugan" <Sevugan@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:DBD4354E-5A4A-4B1E-8747-CBF0FF913C95@.microsoft.com...
>
>|||HI
Well I have an idea but i am not sure about this.
1)I think you can use the mail component and write a code or a script to
retrieve mails from the machine and make connectivity to the SQL server and
store your mails in the database
2) you can also use SQL DMO to connect to SQL Server and store your mails in
the database.
"Sevugan" wrote:

> Hi,
> I have a mail box in one machine. I just want to download all the mails
> from that machine to the server which is running SQL Server 2000 and store
> them in the database. Is this Possible? If so, let me know how this can be
> done efficiently.
> I would like to download mails automatically from that machine to the
> server whenever the mails arrive.
> Regards,
> Sevugan.C|||Maybe this will help !
You can connect on you server with the same credential than SQL Server,
then check mail !
Pollus Brodeur|||I have started a mail session. I used xp_findnextmsg to get the next
message id.
when I executed the below statement.
EXEC xp_readmail '0x04B72100' it keeps on executing. I am not getting any
response from the server. What could be the problem.
How could I resolve this?
Sevugan.C
"Jens Sü?meyer" wrote:

> YOu could use the XP xp_readmail, descriptions are written in the BOl for
> that. For further control over the mails you should use another technology
,
> like something coding on your own in .NET to query the mailbox with Webdav
> or something like that.
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Sevugan" <Sevugan@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:DBD4354E-5A4A-4B1E-8747-CBF0FF913C95@.microsoft.com...
>
>

Is it possbile to define Database server and web server on different machine (Not same phy

Hi All,

Is it possbile to define connection string for web and database server which is running on different machine. Note( Not same LAN).

E.g (My Web Server is in London and Database server in Sydney).

Please can any one help me.??

Thanks in advance...

Dj

They dont need to be on the same LAN, but you'll still need a viable WAN link.

To connect you could use the remote servers IP address with sql credentials.

data source=192.x.x.x;initial catalog=yourDatabase;user id=yourUsername;password=yourPassword;

Is it mandatory to install "SQL server client" to connect to server that has "SQL

Hello,

My database is on the server. I have a vb.net application installed on a client's machine. The problem is I am not able to connect to server from my application.

I have figured out that "SQL server client" is not installed on client's machine.

So is there any settings/utility available using which without installing SQL client I can connect to Server.

Any views/help would be apprecciated.

You do not need to install anything on the client to connect to RS. What error are you recieving?|||

The server machine contains the database and the vb.net application is installed on the client's machine. So my question is in order to connect to the database that resiedes on the server, should client's machine also need "sql server client" or is there any way in which the application can connect to database without "sql client" on client machine.

This has nothing to do with reporting services.

Thanks

|||

I would suggest posting your question here http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=158&SiteID=1

This is a report server forum, so I assumed the question was about RS. Assuming you are using .Net, the answer would still be no, client tools are not required on the client for an application.

Is it mandatory to install "SQL server client" to connect to server that has "

Hello,

My database is on the server. I have a vb.net application installed on a client's machine. The problem is I am not able to connect to server from my application.

I have figured out that "SQL server client" is not installed on client's machine.

So is there any settings/utility available using which without installing SQL client I can connect to Server.

Any views/help would be apprecciated.

You do not need to install anything on the client to connect to RS. What error are you recieving?|||

The server machine contains the database and the vb.net application is installed on the client's machine. So my question is in order to connect to the database that resiedes on the server, should client's machine also need "sql server client" or is there any way in which the application can connect to database without "sql client" on client machine.

This has nothing to do with reporting services.

Thanks

|||

I would suggest posting your question here http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=158&SiteID=1

This is a report server forum, so I assumed the question was about RS. Assuming you are using .Net, the answer would still be no, client tools are not required on the client for an application.

Is Installing SQL05dev and VS05pro on the same machine supported?

Hello,

When SQL05dev is installed a SQL05 version of Visual Studio (SQL05-VS) is also installed (called the “SQL Server Business Intelligence Development Studio”). The SQL05-VS installs files into a “C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE” directory (and other directories - not described here).

When the full version VS05pro is installed it installs/uses files in a “C:\Program Files\Microsoft Visual Studio 8\Common7\IDE” directory.

The number of files in these two directories is different – the directory for VS05pro has (of course) many many more files than the directory for SQL05-VS. On the surface this seems ok since the install of VS05pro should supersede the install of the SQL05-VS and when VS05 is started it utilizes the files from the VS05pro directory and picks up the functions from the SQL05-VS (like SSIS, SSAS, SSRS and such).

But what about the SQL05-VS Common7/IDE directory? In this directory are 64 files that exist in both directores (556 files are not found in the VS05pro Common7/IDE directory). Additionally, there are 10 files that have different versions (mostly having to do with SQL-CE) – newer versions are in the SQL05-VS directory.

I’m confused. Is Microsoft going to support revision changes (Service Packs and such) to both directories? I suppose so, but this introduces possible versioning problems when SQL is updated but VS is not or VS is updated but SQL is not.

I guess I do not understand the rational for not maintaining a single VS directory structure and the problems that this creates. Microsoft is utilizing VS as the IDE for SQL but to not have a really good matching installation layout with the full version of VS is wacky – to say the least. Maybe M$ considers maintaing the versions of 64 files to be unimportant for the correct functioning of VS?

Is Installing SQL05dev and VS05pro on the same machine supported?

MikeC

Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.

SQL installs what we call the Premier Partner Edition, which is just the basic IDE with no langauges. SQL then installs its own packages on top of the IDE.

The additional files are SQL specific. The Premier Partner Edition and any VS flavor will install to one location. If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want.

That way, you only have one version of the file, its serviced in one place, and is properly ref counted.

|||

QuanT,

You said, "Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.”

If this is the case, then I would like to see Microsoft fix the problems with SQL05 when VS and SQL05 are installed on the same machine – *but not to the C: volume*. That is - installing full VS05 (without SQL Express) and SQL05 to a non-C: volume on a freshly formatted/installed version of Windows 2003R2.

You said “If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want."

It does not matter which you install first, installing VS to a non-C: volume after SQL is installed to a non-C: volume broke SSIS and the copy db wizard (I did not do any checking beyond these show-stoppers…)

Installing VS first (to a non-C: volume) allows the SQL install to install more components to a non-C: volume, but the problems still arise. Installing in this order should also be supported.

Installing VS to C: and SQL to E: works, but then RS has issues...

It appears that very little SQL05 installation testing was done to anything other than a C: volume - when VS05 is also installed on the same machine - as would be the case on development boxes. On a production db server it is unlikly that I would install the full VS, but who knows, it might be necessary, and should be possible without worry that SQL05 will be broken.

MikeC

Error from create SSIS package (save to server):
===================================

No description found (Microsoft Visual Studio)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String serverUserName, String serverPassword) at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package) at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)

===================================

Error from copy db wizard:
===================================

No description found (Copy Database Wizard)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword) at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()

===================================

|||

Thanks for the feedback Mike.

I'm moving this to the SQL Setup alias to get comments from the SQL Team.

|||

Mike,

is your issue resolved? I would like to know what the resolution was if it has been resolved. Iam encountering the same issue now.

My setup is:

1. Installed SQL2000 (default instance)

2. Installed SQL2005 (named instance)

All on C:

I was able to save SSIS packages to the DB until recently using "Save Copy of <pkg> As".

Now I'm encountering the above error (No decription found etc..). I don't even remember anymore if I specified the <machine name> OR <machine name>\<Instance Name> for the "Server" when I had it working.

But I tried with both and I get different errors:

<machine name>\<Instance Name> : No decription found etc.

<machine name> :

======================
The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed.
(Microsoft Visual Studio)

=======================

For "Protection Level", I have tried different options, but it doesn't seem to matter.

Another thing is that I suspect this may have started happening after I was trying to install VS05 (other components) on top of the default version that was installed along with SQL05. I didn't go ahead with the VS install and canceled it half way through the initial install setup.

Any inputs are appreciated.

Thanks.

|||

Sql_Rv,

I have an open support call with M$ for the last week or so about the "can't save package" problem. This problem with saving packages absolutely has something to do with installing VS05 on the same machine that has SQL05 installed. Works without VS05, fails with VS05 installed.

To fix your installation (without a complete wipe of the house-of-cards that is Windows ), I suggest installing VS05 all the way! Then run the VS05 uninstall. This is the only way to get the VS05 install/uninstall program to run and remove the all the bits of VS05 that M$ stashes all over the place - especially the registry. I would hope that an aborted VS05 install would back-out any changes, but given the somewhat buggy state of Win03r2, MMCv3, VS05 and SQL05 tools… Really, I don’t think M$ has it altogether any more, the testers likely do not have initiative to try anything slightly out of line…

Lets see - ALL third party and M$ products like ISA04 that use MMC cause the new MMC v3 to crash on WinR2 - really - what kind of testing is M$ doing? I suppose we are doing the testing for them...

It would be nice if M$ (and other M$ app mfg) would wake up and see the simplicity of installing all executables of an application in ONE directory tree, and have a minimal registry footprint. A manifest of files would be nice also - but no, we get this horrific splat of install logs that lists what files were installed - and the number of registry entries that get added by SQL05 is obscene. Really, it is too much to ask for list of files and their versions needed to maintain a SQL05 installation? Tracking revisions must be a fuzzy concept at M$...

Anyway - M$ support is slow on the testing and the wonderfully informative error message "no description found" goes a long way in pointing to the problem - not.

Question: What version of Windows are you running? Is it a domain controller? Are SQL services running with a domain account?

MikeC

|||

Mike,

Thanks for taking the time to respond. I appreciate it.

This is on my dev box which is running XP Pro. No, it is not a domain controller. Yes, the services are running with a domain account that has admin privileges on this box.

btw, to get around this problem, I tried saving it from a different machine and it worked. This is what I did:

box1\2K5 - Unable to save the pkg to this DB from box1.

box2 - Has a 2K5 instance too. I used this to save it to box1\2K5 by doing a save as and specifying box1\2K5 as the SQLServer name - and it saved successfully.

Thanks,

RV

|||

I have the same problem.

MS WinXP Pro sp2 (latest patches as of 9.26.2006)

SQL Server 2005

VS2005

error:TITLE: SQL Server Import and Export Wizard The operation could not be completed. ADDITIONAL INFORMATION: The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed. BUTTONS: OK

The error is generated when I try to save the SISS package to the SQL server instance mentioned above.

I was able to save the SISS package using the filesystem option.

Is Installing SQL05dev and VS05pro on the same machine supported?

Hello,

When SQL05dev is installed a SQL05 version of Visual Studio (SQL05-VS) is also installed (called the “SQL Server Business Intelligence Development Studio”). The SQL05-VS installs files into a “C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE” directory (and other directories - not described here).

When the full version VS05pro is installed it installs/uses files in a “C:\Program Files\Microsoft Visual Studio 8\Common7\IDE” directory.

The number of files in these two directories is different – the directory for VS05pro has (of course) many many more files than the directory for SQL05-VS. On the surface this seems ok since the install of VS05pro should supersede the install of the SQL05-VS and when VS05 is started it utilizes the files from the VS05pro directory and picks up the functions from the SQL05-VS (like SSIS, SSAS, SSRS and such).

But what about the SQL05-VS Common7/IDE directory? In this directory are 64 files that exist in both directores (556 files are not found in the VS05pro Common7/IDE directory). Additionally, there are 10 files that have different versions (mostly having to do with SQL-CE) – newer versions are in the SQL05-VS directory.

I’m confused. Is Microsoft going to support revision changes (Service Packs and such) to both directories? I suppose so, but this introduces possible versioning problems when SQL is updated but VS is not or VS is updated but SQL is not.

I guess I do not understand the rational for not maintaining a single VS directory structure and the problems that this creates. Microsoft is utilizing VS as the IDE for SQL but to not have a really good matching installation layout with the full version of VS is wacky – to say the least. Maybe M$ considers maintaing the versions of 64 files to be unimportant for the correct functioning of VS?

Is Installing SQL05dev and VS05pro on the same machine supported?

MikeC

Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.

SQL installs what we call the Premier Partner Edition, which is just the basic IDE with no langauges. SQL then installs its own packages on top of the IDE.

The additional files are SQL specific. The Premier Partner Edition and any VS flavor will install to one location. If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want.

That way, you only have one version of the file, its serviced in one place, and is properly ref counted.

|||

QuanT,

You said, "Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.”

If this is the case, then I would like to see Microsoft fix the problems with SQL05 when VS and SQL05 are installed on the same machine – *but not to the C: volume*. That is - installing full VS05 (without SQL Express) and SQL05 to a non-C: volume on a freshly formatted/installed version of Windows 2003R2.

You said “If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want."

It does not matter which you install first, installing VS to a non-C: volume after SQL is installed to a non-C: volume broke SSIS and the copy db wizard (I did not do any checking beyond these show-stoppers…)

Installing VS first (to a non-C: volume) allows the SQL install to install more components to a non-C: volume, but the problems still arise. Installing in this order should also be supported.

Installing VS to C: and SQL to E: works, but then RS has issues...

It appears that very little SQL05 installation testing was done to anything other than a C: volume - when VS05 is also installed on the same machine - as would be the case on development boxes. On a production db server it is unlikly that I would install the full VS, but who knows, it might be necessary, and should be possible without worry that SQL05 will be broken.

MikeC

Error from create SSIS package (save to server):
===================================

No description found (Microsoft Visual Studio)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String serverUserName, String serverPassword) at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package) at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)

===================================

Error from copy db wizard:
===================================

No description found (Copy Database Wizard)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword) at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()

===================================

|||

Thanks for the feedback Mike.

I'm moving this to the SQL Setup alias to get comments from the SQL Team.

|||

Mike,

is your issue resolved? I would like to know what the resolution was if it has been resolved. Iam encountering the same issue now.

My setup is:

1. Installed SQL2000 (default instance)

2. Installed SQL2005 (named instance)

All on C:

I was able to save SSIS packages to the DB until recently using "Save Copy of <pkg> As".

Now I'm encountering the above error (No decription found etc..). I don't even remember anymore if I specified the <machine name> OR <machine name>\<Instance Name> for the "Server" when I had it working.

But I tried with both and I get different errors:

<machine name>\<Instance Name> : No decription found etc.

<machine name> :

======================
The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed.
(Microsoft Visual Studio)

=======================

For "Protection Level", I have tried different options, but it doesn't seem to matter.

Another thing is that I suspect this may have started happening after I was trying to install VS05 (other components) on top of the default version that was installed along with SQL05. I didn't go ahead with the VS install and canceled it half way through the initial install setup.

Any inputs are appreciated.

Thanks.

|||

Sql_Rv,

I have an open support call with M$ for the last week or so about the "can't save package" problem. This problem with saving packages absolutely has something to do with installing VS05 on the same machine that has SQL05 installed. Works without VS05, fails with VS05 installed.

To fix your installation (without a complete wipe of the house-of-cards that is Windows ), I suggest installing VS05 all the way! Then run the VS05 uninstall. This is the only way to get the VS05 install/uninstall program to run and remove the all the bits of VS05 that M$ stashes all over the place - especially the registry. I would hope that an aborted VS05 install would back-out any changes, but given the somewhat buggy state of Win03r2, MMCv3, VS05 and SQL05 tools… Really, I don’t think M$ has it altogether any more, the testers likely do not have initiative to try anything slightly out of line…

Lets see - ALL third party and M$ products like ISA04 that use MMC cause the new MMC v3 to crash on WinR2 - really - what kind of testing is M$ doing? I suppose we are doing the testing for them...

It would be nice if M$ (and other M$ app mfg) would wake up and see the simplicity of installing all executables of an application in ONE directory tree, and have a minimal registry footprint. A manifest of files would be nice also - but no, we get this horrific splat of install logs that lists what files were installed - and the number of registry entries that get added by SQL05 is obscene. Really, it is too much to ask for list of files and their versions needed to maintain a SQL05 installation? Tracking revisions must be a fuzzy concept at M$...

Anyway - M$ support is slow on the testing and the wonderfully informative error message "no description found" goes a long way in pointing to the problem - not.

Question: What version of Windows are you running? Is it a domain controller? Are SQL services running with a domain account?

MikeC

|||

Mike,

Thanks for taking the time to respond. I appreciate it.

This is on my dev box which is running XP Pro. No, it is not a domain controller. Yes, the services are running with a domain account that has admin privileges on this box.

btw, to get around this problem, I tried saving it from a different machine and it worked. This is what I did:

box1\2K5 - Unable to save the pkg to this DB from box1.

box2 - Has a 2K5 instance too. I used this to save it to box1\2K5 by doing a save as and specifying box1\2K5 as the SQLServer name - and it saved successfully.

Thanks,

RV

|||

I have the same problem.

MS WinXP Pro sp2 (latest patches as of 9.26.2006)

SQL Server 2005

VS2005

error:TITLE: SQL Server Import and Export Wizard The operation could not be completed. ADDITIONAL INFORMATION: The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed. BUTTONS: OK

The error is generated when I try to save the SISS package to the SQL server instance mentioned above.

I was able to save the SISS package using the filesystem option.

Is Installing SQL05dev and VS05pro on the same machine supported?

Hello,

When SQL05dev is installed a SQL05 version of Visual Studio (SQL05-VS) is also installed (called the “SQL Server Business Intelligence Development Studio”). The SQL05-VS installs files into a “C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE” directory (and other directories - not described here).

When the full version VS05pro is installed it installs/uses files in a “C:\Program Files\Microsoft Visual Studio 8\Common7\IDE” directory.

The number of files in these two directories is different – the directory for VS05pro has (of course) many many more files than the directory for SQL05-VS. On the surface this seems ok since the install of VS05pro should supersede the install of the SQL05-VS and when VS05 is started it utilizes the files from the VS05pro directory and picks up the functions from the SQL05-VS (like SSIS, SSAS, SSRS and such).

But what about the SQL05-VS Common7/IDE directory? In this directory are 64 files that exist in both directores (556 files are not found in the VS05pro Common7/IDE directory). Additionally, there are 10 files that have different versions (mostly having to do with SQL-CE) – newer versions are in the SQL05-VS directory.

I’m confused. Is Microsoft going to support revision changes (Service Packs and such) to both directories? I suppose so, but this introduces possible versioning problems when SQL is updated but VS is not or VS is updated but SQL is not.

I guess I do not understand the rational for not maintaining a single VS directory structure and the problems that this creates. Microsoft is utilizing VS as the IDE for SQL but to not have a really good matching installation layout with the full version of VS is wacky – to say the least. Maybe M$ considers maintaing the versions of 64 files to be unimportant for the correct functioning of VS?

Is Installing SQL05dev and VS05pro on the same machine supported?

MikeC

Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.

SQL installs what we call the Premier Partner Edition, which is just the basic IDE with no langauges. SQL then installs its own packages on top of the IDE.

The additional files are SQL specific. The Premier Partner Edition and any VS flavor will install to one location. If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want.

That way, you only have one version of the file, its serviced in one place, and is properly ref counted.

|||

QuanT,

You said, "Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.”

If this is the case, then I would like to see Microsoft fix the problems with SQL05 when VS and SQL05 are installed on the same machine – *but not to the C: volume*. That is - installing full VS05 (without SQL Express) and SQL05 to a non-C: volume on a freshly formatted/installed version of Windows 2003R2.

You said “If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want."

It does not matter which you install first, installing VS to a non-C: volume after SQL is installed to a non-C: volume broke SSIS and the copy db wizard (I did not do any checking beyond these show-stoppers…)

Installing VS first (to a non-C: volume) allows the SQL install to install more components to a non-C: volume, but the problems still arise. Installing in this order should also be supported.

Installing VS to C: and SQL to E: works, but then RS has issues...

It appears that very little SQL05 installation testing was done to anything other than a C: volume - when VS05 is also installed on the same machine - as would be the case on development boxes. On a production db server it is unlikly that I would install the full VS, but who knows, it might be necessary, and should be possible without worry that SQL05 will be broken.

MikeC

Error from create SSIS package (save to server):
===================================

No description found (Microsoft Visual Studio)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String serverUserName, String serverPassword) at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package) at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)

===================================

Error from copy db wizard:
===================================

No description found (Copy Database Wizard)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword) at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()

===================================

|||

Thanks for the feedback Mike.

I'm moving this to the SQL Setup alias to get comments from the SQL Team.

|||

Mike,

is your issue resolved? I would like to know what the resolution was if it has been resolved. Iam encountering the same issue now.

My setup is:

1. Installed SQL2000 (default instance)

2. Installed SQL2005 (named instance)

All on C:

I was able to save SSIS packages to the DB until recently using "Save Copy of <pkg> As".

Now I'm encountering the above error (No decription found etc..). I don't even remember anymore if I specified the <machine name> OR <machine name>\<Instance Name> for the "Server" when I had it working.

But I tried with both and I get different errors:

<machine name>\<Instance Name> : No decription found etc.

<machine name> :

======================
The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed.
(Microsoft Visual Studio)

=======================

For "Protection Level", I have tried different options, but it doesn't seem to matter.

Another thing is that I suspect this may have started happening after I was trying to install VS05 (other components) on top of the default version that was installed along with SQL05. I didn't go ahead with the VS install and canceled it half way through the initial install setup.

Any inputs are appreciated.

Thanks.

|||

Sql_Rv,

I have an open support call with M$ for the last week or so about the "can't save package" problem. This problem with saving packages absolutely has something to do with installing VS05 on the same machine that has SQL05 installed. Works without VS05, fails with VS05 installed.

To fix your installation (without a complete wipe of the house-of-cards that is Windows ), I suggest installing VS05 all the way! Then run the VS05 uninstall. This is the only way to get the VS05 install/uninstall program to run and remove the all the bits of VS05 that M$ stashes all over the place - especially the registry. I would hope that an aborted VS05 install would back-out any changes, but given the somewhat buggy state of Win03r2, MMCv3, VS05 and SQL05 tools… Really, I don’t think M$ has it altogether any more, the testers likely do not have initiative to try anything slightly out of line…

Lets see - ALL third party and M$ products like ISA04 that use MMC cause the new MMC v3 to crash on WinR2 - really - what kind of testing is M$ doing? I suppose we are doing the testing for them...

It would be nice if M$ (and other M$ app mfg) would wake up and see the simplicity of installing all executables of an application in ONE directory tree, and have a minimal registry footprint. A manifest of files would be nice also - but no, we get this horrific splat of install logs that lists what files were installed - and the number of registry entries that get added by SQL05 is obscene. Really, it is too much to ask for list of files and their versions needed to maintain a SQL05 installation? Tracking revisions must be a fuzzy concept at M$...

Anyway - M$ support is slow on the testing and the wonderfully informative error message "no description found" goes a long way in pointing to the problem - not.

Question: What version of Windows are you running? Is it a domain controller? Are SQL services running with a domain account?

MikeC

|||

Mike,

Thanks for taking the time to respond. I appreciate it.

This is on my dev box which is running XP Pro. No, it is not a domain controller. Yes, the services are running with a domain account that has admin privileges on this box.

btw, to get around this problem, I tried saving it from a different machine and it worked. This is what I did:

box1\2K5 - Unable to save the pkg to this DB from box1.

box2 - Has a 2K5 instance too. I used this to save it to box1\2K5 by doing a save as and specifying box1\2K5 as the SQLServer name - and it saved successfully.

Thanks,

RV

|||

I have the same problem.

MS WinXP Pro sp2 (latest patches as of 9.26.2006)

SQL Server 2005

VS2005

error:TITLE: SQL Server Import and Export Wizard The operation could not be completed. ADDITIONAL INFORMATION: The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed. BUTTONS: OK

The error is generated when I try to save the SISS package to the SQL server instance mentioned above.

I was able to save the SISS package using the filesystem option.