|
Yes, that certainly works and saves alot of typing.
In either case, the best 'optimized' version would be 3 separate stored procs. Since the SQL Server optimizes a SP by its first execution (ignoring later re-optimizations due to structure changes), one side of the IF statement will be ignored. In your case, one side is an index lookup and the other is a table scan. It may be best to put each side into its own stored proc and put the IF in another. This way both are optimized properly for execution.
Of course, this is a useless point if your tables are small.
|
|
|
|
|
I have a DetailsView (ID=CtrDetails) in Visual Studio 2005 with the following Columns:
-CustomerID
-Customer
How can I retrieve the value of the columm CustomerID ???
I expect something like "Where CtrDetails.Value=X" or something like that
THANX ¡¡¡
|
|
|
|
|
I have a table:
ID FirstName CreateDate UpdateDate
How would I update the UpdateDate when making an entry in the table? The createDate has the getdate() function allready...
Illegal Operation
Making Computer Software Talk
|
|
|
|
|
is ur UpdateDate field value varchar or datetime and u need to update from ur application or directly in SQL Query
regards
_____________________
Proud to be Albanian
_____________________
|
|
|
|
|
The value of updatedate should be datetime as well because I want to update the date in sql when the entry is made.
This must be executed in the Stored procedure...
Illegal Operation
Making Computer Software Talk
|
|
|
|
|
Investigate the use of insert and update triggers on your table. The insert trigger can set CreateDate and UpdateDate to the current time. The update trigger should ensure that CreateDate is not changed and that UpdateDate is set to the current time.
Chris Meech
I am Canadian. [heard in a local bar]
When I want privacy, I'll close the bathroom door. [Stan Shannon]
BAD DAY FOR: Friendly competition, as Ford Motor Co. declared the employee parking lot at its truck plant in Dearborn, Mich., off limits to vehicles built by rival companies. Workers have to drive a Ford to work, or park across the street. [CNNMoney.com]
Nice sig! [Tim Deveaux on Matt Newman's sig with a quote from me]
|
|
|
|
|
Hi,
i am having a stored procedure like this:
CREATE PROCEDURE SP1 @arg1 varchar(100)
select * from emp where empid in (@arg1)
the argument @arg1 will depend on the user's choice in the front end. An example of this argument may look like this:
'emp1','emp2','emp6'
My problem is "I am unable to pass this type of argument for executing the stored procedure"
Please help. Thank You.
Please Plant Trees to Save the Mother Earth.
|
|
|
|
|
The above problem i am facing in SQL Query Analyser .
|
|
|
|
|
Would that work in a languge like C# or VB.NET? For example, if I had some code like this:
public void DoStuff(string arg)
{
if (arg)
{
DoSomething();
}
else
{
DoSomethingElse();
}
}where arg is: (this.someField == "Hello") || (this.someOtherField == "World"))
No? So why do people seem to think that kind of thing should work in SQL. (Sorry, I just see this question over and over on various forums)
ColinMackay.net
Scottish Developers are looking for speakers for user group sessions over the next few months. Do you want to know more?
|
|
|
|
|
Possible solutions:
* You could pass in multiple arguments.
* You could create some dynamic sql, concatenating strings together and executing it. (Not recommended unless you absolutely have no other viable solution as it is a security risk)
ColinMackay.net
Scottish Developers are looking for speakers for user group sessions over the next few months. Do you want to know more?
|
|
|
|
|
This worked fine for me:
create proc SP1 @arg1 varchar(100)<br />
as <br />
select @arg1 = 'select * from emp where empid in(' + @arg1 +')'<br />
<br />
exec (@arg1)
----------
There go my people. I must find out where they are going so I can lead them.
- Alexander Ledru-Rollin
|
|
|
|
|
But remember, there are security issue using dynamic SQL execution.
ColinMackay.net
Scottish Developers are looking for speakers for user group sessions over the next few months. Do you want to know more?
|
|
|
|
|
Hi,
I my stored procedure I have something like:
SELECT CategoryID_PK, CategoryName FROM tblCategories;
If this select goes through fine, what is the default value returned? Is it 0? Is it necessary to have a RETURN 0 after the SELECT statement? Or when is the RETURN 0 required?
If the stored procedure must just do a simple SELECT statement, must they still be between a BEGIN and END? When is this required?
I hope someone can help me clear things up.
Regards,
ma se
|
|
|
|
|
Return values are only useful if you read them. No need to return at the end of a stored proc.
BEGIN, END are used for code block seperation such as in an IF/ELSE statement. They are not necessary anywhere else.
|
|
|
|
|
Hello,
I am getting DB_E_DATAFIELD_OVERFLOW run-time error while retriving the value of the field using value property on Field object. I get the error while retrieving the records having value greater than 2147483648. If the data value is suppose 1000023 than all is fine.
Query is like : select F_DOCNUMBER from fndocument where F_DOCNUMBER > 10000000;
Datatype of column is 19 i.e unsigned long..
Please help... Its really urgent
....Thanks in advance.....
Suraj Gupta
|
|
|
|
|
You don't give enough information to help:
* What database are you using?
* What are you using to access the database?
ColinMackay.net
Scottish Developers are looking for speakers for user group sessions over the next few months. Do you want to know more?
|
|
|
|
|
Firts of all thanks for responding.
By the way we are using SQL Server. And using ADODB to access the database. We have our own OLEDB provider. It pass the recordset to the client in tabular format.
Anything else, that can help you out to know exact problem.
Thanks and Regards,
Suraj Gupta
Suraj Gupta
|
|
|
|
|
Please, if any one can help me out.
Thanks and Regards,
Suraj Gupta
Suraj Gupta
|
|
|
|
|
hi there,
I am connecting to a sql server express 2005 database which is located on another developers machine in the company. he has given me the username and password and i can read and write to this db using vs2005 no problems.
i can also added new tables and everything through the management studio, but when i add stored procedures, it does not seem to commit to the database, when i click save it asks for a local destination but i want it to save onto the sql server.
i can add stored procedures through vs 2005 no problems! this does not make sense?
|
|
|
|
|
NewbieDude wrote: but when i add stored procedures, it does not seem to commit to the database, when i click save it asks for a local destination but i want it to save onto the sql server.
When you click "save" it wants to "save" a file, naturally. You need to "execute" (F5 - if you want the keyboard shortcut) the SQL in order to apply it to the database.
ColinMackay.net
Scottish Developers are looking for speakers for user group sessions over the next few months. Do you want to know more?
|
|
|
|
|
Hi
I am developing a website in which we sale/purchase vehicles of different categories eg Cars,boats,trucks,aircrafts etc.
I am using MySQL at backEnd with ASP.net. I need to develop a database which should contain all the Makes(BMW,Mercedez etc) and their relevent Models.
From where can I download such database.
Thanks
Lets work it Out.........!
|
|
|
|
|
dont really understand the question. Do you want to know where to download MySQL or where to download an actual database.
You can get mySQL from
http://dev.mysql.com/downloads/ [^]
As for the database the idea is you build it yourself. Shouldnt be too hard for someone with a Masters.
Jon
|
|
|
|
|
I have MySQL and I need to download the database. I have the idea to build the database But i need to escape from entering so much data by my self. As you know there are so many Makes and there Models in the market and it will be very hard to enter entire data by mySelf.
I hope you understand now. Thanks for rply
Lets work it Out.........!
|
|
|
|
|
Hi All,
there are softwares that automatically converts mysql to sql server script. i have below script and i want to convert into sql server 2000 format so please help me change this script to sql server format.
many thanks in forward.
---------------------
-- MySQL Administrator dump 1.4
--
-- ------------------------------------------------------
-- Server version 3.23.53-max-nt
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
--
-- Remove the CREATE line below if you already have a database setup.
--
--
CREATE DATABASE /*!32312 IF NOT EXISTS*/ dating_db;
--
-- Change this to your database name.
--
USE dating_db;
--
-- Table structure for table `dating_db`.`abusereports`
--
DROP TABLE IF EXISTS `abusereports`;
CREATE TABLE `abusereports` (
`RecordID` int(10) unsigned NOT NULL auto_increment,
`RecordDate` timestamp(14) NOT NULL,
`AbuserID` int(10) unsigned NOT NULL default '0',
`ReporterID` int(10) unsigned NOT NULL default '0',
`ReporterComments` varchar(128) default '',
`AbuseTypeID` tinyint(4) NOT NULL default '0',
PRIMARY KEY (`RecordID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`abusereports`
--
/*!40000 ALTER TABLE `abusereports` DISABLE KEYS */;
/*!40000 ALTER TABLE `abusereports` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`abusers`
--
DROP TABLE IF EXISTS `abusers`;
CREATE TABLE `abusers` (
`RecordID` int(10) unsigned NOT NULL auto_increment,
`SuspensionDate` datetime NOT NULL default '0000-00-00 00:00:00',
`DeletionDate` timestamp(14) NOT NULL,
`FlagTypeID` tinyint(4) NOT NULL default '0',
`AbuserUserName` varchar(16) NOT NULL default '',
`AbuserEmail` text NOT NULL,
PRIMARY KEY (`RecordID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`abusers`
--
/*!40000 ALTER TABLE `abusers` DISABLE KEYS */;
/*!40000 ALTER TABLE `abusers` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`abusetypes`
--
DROP TABLE IF EXISTS `abusetypes`;
CREATE TABLE `abusetypes` (
`AbuseTypeID` tinyint(3) unsigned NOT NULL auto_increment,
`AbuseTypeName` tinytext NOT NULL,
PRIMARY KEY (`AbuseTypeID`)
) TYPE=MyISAM COMMENT='static';
--
-- Dumping data for table `dating_db`.`abusetypes`
--
/*!40000 ALTER TABLE `abusetypes` DISABLE KEYS */;
INSERT INTO `abusetypes` (`AbuseTypeID`,`AbuseTypeName`) VALUES
(1,'Profile contains nudity'),
(2,'Profile includes a picture of a minor'),
(3,'Profile contains copyrighted material'),
(4,'Profile contains spam'),
(5,'Profile contains racist or hateful words'),
(6,'Other (please comment)');
/*!40000 ALTER TABLE `abusetypes` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`bodytypes`
--
DROP TABLE IF EXISTS `bodytypes`;
CREATE TABLE `bodytypes` (
`BodyTypeID` tinyint(3) unsigned NOT NULL auto_increment,
`BodyTypeName` tinytext NOT NULL,
PRIMARY KEY (`BodyTypeID`)
) TYPE=MyISAM COMMENT='static';
--
-- Dumping data for table `dating_db`.`bodytypes`
--
/*!40000 ALTER TABLE `bodytypes` DISABLE KEYS */;
INSERT INTO `bodytypes` (`BodyTypeID`,`BodyTypeName`) VALUES
(1,'average'),
(2,'slim/slender'),
(3,'athletic'),
(4,'thick'),
(5,'a little extra padding'),
(6,'large');
/*!40000 ALTER TABLE `bodytypes` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`databaseerrors`
--
DROP TABLE IF EXISTS `databaseerrors`;
CREATE TABLE `databaseerrors` (
`ErrorID` smallint(5) unsigned NOT NULL auto_increment,
`ErrorDate` datetime NOT NULL default '0000-00-00 00:00:00',
`SqlStatement` text NOT NULL,
`Exception` text NOT NULL,
`PageName` tinytext NOT NULL,
PRIMARY KEY (`ErrorID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`databaseerrors`
--
/*!40000 ALTER TABLE `databaseerrors` DISABLE KEYS */;
/*!40000 ALTER TABLE `databaseerrors` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`emailerrors`
--
DROP TABLE IF EXISTS `emailerrors`;
CREATE TABLE `emailerrors` (
`EmailErrorID` int(11) NOT NULL auto_increment,
`FromEmail` text NOT NULL,
`ToEmail` text NOT NULL,
`Subject` varchar(128) NOT NULL default '',
`Body` text NOT NULL,
`ErrorDate` timestamp(14) NOT NULL,
`ExceptionError` text,
PRIMARY KEY (`EmailErrorID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`emailerrors`
--
/*!40000 ALTER TABLE `emailerrors` DISABLE KEYS */;
/*!40000 ALTER TABLE `emailerrors` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`ethnicities`
--
DROP TABLE IF EXISTS `ethnicities`;
CREATE TABLE `ethnicities` (
`EthnicID` tinyint(4) NOT NULL auto_increment,
`EthnicName` varchar(50) NOT NULL default '',
PRIMARY KEY (`EthnicID`)
) TYPE=MyISAM COMMENT='static';
--
-- Dumping data for table `dating_db`.`ethnicities`
--
/*!40000 ALTER TABLE `ethnicities` DISABLE KEYS */;
INSERT INTO `ethnicities` (`EthnicID`,`EthnicName`) VALUES
(1,'asian'),
(2,'black / african'),
(3,'hispanic / latino'),
(4,'indian / south asian'),
(5,'middle eastern / arab'),
(6,'native american'),
(7,'pacific islander'),
(8,'white / caucasian'),
(9,'mixed'),
(10,'other');
/*!40000 ALTER TABLE `ethnicities` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`favorites`
--
DROP TABLE IF EXISTS `favorites`;
CREATE TABLE `favorites` (
`RecordID` int(10) unsigned NOT NULL auto_increment,
`ProfileID` int(10) unsigned NOT NULL default '0',
`FavoriteID` int(10) unsigned NOT NULL default '0',
`MutualFavorite` tinyint(1) NOT NULL default '0',
PRIMARY KEY (`RecordID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`favorites`
--
/*!40000 ALTER TABLE `favorites` DISABLE KEYS */;
/*!40000 ALTER TABLE `favorites` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`genders`
--
DROP TABLE IF EXISTS `genders`;
CREATE TABLE `genders` (
`GenderID` tinyint(3) unsigned NOT NULL auto_increment,
`GenderName` tinytext NOT NULL,
PRIMARY KEY (`GenderID`)
) TYPE=MyISAM COMMENT='static';
--
-- Dumping data for table `dating_db`.`genders`
--
/*!40000 ALTER TABLE `genders` DISABLE KEYS */;
INSERT INTO `genders` (`GenderID`,`GenderName`) VALUES
(1,'female'),
(2,'male'),
(3,'transgender(ftm)'),
(4,'transgender(mtf)');
/*!40000 ALTER TABLE `genders` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`messageblocks`
--
DROP TABLE IF EXISTS `messageblocks`;
CREATE TABLE `messageblocks` (
`RecordID` int(10) unsigned NOT NULL auto_increment,
`ProfileID` int(10) unsigned NOT NULL default '0',
`BlockID` int(10) unsigned NOT NULL default '0',
PRIMARY KEY (`RecordID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`messageblocks`
--
/*!40000 ALTER TABLE `messageblocks` DISABLE KEYS */;
/*!40000 ALTER TABLE `messageblocks` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`messages`
--
DROP TABLE IF EXISTS `messages`;
CREATE TABLE `messages` (
`MessageID` int(10) unsigned NOT NULL auto_increment,
`MessageDate` datetime NOT NULL default '0000-00-00 00:00:00',
`SenderID` int(10) unsigned NOT NULL default '0',
`RecipientID` int(10) unsigned NOT NULL default '0',
`Subject` varchar(128) default '',
`Body` text NOT NULL,
`MessageRead` tinyint(1) default '0',
`DeletedByRecipient` tinyint(1) default '0',
`DeletedBySender` tinyint(1) default '0',
PRIMARY KEY (`MessageID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`messages`
--
/*!40000 ALTER TABLE `messages` DISABLE KEYS */;
/*!40000 ALTER TABLE `messages` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`neighborhoods`
--
DROP TABLE IF EXISTS `neighborhoods`;
CREATE TABLE `neighborhoods` (
`NeighborhoodID` tinyint(3) unsigned NOT NULL auto_increment,
`NeighborhoodName` tinytext NOT NULL,
PRIMARY KEY (`NeighborhoodID`)
) TYPE=MyISAM COMMENT='static';
--
-- Dumping data for table `dating_db`.`neighborhoods`
--
/*!40000 ALTER TABLE `neighborhoods` DISABLE KEYS */;
INSERT INTO `neighborhoods` (`NeighborhoodID`,`NeighborhoodName`) VALUES
(1,'bayview / hunter\'s point'),
(2,'bernal heights'),
(3,'castro / eureka valley'),
(4,'chinatown'),
(5,'cole valley'),
(6,'excelsior / outer mission'),
(7,'financial district'),
(8,'glen park'),
(9,'haight ashbury'),
(10,'hayes valley'),
(11,'ingleside / merced / ocean view (SFSU,CCSF)'),
(12,'inner richmond'),
(13,'inner sunset / parnassus heights (UCSF)'),
(14,'laurel heights / presidio'),
(15,'lower haight / fillmore'),
(16,'marina / cow hollow'),
(17,'mission district'),
(18,'nob hill'),
(19,'noe valley'),
(20,'north beach / telegraph hill'),
(21,'pacific heights'),
(22,'panhandle (USF)'),
(23,'potrero hill / dogpatch'),
(24,'richmond / seacliff'),
(25,'russian hill'),
(26,'soma / south beach / mission bay'),
(27,'sunset / parkside'),
(28,'tenderloin / civic center'),
(29,'tendernob'),
(30,'twin peaks / diamond heights'),
(31,'visitacion valley / sunnydale / portola'),
(32,'west portal / st. francis wood / forest hill'),
(33,'western addition / japantown');
INSERT INTO `neighborhoods` (`NeighborhoodID`,`NeighborhoodName`) VALUES
(34,'East Bay'),
(35,'North Bay'),
(36,'Peninsula'),
(37,'South Bay');
/*!40000 ALTER TABLE `neighborhoods` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`photos`
--
DROP TABLE IF EXISTS `photos`;
CREATE TABLE `photos` (
`PhotoID` int(10) unsigned NOT NULL auto_increment,
`ProfileID` int(10) unsigned NOT NULL default '0',
`PhotoFilename` varchar(40) NOT NULL default '',
`Caption` varchar(255) default NULL,
PRIMARY KEY (`PhotoID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`photos`
--
/*!40000 ALTER TABLE `photos` DISABLE KEYS */;
/*!40000 ALTER TABLE `photos` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`profiles`
--
DROP TABLE IF EXISTS `profiles`;
CREATE TABLE `profiles` (
`ProfileID` int(10) unsigned NOT NULL auto_increment,
`UserName` varchar(16) NOT NULL default '',
`Password` varchar(32) NOT NULL default '',
`Email` text NOT NULL,
`GenderID` tinyint(3) NOT NULL default '0',
`Age` tinyint(3) NOT NULL default '0',
`SexualOrientationID` tinyint(3) default '0',
`SignID` tinyint(3) default '0',
`Height` tinyint(3) default '0',
`BodyTypeID` tinyint(3) default '0',
`EthnicID` tinyint(4) default '0',
`NeighborhoodID` tinyint(3) default '0',
`AboutMe` text,
`WantActivityPartner` tinyint(1) default '0',
`WantFriend` tinyint(1) default '0',
`WantDate` tinyint(1) default '0',
`WantLTR` tinyint(1) default '0',
`ForwardMessages` tinyint(1) default '0',
`ImageName` varchar(40) default NULL,
`ImageCaption` varchar(255) default NULL,
`CreationDate` datetime default '0000-00-00 00:00:00',
`ModificationDate` datetime default '0000-00-00 00:00:00',
`LoginDate` datetime default '0000-00-00 00:00:00',
`ActivationCode` varchar(16) default '0',
`ProfileStatusID` tinyint(3) unsigned NOT NULL default '1',
PRIMARY KEY (`ProfileID`)
) TYPE=MyISAM;
--
-- Dumping data for table `dating_db`.`profiles`
--
/*!40000 ALTER TABLE `profiles` DISABLE KEYS */;
/*!40000 ALTER TABLE `profiles` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`profilestatuses`
--
DROP TABLE IF EXISTS `profilestatuses`;
CREATE TABLE `profilestatuses` (
`ProfileStatusID` tinyint(3) unsigned NOT NULL auto_increment,
`ProfileStatusName` tinytext NOT NULL,
PRIMARY KEY (`ProfileStatusID`)
) TYPE=MyISAM COMMENT='static';
--
-- Dumping data for table `dating_db`.`profilestatuses`
--
/*!40000 ALTER TABLE `profilestatuses` DISABLE KEYS */;
INSERT INTO `profilestatuses` (`ProfileStatusID`,`ProfileStatusName`) VALUES
(1,'pending activation'),
(2,'active'),
(3,'suspended'),
(4,'deleted');
/*!40000 ALTER TABLE `profilestatuses` ENABLE KEYS */;
--
-- Table structure for table `dating_db`.`sexualorientations`
--
DROP TABLE IF EXISTS `sexualorientations`;
CREATE TABLE `sexualorientations` (
`SexualOrientationID` tinyint(3) unsigned NOT NULL auto_increment,
`SexualOrientationName` tinytext NOT NULL,
PRIMARY KEY (`SexualOrientationID`)
) TYPE=MyISAM COMMENT='static';
--
-- Dumping data for table `dating_db`.`sexualorientations`
--
/*!40000 ALTER TABLE `sexualorientations` DISABLE KEYS */;
INSERT INTO `sexualorientations` (`SexualOrientationID`,`SexualOrientationName`) VALUES
(1,'straight'),
(2,'gay/lesbian'),
(3,'bisexual');
/*!40000 ALTER TABLE `sexualorientations` ENABLE KEYS */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
---------------------
robin
|
|
|
|
|
I just went through this exercise myself - a but of discovery plus trial and error. If you are used to the way MySQL works then you'll find SQL Server a different because most of the manual things we do in MySql like create databases and tables is done through graphical tools. One hot tip is the closest thing to writing SQL procedures like you do for MySQL is using iSQLW. You can enter SQL there but the syntax is slighty different.
For creating tables, the EnterpriseManager is the primary tool you use to create the database and design the table(s). Although with the proper privilege you can create a database through Visual Studio Server connections - although that's a quick a dirty way.
Lastly you need to know about Data Transformation Services (DTS) which is used for all import and exports of data. It has a broad choice of formats but alas no option for MySql option 
Bottom line, if you have a lot of data in MySQL expect to get to know DTS and massaging the data.
Good Luck
Mike Luster
CTI/IVR/Telephony SME
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
