migrating from crystal report 8.5 to 10.0 using vb .

I am working in migrating my cr application to 10th ver from the existing 8.5 where we have to explicitly make a query in query builder and then attach it. I was using dsn in ms odbc for oracle driver to connect the DB. Now in 10.0 i have removed the query file created using 8.5 query builder and trying to write directly to command editor. the report as stand alone is working fine. but when i try to generate the pdf using my vb application then on .export option it is giving error as "Logon failed.
Details: 01S00:[Microsoft][ODBC driver for Oracle]Invalid connection string attribute". i think the problem might be with cddb_oracle.dll or crdb_oracle.dll file as i am using a evaluation version of crystal report 10. as input to dsn i am providing
1.dsn
2.usid
3.database
4.password
what else is missing . plz help....The next is code I use in VB6 to display in CRViewer10 a CR10 report that read data thru ODBC

Set CRReport = CRApplication.OpenReport("Report.rpt", 1)
For MEnt2 = 1 To CRReport.Database.Tables.Count
Set CRTabla = CRReport.Database.Tables(MEnt2)
Set CRConProp = CRTabla.ConnectionProperties("Provider")
CRConProp.value = "MSDASQL"
Set CRConProp = CRTabla.ConnectionProperties("Data Source")
CRConProp.value = "DSNname"
Set CRConProp = CRTabla.ConnectionProperties("Initial Catalog")
CRConProp.value = "Datapath"
Set CRConProp = CRTabla.ConnectionProperties("User ID")
CRConProp.value = ""
Set CRConProp = CRTabla.ConnectionProperties("Locale Identifier")
CRConProp.value = "2058"
Set CRConProp = CRTabla.ConnectionProperties("OLE DB Services")
CRConProp.value = "-5"
Next MEnt2

frmReport.Show vbModal

Migrating form access to SQL

I am facing problems in migrating my application from Access to SQL.
Few of the fuctions like CBDATE (userdefined functions) are not working.
Please let me know how to overcome this problem.
ThanksHi Manas. I am unaware of a function within Access called CBDATE...is it something you designed and coded (in VBA possibly)? There are a many things you can do in SQL to get the same functionality, but could you post an example code snipet for what that function does?|||

Note he stated it was a user defined function.

You will have to migrate that function into SQL, along with the rest of the database.

|||Did you define the function in the database itself (can you do that in Access?), or in the front end?|||In access you can write functions in VBA that can be called from queries...I'm assuming that's what was being done...|||Ah yes, you are most probably correct. In that case, I presume he will have to write an analagous function in SQL to correct that, with the same name and return type?|||Yeah, I would assume that to be the case...problem would be if the VBA function is doing anything you can't do in T-SQL...then it would be more difficult...

MIgrating DTS packages of SQL 2000 to SQL 2005

Hello All,

I am working on a migration project of my database(lets name it DB1), from SQL 2000 to SQL 2005. I have some DTS packages in my SQL 2000 database which also needs to be migrated to SSIS. These DTS packages currently interacts with other database(lets name it DB2) which is also in SQL 2000 and which does the data transmission. The real issue is that the other database(DB2) also has some DTS packages which also communicates with DB1 (the db to be upgraded) and so when i migrate my DB1 to SQL 2005, i will have to change my DB2 packages also (although the change will be minor). Now considering that in future I might also migrate my DB2 to SQL 2005 I wanted to know what will be the right approach to follow. One is to modify the DTS packages of DB2 to accmodate the change in connection and the other is to migrate the DTS packages of DB2 also to SSIS.

Can anyone help me with this one.

Thanks in Advance

Mitesh

Hi Mitesh,

Something to consider: You can migrate a SQL Server 2000 database (DB1) to SQL Server 2005 and continue to run it at a SQL Server 2000 Compatibility Level. The implication is you may be able to continue connecting to DB1 from the DB2 DTS packages as you do now - it will just be on a different instance of SQL Server. I'm not sure what your DB2 DTS packages do exactly, so it's difficult to make that statement with more confidence.

There's also an Execute DTS 2000 Package Task available in SSIS. You can execute your existing DTS packages from SSIS. I've used this (and the aforementioned Compatibility Level) before as part of a migration plan from SQL Server 2000 to SQL Server 2005. It's nice because I don't have to get everything converted before starting to use the new database engine.

