Ms Sql...

Thinker said:
Unless there is something special needed for .net, everything
should be in mdac_typ.exe. (Unless you are asking for MSDE?)
Click to expand...

Ya, my mistake. I ment MSDE. My VB6 professional comes with MSDE 1.0 for VB6, but that's for SQL Server 7.0 and not sure if MSDE 1.0 can be used under .NET?

Here's the link for MSDE 2000 (for .NET)
http://www.microsoft.com/sql/techinfo/development/2000/MSDE2000.asp

Roaming around the site (just now, probably should of done this in the first place) it says that it comes with the .NET SDK.
http://www.microsoft.com/technet/treeview/?url=/technet/security/msdeapps.asp

*ponders* Maybe I already have it installed and am just to moronic to look? I guess if I already have MSDE installed..
1) How do I check to see if it is, if it isn't where in the .NET SDK is the setup.exe for it?
2) How do I create an MS SQL database, or am I only able to connect to one using MSDE?

I know, silly questions.. I always use Access and never bother with MS SQL so. :( Lack of knowledge as to how MS SQL exactly works just sucks.. time to learn.
 
Okay.. I put in the install CD for .NET, and it had SQL Server checked for install (I went to update/remove components). I clicked on it to read the message, and it said to complete the install to go to ../setup/msde/ and run the setup.exe. I did that, it did somethin then quit.. reboot and now I got some little SQL Server icon in my system tray.

After all that, I opened up .NET and it has options and what not for creating SQL Server databases under my server explorer. It seems to be working fine I guess. If I have more questions I'll post in the database area.

Next thing I'm going to do is read the readme and see what all this about SP update stuff is.

Thanks for the help... :) Sometimes I just need a little push to get my brain ticking.
 
That SQL Server icon opens up the Service Manager. It is useful
for starting and stopping the services and checking their state but
you will need something else to do things like create new
databases. If you have Access you can create an Access project
(.adp) that acts as a front end for SQL Server. There is a dosbox/
command prompt interface called osql that will let you execute
any command in the server. There are other third-party admin
tools out there too (although I don't know if any of them are
written in .net). MSDE is very useful but if you are used to having
the enterprise tools available (enterprise manager/query analyzer)
it can sometimes be very frustrating.
 
msde

I had several wild days learning how to write the permissions that would allow select, insert, and delete sql in the msde databases. MSDN has some helpful although criptic pages. In Access, you use the Tools|Database Utilities|Upsizing Wizard to create/convert your Access database to one that can be used by sqlserver. After fighting with it for several days (successfully I'm happy to report) I came to the conclusion I would create and use the msde only when I expected greater than 20 users accessing my data at any time. For me that hasn't been an issue yet;)
 
Thinker - VS.NET comes with a cut-down version of enterprise manager in the form of the Server Explorer. I guess it's intended for people who install MSDE with Visual Studio. It's actually pretty good.
 
Yah, as divil said I've been using the Server Explorer. I just need to see if I can find documentation on it, there's a few things on it that I'm not familiar with. (well, it'd probably help if I was familiar with MS SQL heh)
 
Have you tried creating a VS.NET DataBase project to connect to your MSDE database? I haven't tried it yet, thought I have used the DB project type to connect to SQL Server and LOVE it (stored procs in SourceSafe - oh yeah!).

-nerseus
 
It seems to.. except a few problems I have when creating a database.

1) I have to use my full computer name, it doesn't accept localhost for some reason? :\
2) I can't add a login/pass for the database, it gives me an error saying that the "user is not associated with a trusted Sql Server connection". How can I fix that? Until I figure that out all my databases use generic Integrated Security.

Everything else seems to work just fine (haven't tested much though).

C#: 
DataSet ds = new DataSet();
SqlConnection con = 
   new SqlConnection(@"data source=*****-Z3KRWZD9LVE\VSdotNET;initial catalog=testdb;integrated security=SSPI;persist security info=False;workstation id=*****-Z3KRWZD9LVE;packet size=4096");

SqlDataAdapter da = new SqlDataAdapter("Select * from Names", con);
da.Fill(ds, "Names");
dataGrid1.DataSource = ds.Tables["Names"];
 
Wyrd,
Try (local)\netsdk in your connection string as datasource
Visual Basic: 
dim conn as string = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Payroll;Data Source=(local)\netsdk;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=LAPTOP;Use Encryption for Data=False;Tag with column collation when possible=False"

works for me.
 
Last edited:
Hmm.. interesting. Thanks for the info, works good. Except mine has to be pointed to (local)\VSdotNET . Good stuff. :)

Now if I can just figure out the username/password problem I'm set.
 
divil said:
Thinker - VS.NET comes with a cut-down version of enterprise manager in the form of the Server Explorer. I guess it's intended for people who install MSDE with Visual Studio. It's actually pretty good.
Click to expand...

Ah, cool! That should help make MSDE much more popular. I
know Microsoft really wants to transition people from Access to
it as the low-end database of choice.
 
NOTE: I know this thread is old.

fjackler:
Coming back to MSDE and actually needing to admin MSDE a little bit this time around (when I originaly posted this thread I was just toying with it), I found those links most helpful. Thanks.
 
Back
Top