![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Hi.. We can generate scripts of objects in SQL server using Enterprise Manager. For more info refer the following link http://msdn.microsoft.com/library/de.../en-us/entrmgr /agent_067n.asp |
#4
| |||
| |||
|
|
Good morning: At least it's morning where I am. ![]() |
|
I have a rather newbie question I'm afraid. I have VisualStudio.NET, and have installed it along with SQL server. However I can't seem to find an administration front-end to SQL, other than the VisualStudio, which is ok for creating databases and adding tables/columns. However when I go to generate create script, I'm told that I need client tools. I've installed everything from the cd's - am I missing something very obvious, and/or how does one import scripts? |
#5
| |||
| |||
|
|
Dagwood ("Dagwood Bumstead"@antionline.com) writes: Good morning: At least it's morning where I am. ![]() Good Evening to you! :-) |
|
I have a rather newbie question I'm afraid. I have VisualStudio.NET, and have installed it along with SQL server. However I can't seem to find an administration front-end to SQL, other than the VisualStudio, which is ok for creating databases and adding tables/columns. However when I go to generate create script, I'm told that I need client tools. I've installed everything from the cd's - am I missing something very obvious, and/or how does one import scripts? With VS.Net you get MSDE, and MSDE does not come with any other administration tools than OSQL which is a command-line tool. To get the fancy stuff, you need to buy an SQL Server license. |
|
But don't despair. MS has announced that from Aug 1st the price for Developer Edition will be slashed to 49 USD. (The current price is about 10 as high.) In the mean while, you can download the Evaluation Edition of SQL Server from www.microsoft.com/sql. It is good for 120 days. |

#6
| |||
| |||
|
|
Hmm, well I have an SQL server with SQL service manager, is this MSDE? What does the acronymn MSDE stand for? |
|
I don't mind using a term and CLI, but I can use VStudio can I not for this, in terms of importing data? I've already created the database and tables... |
#7
| |||
| |||
|
|
Dagwood ("Dagwood Bumstead"@antionline.com) writes: Hmm, well I have an SQL server with SQL service manager, is this MSDE? What does the acronymn MSDE stand for? MSDE is the desktop edition of MS SQL Server. It comes with a bunch of products, VS and Office Developer are two examples. You can also build an application that uses MSDE and redistribute freely. I don't mind using a term and CLI, but I can use VStudio can I not for this, in terms of importing data? I've already created the database and tables... If the command-lines are there, you should have BCP as well. That's good for import. If you have MSDN Library, you should have all SQL documentation there. Else, check my signature. |
#8
| |||
| |||
|
|
In comp.databases.ms-sqlserver, Erland Sommarskog wrote: Dagwood ("Dagwood Bumstead"@antionline.com) writes: Hmm, well I have an SQL server with SQL service manager, is this MSDE? What does the acronymn MSDE stand for? MSDE is the desktop edition of MS SQL Server. It comes with a bunch of products, VS and Office Developer are two examples. You can also build an application that uses MSDE and redistribute freely. I don't mind using a term and CLI, but I can use VStudio can I not for this, in terms of importing data? I've already created the database and tables... If the command-lines are there, you should have BCP as well. That's good for import. If you have MSDN Library, you should have all SQL documentation there. Else, check my signature. Ok thanks, (I apologize in advance for being thick headed), but you haven't really answered my question. First, what I've got is NOT called MSDE, I don't have anything on my install disk or on my hard drive called that. It says SQL server, explicitly. You're saying that MSDE is NOT referred to as SQL server or is? Why would it be called SQL server, if in fact it isn't MS-SQL? Second, if one can create tables in VisualStudio, surely one can import data -- is this too far fetched, or am I totally off base here, without using a terminal? I use a terminal, but I'm trying to figure out why I need VisualStudio.NET, as I have independent apps that I use in WebDevelopment, I'm not an application developer, I simply create dynamic websites. I guess I should go back to PostreSQL, at least I have the whole application. -- Regards ================================================== ====================== |
|
You have been selected for a secret mission. |
#9
| |||
| |||
|
|
In comp.databases.ms-sqlserver, Erland Sommarskog wrote: Dagwood ("Dagwood Bumstead"@antionline.com) writes: Hmm, well I have an SQL server with SQL service manager, is this MSDE? What does the acronymn MSDE stand for? MSDE is the desktop edition of MS SQL Server. It comes with a bunch of products, VS and Office Developer are two examples. You can also build an application that uses MSDE and redistribute freely. I don't mind using a term and CLI, but I can use VStudio can I not for this, in terms of importing data? I've already created the database and tables... If the command-lines are there, you should have BCP as well. That's good for import. If you have MSDN Library, you should have all SQL documentation there. Else, check my signature. Ok thanks, (I apologize in advance for being thick headed), but you haven't really answered my question. First, what I've got is NOT called MSDE, I don't have anything on my install disk or on my hard drive called that. It says SQL server, explicitly. You're saying that MSDE is NOT referred to as SQL server or is? Why would it be called SQL server, if in fact it isn't MS-SQL? Second, if one can create tables in VisualStudio, surely one can import data -- is this too far fetched, or am I totally off base here, without using a terminal? I use a terminal, but I'm trying to figure out why I need VisualStudio.NET, as I have independent apps that I use in WebDevelopment, I'm not an application developer, I simply create dynamic websites. I guess I should go back to PostreSQL, at least I have the whole application. -- Regards ================================================== ========================= You have been selected for a secret mission. |
#10
| |||
| |||
|
|
On Sun, 27 Jul 2003 11:06:20 -0400, Dagwood <"Dagwood Bumstead"@antionline.com> wrote: |
|
I guess I should go back to PostreSQL, at least I have the whole application. What MSDE is is a sort of SQL Server Light - it has nearly all of the functionality of SQL Server (with a limited number of allowable concurrent connections) but none of the fancy GUI tools. It is intended to be a redistributable version of SQL Server: Microsoft allows it to be distributed free with applications. So, as a developer, you can actually distribute applications with their own little SQL Server engine. To protect their marketability of the full version of SQL Server, they don't give you all the tools or the GUI. However, with the command line interface, you can replicate a surprising percentage of the full version. Personally, I think it was a pretty cool thing that Microsoft did - it is a more robust solution for single user database apps than using Access mdb's, anyway. You *do* have the whole version of MSDE - it is just a "light" version of SQL Server, though I would agree it is not nearly as convenient to use. |
![]() |
| Thread Tools | |
| Display Modes | |
| |