Regarding migrating between DTS and SSIS: that's a tough one. I teach ETL with SSIS for Solid Quality Learning. One of the things I share with students is the fact that SSIS is not the new version of DTS - it's a replacement. Microsoft did not start with DTS and modify it - they rewrote the entire application. This has some bearing on how easy it is to migrate from DTS. I've seen very simple DTS packages migrate easily, but that's about it.

There's so much new under the hood, you will most likely want to rebuild - and perhaps redesign - your packages in SSIS to take advantage of some of the stellar performance gains.

Hope this helps,

Andy

|||

Hey Andy,

Thanks for the reply will surely consider your suggestion. Just one more thing, when i use the Execute DTS 2000 Package task of SSIS i will have to change my connection as my database is migrated to SQL 2005 on another server. Correct me if i am wrong

|||

Hi Mitesh,

Yes sir - you will have to change your connection to target another database, server, or both.

Hope this helps,

Andy

Migrating AS/400 DB2 to SQL Server

The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving years
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same as
a tables and logicals look to be the same as views.
Thx
You're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It was
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:

> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 on
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving years
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should know
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in the
> 400. Each of those contain files and logicals. Files look to be the same as
> a tables and logicals look to be the same as views.
> Thx

Migrating AS/400 DB2 to SQL Server

The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving years
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same as
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It was
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:
> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 on
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving years
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should know
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in the
> 400. Each of those contain files and logicals. Files look to be the same as
> a tables and logicals look to be the same as views.
> Thx

Migrating AS/400 DB2 to SQL Server

The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving year
s
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same a
s
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It wa
s
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:

> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 o
n
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving ye
ars
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should kn
ow
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in t
he
> 400. Each of those contain files and logicals. Files look to be the same
as
> a tables and logicals look to be the same as views.
> Thx

migrate mdf file to sql server 2005

hello

i am working on a mdf file on sql server express 2005 and i would like to migrate the content to sql server 2005.

How can i do it ?the reason why i want to do this is because i want to work on the same database from different project|||I havent used Express but you could try copying the mdf file into the data folder of SQL Server and "attaching" the database.|||Yup, it's that simple. Copy, and attach.

Migrate Access2000 to SQL2000 database

I am working on new project that migration Access database and its ASP.NET
application to SQL2000 database. Please give me the guide and strategy how to
do it from beginning to the end.
Thank you very much and Happy New Year.
Kevin,
Microsoft suggests that you use the Upsizing wizard in Access 2k to
accomplish this. I have posted a url for you below that has a link to a very
detailed white paper that explains how to use this wizard.
I hope this helps.
http://support.microsoft.com/default...roduct=acc2000
|||That request is beyond the scope of a simple newsgroup question.
Migrating the data shouldn't be too difficult -- for best results,
create the schema and database objects in SQLS and migrate the data
using DTS or the Access upsizing wizard. As far as ASP.NET goes, take
a look at the ASP.NET security best-practices whitepaper,
http://www.microsoft.com/downloads/r...leaseID=44047. That
will get you started about thinking of your overall application and
security architecture. Also visit the ASP.NETand SQLS developer
centers at http://msdn.microsoft.com/asp.net/ and
http://msdn.microsoft.com/sql/, respectively.
--Mary
On Wed, 29 Dec 2004 07:50:25 -0800, "Kevin"
<Kevin@.discussions.microsoft.com> wrote:

>I am working on new project that migration Access database and its ASP.NET
>application to SQL2000 database. Please give me the guide and strategy how to
> do it from beginning to the end.
>Thank you very much and Happy New Year.
|||Thanks Brian.
Do you know which one is better between Upsizing or DTS approach?
"Brian Brown" wrote:

> Kevin,
> Microsoft suggests that you use the Upsizing wizard in Access 2k to
> accomplish this. I have posted a url for you below that has a link to a very
> detailed white paper that explains how to use this wizard.
> I hope this helps.
> --
> http://support.microsoft.com/default...roduct=acc2000
|||Thanks Mary.
"Mary Chipman" wrote:

