Migration to VS 2003 worked though I don't know why 
Author Message
 Migration to VS 2003 worked though I don't know why

I made the migration to VS 2003 from 2002 and it seems to have worked though
I can't explain some things.  I am perplexed because of the difference in
the way I used to access my SQL Server 2000 database and the way I do now.
Prior to the move the database I am interested in resided in a Server Name
of P3800\NetSdk.  (My machine name is P3800).  Now I am able to access the
same database but it is residing in a Server Name of P3800.  Don't ask me
how I go it there but I did.

There are obviously some fundamentals that I do not understand wrt VS and
server group names.  In the end it doesn't make any difference to me as long
as VS considers what I have done as orthodox and it works.  Somehow, in the
past, I got it in my mind that there was some disadvantage or there was
something wrong in having a database in my local server.  Is this OK?  Does
it have to be or should it be in something else like NetSDK?  Am I in Okey
Dokey land by accessing my database in Local?

I should add, however, that I must have something wrong because when I go
into a particular project, the computer halts for a long time and finally
comes up with a connection dialog that makes reference to the old
P3800\NetSDK.  This is strange because no such directory even exists any
more.  There used to be a dir under my Microsoft SQL Server directory called
$NetSDK but it is history now.  How can I set things up so VS is happy with
it and it works too?



Sun, 04 Dec 2005 08:48:33 GMT  
 Migration to VS 2003 worked though I don't know why
NetSdk is a SQL server 2000 instance on your computer installed with
VS.NET. We can install multiple of  SQL Server 2000 on same computer. For
detail on this, you can refer to this article:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
ar_cs_9i5u.asp

Hope this help

Luke

(This posting is provided "AS IS", with no warranties, and confers no
rights.)



Mon, 05 Dec 2005 11:23:29 GMT  
 Migration to VS 2003 worked though I don't know why

Quote:
> NetSdk is a SQL server 2000 instance on your computer installed with
> VS.NET.

If I understand, VS.net itself created this instance when I installed,
correct?  Is this true in both VS 2002 and 2003?  If you do not already have
SQL Server installed on a local machine and you install VS.net 2003 or 2003
will it automatically create this instance name?

Could you explain this to me.  I have a situation where I have a database
named Invoices.  It shows up in two different InstanceNames.  I made a
change to the database from InstanceName_A.  I switched to InstanceName_B
and the change I made in A was reflected there.  How could this be?  Is it
simply because they are both pointing to the  same database?

Thank you for help and thank you for pointing me to the web site.  It
answered a number of questions.

Woody



Quote:
> NetSdk is a SQL server 2000 instance on your computer installed with
> VS.NET. We can install multiple of  SQL Server 2000 on same computer. For
> detail on this, you can refer to this article:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
Quote:
> ar_cs_9i5u.asp

> Hope this help

> Luke

> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)



Mon, 05 Dec 2005 22:58:15 GMT  
 Migration to VS 2003 worked though I don't know why

[If I understand, VS.net itself created this instance when I installed,
correct?  Is this true in both VS 2002 and 2003?  If you do not already
have SQL Server installed on a local machine and you install VS.net 2003 or
2003 will it automatically create this instance name?]

Yes, your are right, This incidence will installed with VS.NET 2002 and
2003 whenever we have SQL server installed before.

[Could you explain this to me.  I have a situation where I have a database
named Invoices.  It shows up in two different InstanceNames.  I made a
change to the database from InstanceName_A.  I switched to InstanceName_B
and the change I made in A was reflected there.  How could this be?  Is it
simply because they are both pointing to the  same database?]

For a SQL server database, there will be two files will be created: .mdf
and .ldf. They store the data in the database and their log information.  
For example, the database "pubs" is on the two files: pubs.mdf and
pubs_log.ldf. You may check if your two instance share these database
files.

Luke

(This posting is provided "AS IS", with no warranties, and confers no
rights.)



Fri, 09 Dec 2005 21:08:04 GMT  
 
 [ 4 post ] 

 Relevant Pages 

1. does anybody know why this code don't work

2. I don't know why..

3. PLS Help, I don't know why to write

4. VB4 16bit GPF and I don't know why (I bother sometimes)

5. I don't know why..

6. ADO Error! Don't know why

7. PLS Help, I don't know why to write

8. Will the TabControl work in VS.Net 2003?

9. VB .Net 2003 Standard or VS .Net 2003 Pro for Smart Devices

10. ANN: What's new in VS 2003 (Everett)

11. Sprites and why they don't work

12. Wallpaper Why don't this work in Win95

 

 
Powered by phpBB® Forum Software