Friday, March 23, 2012
name of SQL Server
HI
The SQL Server name is the computer NETBIOS name (default instance) or [NETBIOS NAME]\[instance name] when you use named instance of SQL server.
Andras Jakus MCDBA
"martynroots" wrote:
> This is a very basic question. I have just installed SQL Server 2000 Developer. Could someone tell me please how I find out what the server name is? I have tried using OEMCOMPUTER but that didn't work. I am therefore unable to connect to the server.
|||Go to Start --> Programs --> Microsoft SQL Server --> Server Network Utility. The General Tab of the utility should list the SQL Instances that you have installed on your computer. Hope this helps.
Tea C.
"martynroots" wrote:
> This is a very basic question. I have just installed SQL Server 2000 Developer. Could someone tell me please how I find out what the server name is? I have tried using OEMCOMPUTER but that didn't work. I am therefore unable to connect to the server.
|||Go to Start --> Programs --> Microsoft SQL Server --> Server Network Utility. The General Tab of the utility should list the SQL Instances that you have installed on your computer. Hope this helps.
Tea C.
"martynroots" wrote:
> This is a very basic question. I have just installed SQL Server 2000 Developer. Could someone tell me please how I find out what the server name is? I have tried using OEMCOMPUTER but that didn't work. I am therefore unable to connect to the server.
name of SQL Server
per. Could someone tell me please how I find out what the server name is?
I have tried using OEMCOMPUTER but that didn't work. I am therefore unable
to connect to the server.HI
The SQL Server name is the computer NETBIOS name (default instance) or [
NETBIOS NAME]\[instance name] when you use named instance of SQL server.
Andras Jakus MCDBA
"martynroots" wrote:
> This is a very basic question. I have just installed SQL Server 2000 Developer.
Could someone tell me please how I find out what the server name is? I have tried u
sing OEMCOMPUTER but that didn't work. I am therefore unable to connect to the serv
er.|||Go to Start --> Programs --> Microsoft SQL Server --> Server Network Utility
. The General Tab of the utility should list the SQL Instances that you hav
e installed on your computer. Hope this helps.
Tea C.
"martynroots" wrote:
> This is a very basic question. I have just installed SQL Server 2000 Developer.
Could someone tell me please how I find out what the server name is? I have tried u
sing OEMCOMPUTER but that didn't work. I am therefore unable to connect to the serv
er.|||Go to Start --> Programs --> Microsoft SQL Server --> Server Network Utility
. The General Tab of the utility should list the SQL Instances that you hav
e installed on your computer. Hope this helps.
--
Tea C.
"martynroots" wrote:
> This is a very basic question. I have just installed SQL Server 2000 Developer.
Could someone tell me please how I find out what the server name is? I have tried u
sing OEMCOMPUTER but that didn't work. I am therefore unable to connect to the serv
er.sql
Wednesday, March 21, 2012
n00b: best way to import flat file with BIDS
I'm totally new to SQL Server 2k5 and need to do something rather basic: import some CSV files into tables. I'm getting translation errors and would like to know what's the best way to cast the strings before inserts.
I'm doing the import in BI Development Studio.
Current situation:
Created connection managers to csv files
created SQL server destinations pointing to the tables
connected them directly with a dataflow path
Ran the packadge: one import went just fine, the other one complains about conversion errors like "Conversion DT_STR and DT_I4 not supported"
Both tables have the same kind of fields (varchar, float, datetime, int)
I looked at converting the data using a transformation but am somewhat confused of which one to use.
What's the best way to transform the data before insert: derived column, import column or data conversion? Or something else I overlooked?
TIA
PeterFor doing this kind of work, I prefer to use bcp.exe over SSIS/DTS. It's a simple command line utility.
Look for "bcp utility" in BOL.
Monday, March 12, 2012
MySQL vs. MS SQL Server. What's the difference?
I'm a beginner programmer and databases are still a bit of a mystery to me. I have some basic questions that I can't find direct answers for anywhere but which I think should be fairly simple for someone acquainted with using databases in programming.
1. MySQL & MS SQL Server (or Express)...what's the difference? Are they mutually compatible? Are all SQL files written in the same file format?
2. If I write create a MySQL database on my website to store customer data, can my application which was written with VB 2005 Express (and which uses MS SQL Server Express) read those database files? Vice-versa?
3. If I create a MS SQL database in VB express for my application, is that database on some huge central server somewhere or is my computer used as the server, or what? (yeah, I know that's probably a really stupid question but I can find the answer in any of the three programming books I've bought in recent months or online either.)
4. I've read the MySQL is free unless I use the databases within an actual application from which I'm making money, in which case I need to buy a license. What about MS SQL Server or MS SQL Express? Microsoft can be so withholding about what costs money, what is free, and what is temporarily free.
That's all for now...I hope someone can answer my stupid questions.
1. No the file types are not compatible, they are from different vendors. Even the SQL symtax differ but shares a common dictionary the SQL Ansi standard.
2. That depends on how you did your database layer implementation. Some developers use the generic adapter approach making database capable for many database whereas only the adapter using to connect to the database has to be exchange. if you are using the SQL* classes in youa application and not the e.g. OLEDb like olecbcommand you cannot switch to another database within your application.
3. The SQL Server editions (beside the compact edition) run as services. They do not have to run on a "central computer" and can be based on normal pcs (depending on the edition you need a server OS to install the services like for enterprise edition) The SQL Server express editions were designed to run on normal worksatation having a local database stored on the computer.
4. All edition beside the SQL Server Express and the Compact editions have to be licensed. they either go by the Server/cal or the processor licence. SQL Server Express and Comnpact edition are free not matter if you shipping them with your applications or using them privately.
See the frature comparisons on this site for more information wheter SQL Server Express fits your needs, as it has some limitations:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
No stupid question at all :-)
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Hey Jens, thank you so much for answering my questions.Saturday, February 25, 2012
My SQL application on Windows Mobile 5
My application :
On PC : Access application + Access DB
On PocketPC : Embedded Visual Basic 3.0 application + PocketAccess DB
I synchronise my DBs through ActivSync.
It runs good before Windows Mobile 5.
My customers asked me for new PocketPC with this application, so I bought some new PocketPCs : but as I see, syncronisation with Access is no more supported.
So what are my solutions ?
My customer wait for there PocketPC, so I need a quick solution, I don't want to rewrite all my application now.
My application run before WM5, so now I don't want to have to pay for a Visual Studio .Net, some SQL Server, etc ....
Please, what are the solutions that won't cost me more than the time that have already lost with this new Windows Mobile 5 ?
Jo?l
Joel,
You're at the end of the road with eVB. You are going to need to move your mobile application's code either to the .NET Compact Framework or use Visual C++ for Mobile Devices (in VS2005) to achieve Windows Mobile 5 compliance. I recommend using SQL Mobile for your on-device database as a replacement for Pocket Access. Sorry there isn't better news, but eVB and Access have reached the end of their support time horizon for current and future Windows Mobile platforms.
-Darren
|||Ok Darren
So if I move my application to .Net et use SQL Mobile 2005 on my PocketPC, what do I need to synchronise my PocketPC's database (so SQL Mobile) and my PC Database ?
Which database on PC ?
Each PocketPC will have his own PC and his own database, and it have to run my application on Windows XP Home.
What solution for synchronisation ?
Thanks for your explanations
Jo?l
|||Any solution ?
Jo?l
|||
Joel,
SQL Mobile comes with two options for data synchronization, Remote Data Access and Merge Replication. Both of these require IIS as the broker or gateway through which this synchronization occurs. In your situation, you may want to write a simple synchronization method that detects when the device is connected and uses System.Data.SqlClient to synchronize between your device database and SQL Server 2005.
-Darren
|||Ok Darren, thks.Is there a place where I can find some example of this method ?
My SQL application on Windows Mobile 5
My application :
On PC : Access application + Access DB
On PocketPC : Embedded Visual Basic 3.0 application + PocketAccess DB
I synchronise my DBs through ActivSync.
It runs good before Windows Mobile 5.
My customers asked me for new PocketPC with this application, so I bought some new PocketPCs : but as I see, syncronisation with Access is no more supported.
So what are my solutions ?
My customer wait for there PocketPC, so I need a quick solution, I don't want to rewrite all my application now.
My application run before WM5, so now I don't want to have to pay for a Visual Studio .Net, some SQL Server, etc ....
Please, what are the solutions that won't cost me more than the time that have already lost with this new Windows Mobile 5 ?
Jo?l
Joel,
You're at the end of the road with eVB. You are going to need to move your mobile application's code either to the .NET Compact Framework or use Visual C++ for Mobile Devices (in VS2005) to achieve Windows Mobile 5 compliance. I recommend using SQL Mobile for your on-device database as a replacement for Pocket Access. Sorry there isn't better news, but eVB and Access have reached the end of their support time horizon for current and future Windows Mobile platforms.
-Darren
|||
Ok Darren
So if I move my application to .Net et use SQL Mobile 2005 on my PocketPC, what do I need to synchronise my PocketPC's database (so SQL Mobile) and my PC Database ?
Which database on PC ?
Each PocketPC will have his own PC and his own database, and it have to run my application on Windows XP Home.
What solution for synchronisation ?
Thanks for your explanations
Jo?l|||Any solution ?
Jo?l|||
Joel,
SQL Mobile comes with two options for data synchronization, Remote Data Access and Merge Replication. Both of these require IIS as the broker or gateway through which this synchronization occurs. In your situation, you may want to write a simple synchronization method that detects when the device is connected and uses System.Data.SqlClient to synchronize between your device database and SQL Server 2005.
-Darren
|||Ok Darren, thks.
Is there a place where I can find some example of this method ?