> That request is beyond the scope of a simple newsgroup question.
> Migrating the data shouldn't be too difficult -- for best results,
> create the schema and database objects in SQLS and migrate the data
> using DTS or the Access upsizing wizard. As far as ASP.NET goes, take
> a look at the ASP.NET security best-practices whitepaper,
> http://www.microsoft.com/downloads/r...leaseID=44047. That
> will get you started about thinking of your overall application and
> security architecture. Also visit the ASP.NETand SQLS developer
> centers at http://msdn.microsoft.com/asp.net/ and
> http://msdn.microsoft.com/sql/, respectively.
> --Mary
> On Wed, 29 Dec 2004 07:50:25 -0800, "Kevin"
> <Kevin@.discussions.microsoft.com> wrote:
>
>

Migrate Access2000 to SQL2000 database

I am working on new project that migration Access database and its ASP.NET
application to SQL2000 database. Please give me the guide and strategy how to
do it from beginning to the end.
Thank you very much and Happy New Year.Kevin,
Microsoft suggests that you use the Upsizing wizard in Access 2k to
accomplish this. I have posted a url for you below that has a link to a very
detailed white paper that explains how to use this wizard.
I hope this helps.
--
http://support.microsoft.com/default.aspx?kbid=241743&product=acc2000|||That request is beyond the scope of a simple newsgroup question.
Migrating the data shouldn't be too difficult -- for best results,
create the schema and database objects in SQLS and migrate the data
using DTS or the Access upsizing wizard. As far as ASP.NET goes, take
a look at the ASP.NET security best-practices whitepaper,
http://www.microsoft.com/downloads/release.asp?ReleaseID=44047. That
will get you started about thinking of your overall application and
security architecture. Also visit the ASP.NETand SQLS developer
centers at http://msdn.microsoft.com/asp.net/ and
http://msdn.microsoft.com/sql/, respectively.
--Mary
On Wed, 29 Dec 2004 07:50:25 -0800, "Kevin"
<Kevin@.discussions.microsoft.com> wrote:
>I am working on new project that migration Access database and its ASP.NET
>application to SQL2000 database. Please give me the guide and strategy how to
> do it from beginning to the end.
>Thank you very much and Happy New Year.|||Thanks Brian.
Do you know which one is better between Upsizing or DTS approach?
"Brian Brown" wrote:
> Kevin,
> Microsoft suggests that you use the Upsizing wizard in Access 2k to
> accomplish this. I have posted a url for you below that has a link to a very
> detailed white paper that explains how to use this wizard.
> I hope this helps.
> --
> http://support.microsoft.com/default.aspx?kbid=241743&product=acc2000|||Thanks Mary.
"Mary Chipman" wrote:
> That request is beyond the scope of a simple newsgroup question.
> Migrating the data shouldn't be too difficult -- for best results,
> create the schema and database objects in SQLS and migrate the data
> using DTS or the Access upsizing wizard. As far as ASP.NET goes, take
> a look at the ASP.NET security best-practices whitepaper,
> http://www.microsoft.com/downloads/release.asp?ReleaseID=44047. That
> will get you started about thinking of your overall application and
> security architecture. Also visit the ASP.NETand SQLS developer
> centers at http://msdn.microsoft.com/asp.net/ and
> http://msdn.microsoft.com/sql/, respectively.
> --Mary
> On Wed, 29 Dec 2004 07:50:25 -0800, "Kevin"
> <Kevin@.discussions.microsoft.com> wrote:
> >I am working on new project that migration Access database and its ASP.NET
> >application to SQL2000 database. Please give me the guide and strategy how to
> > do it from beginning to the end.
> >Thank you very much and Happy New Year.
>

Migrate Access2000 to SQL2000 database

I am working on new project that migration Access database and its ASP.NET
application to SQL2000 database. Please give me the guide and strategy how t
o
do it from beginning to the end.
Thank you very much and Happy New Year.Kevin,
Microsoft suggests that you use the Upsizing wizard in Access 2k to
accomplish this. I have posted a url for you below that has a link to a ver
y
detailed white paper that explains how to use this wizard.
I hope this helps.
http://support.microsoft.com/defaul...product=acc2000|||That request is beyond the scope of a simple newsgroup question.
Migrating the data shouldn't be too difficult -- for best results,
create the schema and database objects in SQLS and migrate the data
using DTS or the Access upsizing wizard. As far as ASP.NET goes, take
a look at the ASP.NET security best-practices whitepaper,
http://www.microsoft.com/downloads/...eleaseID=44047. That
will get you started about thinking of your overall application and
security architecture. Also visit the ASP.NETand SQLS developer
centers at http://msdn.microsoft.com/asp.net/ and
http://msdn.microsoft.com/sql/, respectively.
--Mary
On Wed, 29 Dec 2004 07:50:25 -0800, "Kevin"
<Kevin@.discussions.microsoft.com> wrote:

>I am working on new project that migration Access database and its ASP.NET
>application to SQL2000 database. Please give me the guide and strategy how
to
> do it from beginning to the end.
>Thank you very much and Happy New Year.|||Thanks Brian.
Do you know which one is better between Upsizing or DTS approach?
"Brian Brown" wrote:

> Kevin,
> Microsoft suggests that you use the Upsizing wizard in Access 2k to
> accomplish this. I have posted a url for you below that has a link to a v
ery
> detailed white paper that explains how to use this wizard.
> I hope this helps.
> --
> http://support.microsoft.com/defaul...product=acc2000|||Thanks Mary.
"Mary Chipman" wrote:

> That request is beyond the scope of a simple newsgroup question.
> Migrating the data shouldn't be too difficult -- for best results,
> create the schema and database objects in SQLS and migrate the data
> using DTS or the Access upsizing wizard. As far as ASP.NET goes, take
> a look at the ASP.NET security best-practices whitepaper,
> http://www.microsoft.com/downloads/...eleaseID=44047. That
> will get you started about thinking of your overall application and
> security architecture. Also visit the ASP.NETand SQLS developer
> centers at http://msdn.microsoft.com/asp.net/ and
> http://msdn.microsoft.com/sql/, respectively.
> --Mary
> On Wed, 29 Dec 2004 07:50:25 -0800, "Kevin"
> <Kevin@.discussions.microsoft.com> wrote:
>
>

MID function in SQL?

My brain is not working this morning. Is there a replacement for the MID
function to be used in SQL statements, or even SQL Triggers for that matter?My bad, wrong forum....found it anyway. SUBSTRING()
"Michael C" wrote:
> My brain is not working this morning. Is there a replacement for the MID
> function to be used in SQL statements, or even SQL Triggers for that matter?

Microsoft Visual Studio is busy

I get this message in a balloon that pops up frequently when I am trying to work in the SSIS designer. For example, I get it when working in a DataFlow task, trying to open editors for the OleDb Source and Destination. Is anyone else getting this? What could be the cause, it seems to get sluggish. Thanks.

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

|||TFYR. I'm just using the OLEDB source/destination that were installed when I upgraded my default instance to SS 2005. (I had been using SQL2005 side-by-side previously with SQL 2000). I've also noticed that when scripting objects it will also get sluggish and hangs for awhile on the step where it determines objects in the database. Right now, I've been waiting over 2 minutes to script a single proc out of the database, so I think there is some kind of systemic problem. Same problem when I try to expand some nodes in Object Explorer (Tables, procs etc), it'll be real sluggish.|||

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

TFYR. Yes, both source/dest are SQL Server machines. And yes, I can do an uninstall/re-install but probably won't get to it until next week . Do you think it might help if I tried removing the named SQL2005 instance that I have? Not sure how I would remove a named instance, but I will look in the docs.

Thanks.

|||

Rich,

You got me thinking about uninstalling/reinstalling but before trying it I wanted to try removing my SQL2005 named instance and the performance is now much improved. I haven't gotten the "Visual Studio is busy" message yet. I don't get the long delay when scripting objects out either. Maybe it was because I had originally installed SQL2005 as a named instance side by side with SQL2005 default instance and then upgraded the default instance to SQL2005 but never removed the named instance. Anyway, it is much, much improved. Thanks.

|||Yes... i'm facing that kind of problem almost everytime. Especially when the project contains a lot of packages. After the pop-up appears, it will hang and i have to terminate the process using ctrl+alt+del. Until now, i still can't configure what d problem is! I don think it is oledb connection. I would say it is software problem.|||How much RAM do you have? I found that adding RAM helped.|||

I'm running 2 gigs of memory on a 2 ghz processor. So i know my computer isn't trash. But As of recently, every single time i open Studio I get issues with a pop-up that "Microsoft Visual Studio is busy." let microsoft know....

and it hangs for roughly 10 seconds. so if I make 20 changes to a page, that the changes themselves took me 20 seconds... i just spent (20*10 + 20) 220 seconds, or nearly 4 minutes to make a few quick changes...

Or, let's say that i like saving the pages alot, which I do, so I may copy paste a <br />, and then it locks, then i'll type something and insert a <asp:label tag, and it locks, then i'll delete the ID and insert a new id, and it locks... and maybe it locks again.

|||I can certainly understand the frustration as I was in the same predicament. I was so desperate I added RAM (increased to 1.5GB) and also purchased Registry Booster. I also removed a named instance of SQL2005 that was a remnant of a side-by-side installation with SQL2000. Whatever I did got rid of the problem and I am no longer plagued by the "Microsoft Visual Studio is busy" message.|||

Hi folks:

I have the same exact problem. I see the message Visual studio is busy. For me this started happening after I installed Visual Studio 2005. I have 1 GB memory and i have both SQL 2000 (default instance) and SQL 2005 (named instance) running on the box. I never had this issue when i was running VS.NET 2003.

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

AK

|||

Hi there,

same problem here. Since I use SSIS development in Visual Studio in combination with Vista, Visual Studio keeps being busy after executing larger SSIS packages. Looks like a Vista problem. Before I used XP where te problem didn't occure. It partically occures when the SSIS package is handling large data volumes (more then 100000 records).

A solution would be welcome.

Thanks.

RK

Microsoft Visual Studio is busy

I get this message in a balloon that pops up frequently when I am trying to work in the SSIS designer. For example, I get it when working in a DataFlow task, trying to open editors for the OleDb Source and Destination. Is anyone else getting this? What could be the cause, it seems to get sluggish. Thanks.

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

|||TFYR. I'm just using the OLEDB source/destination that were installed when I upgraded my default instance to SS 2005. (I had been using SQL2005 side-by-side previously with SQL 2000). I've also noticed that when scripting objects it will also get sluggish and hangs for awhile on the step where it determines objects in the database. Right now, I've been waiting over 2 minutes to script a single proc out of the database, so I think there is some kind of systemic problem. Same problem when I try to expand some nodes in Object Explorer (Tables, procs etc), it'll be real sluggish.|||

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

TFYR. Yes, both source/dest are SQL Server machines. And yes, I can do an uninstall/re-install but probably won't get to it until next week . Do you think it might help if I tried removing the named SQL2005 instance that I have? Not sure how I would remove a named instance, but I will look in the docs.

Thanks.

|||

Rich,

You got me thinking about uninstalling/reinstalling but before trying it I wanted to try removing my SQL2005 named instance and the performance is now much improved. I haven't gotten the "Visual Studio is busy" message yet. I don't get the long delay when scripting objects out either. Maybe it was because I had originally installed SQL2005 as a named instance side by side with SQL2005 default instance and then upgraded the default instance to SQL2005 but never removed the named instance. Anyway, it is much, much improved. Thanks.

|||Yes... i'm facing that kind of problem almost everytime. Especially when the project contains a lot of packages. After the pop-up appears, it will hang and i have to terminate the process using ctrl+alt+del. Until now, i still can't configure what d problem is! I don think it is oledb connection. I would say it is software problem.|||How much RAM do you have? I found that adding RAM helped.|||

I'm running 2 gigs of memory on a 2 ghz processor. So i know my computer isn't trash. But As of recently, every single time i open Studio I get issues with a pop-up that "Microsoft Visual Studio is busy." let microsoft know....

and it hangs for roughly 10 seconds. so if I make 20 changes to a page, that the changes themselves took me 20 seconds... i just spent (20*10 + 20) 220 seconds, or nearly 4 minutes to make a few quick changes...

Or, let's say that i like saving the pages alot, which I do, so I may copy paste a <br />, and then it locks, then i'll type something and insert a <asp:label tag, and it locks, then i'll delete the ID and insert a new id, and it locks... and maybe it locks again.

|||I can certainly understand the frustration as I was in the same predicament. I was so desperate I added RAM (increased to 1.5GB) and also purchased Registry Booster. I also removed a named instance of SQL2005 that was a remnant of a side-by-side installation with SQL2000. Whatever I did got rid of the problem and I am no longer plagued by the "Microsoft Visual Studio is busy" message.|||

Hi folks:

I have the same exact problem. I see the message Visual studio is busy. For me this started happening after I installed Visual Studio 2005. I have 1 GB memory and i have both SQL 2000 (default instance) and SQL 2005 (named instance) running on the box. I never had this issue when i was running VS.NET 2003.

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

AK

Microsoft Visual Studio is busy

I get this message in a balloon that pops up frequently when I am trying to work in the SSIS designer. For example, I get it when working in a DataFlow task, trying to open editors for the OleDb Source and Destination. Is anyone else getting this? What could be the cause, it seems to get sluggish. Thanks.

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

|||TFYR. I'm just using the OLEDB source/destination that were installed when I upgraded my default instance to SS 2005. (I had been using SQL2005 side-by-side previously with SQL 2000). I've also noticed that when scripting objects it will also get sluggish and hangs for awhile on the step where it determines objects in the database. Right now, I've been waiting over 2 minutes to script a single proc out of the database, so I think there is some kind of systemic problem. Same problem when I try to expand some nodes in Object Explorer (Tables, procs etc), it'll be real sluggish.|||

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

TFYR. Yes, both source/dest are SQL Server machines. And yes, I can do an uninstall/re-install but probably won't get to it until next week . Do you think it might help if I tried removing the named SQL2005 instance that I have? Not sure how I would remove a named instance, but I will look in the docs.

Thanks.

|||

Rich,

You got me thinking about uninstalling/reinstalling but before trying it I wanted to try removing my SQL2005 named instance and the performance is now much improved. I haven't gotten the "Visual Studio is busy" message yet. I don't get the long delay when scripting objects out either. Maybe it was because I had originally installed SQL2005 as a named instance side by side with SQL2005 default instance and then upgraded the default instance to SQL2005 but never removed the named instance. Anyway, it is much, much improved. Thanks.

|||Yes... i'm facing that kind of problem almost everytime. Especially when the project contains a lot of packages. After the pop-up appears, it will hang and i have to terminate the process using ctrl+alt+del. Until now, i still can't configure what d problem is! I don think it is oledb connection. I would say it is software problem.|||How much RAM do you have? I found that adding RAM helped.|||

I'm running 2 gigs of memory on a 2 ghz processor. So i know my computer isn't trash. But As of recently, every single time i open Studio I get issues with a pop-up that "Microsoft Visual Studio is busy." let microsoft know....

and it hangs for roughly 10 seconds. so if I make 20 changes to a page, that the changes themselves took me 20 seconds... i just spent (20*10 + 20) 220 seconds, or nearly 4 minutes to make a few quick changes...

Or, let's say that i like saving the pages alot, which I do, so I may copy paste a <br />, and then it locks, then i'll type something and insert a <asp:label tag, and it locks, then i'll delete the ID and insert a new id, and it locks... and maybe it locks again.

|||I can certainly understand the frustration as I was in the same predicament. I was so desperate I added RAM (increased to 1.5GB) and also purchased Registry Booster. I also removed a named instance of SQL2005 that was a remnant of a side-by-side installation with SQL2000. Whatever I did got rid of the problem and I am no longer plagued by the "Microsoft Visual Studio is busy" message.|||

Hi folks:

I have the same exact problem. I see the message Visual studio is busy. For me this started happening after I installed Visual Studio 2005. I have 1 GB memory and i have both SQL 2000 (default instance) and SQL 2005 (named instance) running on the box. I never had this issue when i was running VS.NET 2003.

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

AK

Microsoft Visual Studio is busy

I get this message in a balloon that pops up frequently when I am trying to work in the SSIS designer. For example, I get it when working in a DataFlow task, trying to open editors for the OleDb Source and Destination. Is anyone else getting this? What could be the cause, it seems to get sluggish. Thanks.

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

|||TFYR. I'm just using the OLEDB source/destination that were installed when I upgraded my default instance to SS 2005. (I had been using SQL2005 side-by-side previously with SQL 2000). I've also noticed that when scripting objects it will also get sluggish and hangs for awhile on the step where it determines objects in the database. Right now, I've been waiting over 2 minutes to script a single proc out of the database, so I think there is some kind of systemic problem. Same problem when I try to expand some nodes in Object Explorer (Tables, procs etc), it'll be real sluggish.|||

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

TFYR. Yes, both source/dest are SQL Server machines. And yes, I can do an uninstall/re-install but probably won't get to it until next week . Do you think it might help if I tried removing the named SQL2005 instance that I have? Not sure how I would remove a named instance, but I will look in the docs.

Thanks.

|||

Rich,

You got me thinking about uninstalling/reinstalling but before trying it I wanted to try removing my SQL2005 named instance and the performance is now much improved. I haven't gotten the "Visual Studio is busy" message yet. I don't get the long delay when scripting objects out either. Maybe it was because I had originally installed SQL2005 as a named instance side by side with SQL2005 default instance and then upgraded the default instance to SQL2005 but never removed the named instance. Anyway, it is much, much improved. Thanks.

|||Yes... i'm facing that kind of problem almost everytime. Especially when the project contains a lot of packages. After the pop-up appears, it will hang and i have to terminate the process using ctrl+alt+del. Until now, i still can't configure what d problem is! I don think it is oledb connection. I would say it is software problem.|||How much RAM do you have? I found that adding RAM helped.|||

I'm running 2 gigs of memory on a 2 ghz processor. So i know my computer isn't trash. But As of recently, every single time i open Studio I get issues with a pop-up that "Microsoft Visual Studio is busy." let microsoft know....

and it hangs for roughly 10 seconds. so if I make 20 changes to a page, that the changes themselves took me 20 seconds... i just spent (20*10 + 20) 220 seconds, or nearly 4 minutes to make a few quick changes...

Or, let's say that i like saving the pages alot, which I do, so I may copy paste a <br />, and then it locks, then i'll type something and insert a <asp:label tag, and it locks, then i'll delete the ID and insert a new id, and it locks... and maybe it locks again.

|||I can certainly understand the frustration as I was in the same predicament. I was so desperate I added RAM (increased to 1.5GB) and also purchased Registry Booster. I also removed a named instance of SQL2005 that was a remnant of a side-by-side installation with SQL2000. Whatever I did got rid of the problem and I am no longer plagued by the "Microsoft Visual Studio is busy" message.|||

Hi folks:

I have the same exact problem. I see the message Visual studio is busy. For me this started happening after I installed Visual Studio 2005. I have 1 GB memory and i have both SQL 2000 (default instance) and SQL 2005 (named instance) running on the box. I never had this issue when i was running VS.NET 2003.

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

AK

|||

Hi there,

same problem here. Since I use SSIS development in Visual Studio in combination with Vista, Visual Studio keeps being busy after executing larger SSIS packages. Looks like a Vista problem. Before I used XP where te problem didn't occure. It partically occures when the SSIS package is handling large data volumes (more then 100000 records).

A solution would be welcome.

Thanks.

RK

Microsoft SQL Server, Error: 10053

O get this error when trying to connect to my database. About 5 minutes ago it was working fine...seems to go in and out. We have native client installed in this server as well so not sure why I keep having connection issues. I tried both Windows Authentification and local sql account, both are very choppy, sometimes works sometimes doesn't.

TITLE: Connect to Server

Cannot connect to BG-SQL2005.

ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine.) (Microsoft SQL Server, Error: 10053)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10053&LinkId=20476

BUTTONS:

OK

I am also getting this error when trying to ALTER one of my stored procs :

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

Mostlikely the server is closing the connections for some reason, possibly the client does not have permission to access some sqlserver resources, e.g. database, sp, xp. We might get more hint as to why if you could share out the sql server ERRORLOG.|||Here are my logs:
http://www.photopizzaz.biz/junk/logs.txt
aprint screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http://www.photopizzaz.biz/junk/sqlserver_2005_errors_and_resolutions.doc|||I can't see your error log. Please also enable sql server traceflag -T4029 when you do the repro. Update the errorlog with latest repro.|||

issue resolved, reinstalled SQL Server 2005 completely

thanks for the inputs!