Do SQL 7 CALs count for a SQL 2000 install?

Hi,
I have a client with SQL 7 and they need to go to SQL 2000 via an upgrade to
run their now updated app. Do their existing SQL 7 CALs allow then to access
the SQL 2000 server or do they have to buy all the CALs again. Or maybe there
is some upgrade price.
Their vendor has priced 60 SQL 200 CALs at £8,100.00 - which isnt too cheap(!)
Thanks.From the server EULA:
"Any CAL must have the same or later version number than the corresponding
version number of the Server Software being used."
http://www.microsoft.com/sql/howtobuy/default.asp
Ask the vendor about upgrade pricing.
--
David Portas
SQL Server MVP
--

Do SQL 7 CALs count for a SQL 2000 install?

Hi,
I have a client with SQL 7 and they need to go to SQL 2000 via an upgrade to
run their now updated app. Do their existing SQL 7 CALs allow then to access
the SQL 2000 server or do they have to buy all the CALs again. Or maybe ther
e
is some upgrade price.
Their vendor has priced 60 SQL 200 CALs at ￡8,100.00 - which isnt too cheap
(!)
Thanks.From the server EULA:
"Any CAL must have the same or later version number than the corresponding
version number of the Server Software being used."
http://www.microsoft.com/sql/howtobuy/default.asp
Ask the vendor about upgrade pricing.
David Portas
SQL Server MVP
--

Do SQL 7 CALs count for a SQL 2000 install?

Hi,
I have a client with SQL 7 and they need to go to SQL 2000 via an upgrade to
run their now updated app. Do their existing SQL 7 CALs allow then to access
the SQL 2000 server or do they have to buy all the CALs again. Or maybe there
is some upgrade price.
Their vendor has priced 60 SQL 200 CALs at ￡8,100.00 - which isnt too cheap(!)
Thanks.
From the server EULA:
"Any CAL must have the same or later version number than the corresponding
version number of the Server Software being used."
http://www.microsoft.com/sql/howtobuy/default.asp
Ask the vendor about upgrade pricing.
David Portas
SQL Server MVP

DMO restore problem

I have a C++ app that is using SQLDMO with SqlServer2000. I am Restoring a database using only the .bak file, moving the .mdf and .ldf files. The following is the code:

#ifdef USE_SQLDMO
try
{
if(m_cpServer == NULL)
return E_FAIL;

_RestorePtr cpRestore;
CheckError(cpRestore.CreateInstance(_T("SQLDMO.Restore")));
cpRestore->Action = SQLDMORestore_Database;
cpRestore->Database = _bstr_t(sDbName);
cpRestore->Files = _bstr_t(sBUFile);
cpRestore->LastRestore = false;
cpRestore->ReplaceDatabase = true;
cpRestore->PercentCompleteNotification= 10;
RestoreSinkPtr cpSinkPtr;
//get data path for current server
GetSQLDataPath(sDataPath);
QueryResultsPtr cpFileList;
cpFileList = cpRestore->ReadFileList( m_cpServer);
//get info to change for move from cpFileList and move items
for(int i = 1; i <= cpFileList->Rows; i++)
{
_bstr_t bstrLogicalName = cpFileList->GetColumnString(i,1);
sLogicalName = (LPCTSTR)bstrLogicalName;
sLogicalName.Trim();
_bstr_t bstrPhysicalName = cpFileList->GetColumnString(i,2);
sPhysicalName = (LPCTSTR)bstrPhysicalName;
sPhysicalName.MakeUpper();
if(sPhysicalName.Find(".MDF") > 0)
{
sPhysicalName = sDataPath + "\\" + sDbName;
sFiles.Format("%i",nDatafiles);
if(nDatafiles == 0)
sPhysicalName += ".mdf";
else
sPhysicalName += "_" + sFiles + ".mdf";

nDatafiles++;
}
else if(sPhysicalName.Find(".LDF") > 0)
{
sFiles.Format("%i",nLogFiles);
sPhysicalName = sDataPath + "\\" + sDbName;
if(nLogFiles == 0)
sPhysicalName += ".ldf";
else
sPhysicalName += "_" + sFiles + ".ldf";

nLogFiles++;
}
sNew += "[" + sLogicalName + "],[" + sPhysicalName + "],";
}
sNew = sNew.Left(sNew.GetLength()-1);
sPhysicalName = (LPCTSTR)bstrPhysicalName;

cpRestore->SQLRestore( m_cpServer);
cpRestore->SQLVerify(m_cpServer);
cpRestore = NULL;
bSuccess = true;
}
catch(_com_error& err)
{
PrintComError(err);
PrintProviderError(m_cpServer);
hr = err.Error();
}
#endif

The problem is that the functions appears to work. The Restore command does not return and error and neither does the verify. When I open enterprise manager, the database created but is greyed out and shows a status of loading but never completes.
Any ideas/help would be greatly appreciated.

Sandy

I haven't tried your script, but I suspect that the LastRestore=false is the culprit, as this indicates that this is not the last backup on the restore chain and keeps the database in a loading state as it is expecting a final log backup will be applied.

DMO restore problem

I have a C++ app that is using SQLDMO with SqlServer2000. I am Restoring a database using only the .bak file, moving the .mdf and .ldf files. The following is the code:

#ifdef USE_SQLDMO
try
{
if(m_cpServer == NULL)
return E_FAIL;
_RestorePtr cpRestore;
CheckError(cpRestore.CreateInstance(_T("SQLDMO.Restore")));
cpRestore->Action = SQLDMORestore_Database;
cpRestore->Database = _bstr_t(sDbName);
cpRestore->Files = _bstr_t(sBUFile);
cpRestore->LastRestore = false;
cpRestore->ReplaceDatabase = true;
cpRestore->PercentCompleteNotification= 10;
RestoreSinkPtr cpSinkPtr;
//get data path for current server
GetSQLDataPath(sDataPath);
QueryResultsPtr cpFileList;
cpFileList = cpRestore->ReadFileList( m_cpServer);
//get info to change for move from cpFileList and move items
for(int i = 1; i <= cpFileList->Rows; i++)
{
_bstr_t bstrLogicalName = cpFileList->GetColumnString(i,1);
sLogicalName = (LPCTSTR)bstrLogicalName;
sLogicalName.Trim();
_bstr_t bstrPhysicalName = cpFileList->GetColumnString(i,2);
sPhysicalName = (LPCTSTR)bstrPhysicalName;
sPhysicalName.MakeUpper();
if(sPhysicalName.Find(".MDF") > 0)
{
sPhysicalName = sDataPath + "\\" + sDbName;
sFiles.Format("%i",nDatafiles);
if(nDatafiles == 0)
sPhysicalName += ".mdf";
else
sPhysicalName += "_" + sFiles + ".mdf";

nDatafiles++;
}
else if(sPhysicalName.Find(".LDF") > 0)
{
sFiles.Format("%i",nLogFiles);
sPhysicalName = sDataPath + "\\" + sDbName;
if(nLogFiles == 0)
sPhysicalName += ".ldf";
else
sPhysicalName += "_" + sFiles + ".ldf";

nLogFiles++;
}
sNew += "[" + sLogicalName + "],[" + sPhysicalName + "],";
}
sNew = sNew.Left(sNew.GetLength()-1);
sPhysicalName = (LPCTSTR)bstrPhysicalName;
cpRestore->SQLRestore( m_cpServer);
cpRestore->SQLVerify(m_cpServer);
cpRestore = NULL;
bSuccess = true;
}
catch(_com_error& err)
{
PrintComError(err);
PrintProviderError(m_cpServer);
hr = err.Error();
}
#endif

The problem is that the functions appears to work. The Restore command does not return and error and neither does the verify. When I open enterprise manager, the database created but is greyed out and shows a status of loading but never completes.
Any ideas/help would be greatly appreciated.

Sandy

I haven't tried your script, but I suspect that the LastRestore=false is the culprit, as this indicates that this is not the last backup on the restore chain and keeps the database in a loading state as it is expecting a final log backup will be applied.

DMO doesn't work with SQL Server 2005 (Express)?

I have an applications that uses DMO to access SQL Server 2000.
When I tried to run that app against SQL Server 2005 Express CTP,
I got the below error:
Error
[Microsoft][ODBC SQL Server Driver][SQL Server]
To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO)
OK
Any idea what I'm missing here?
Thanks,
Sarah
DMO is not supported on SQL2005. You need to use SMO.
Chris Wood
"Sarah" <SarahBram@.HotMail.com> wrote in message
news:%23xZE7FzrFHA.904@.tk2msftngp13.phx.gbl...
>I have an applications that uses DMO to access SQL Server 2000.
> When I tried to run that app against SQL Server 2005 Express CTP,
> I got the below error:
> --
> Error
> --
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> To connect to this server you must use SQL Server Management Studio or SQL
> Server Management Objects (SMO)
> --
> OK
> --
> Any idea what I'm missing here?
> Thanks,
> Sarah
|||Hello Chris,
If I complie in SMO will it be backward compatible with SQL 2000 or do I
need to include both in my applications?
Regards,
John
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:OZiB6lzrFHA.248@.TK2MSFTNGP14.phx.gbl...
> DMO is not supported on SQL2005. You need to use SMO.
> Chris Wood
> "Sarah" <SarahBram@.HotMail.com> wrote in message
> news:%23xZE7FzrFHA.904@.tk2msftngp13.phx.gbl...
>
|||Chris Wood wrote:
> DMO is not supported on SQL2005. You need to use SMO.
> Chris Wood
Chris,
There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
Microsoft decided they didn't want to make upgrading DMO apps any more
difficult than they needed to be. The new SQL-DMO is supposed to work
with SQL 2000 and 7. I'm not sure when it will be available for
download if you're not a beta member.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||David,
Hopefully the new version of DMO comes with the September CTP and before the
RTM (Gold) build.
Thanks
Chris
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:Om36c$zrFHA.3596@.TK2MSFTNGP15.phx.gbl...
> Chris Wood wrote:
> Chris,
> There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
> Microsoft decided they didn't want to make upgrading DMO apps any more
> difficult than they needed to be. The new SQL-DMO is supposed to work with
> SQL 2000 and 7. I'm not sure when it will be available for download if
> you're not a beta member.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
|||David,
Did this make it with the September CTP?
Chris
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:Om36c$zrFHA.3596@.TK2MSFTNGP15.phx.gbl...
> Chris Wood wrote:
> Chris,
> There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
> Microsoft decided they didn't want to make upgrading DMO apps any more
> difficult than they needed to be. The new SQL-DMO is supposed to work with
> SQL 2000 and 7. I'm not sure when it will be available for download if
> you're not a beta member.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

DMO doesn't work with SQL Server 2005 (Express)?

I have an applications that uses DMO to access SQL Server 2000.
When I tried to run that app against SQL Server 2005 Express CTP,
I got the below error:
--
Error
--
[Microsoft][ODBC SQL Server Driver][SQL Server]
To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO)
--
OK
--
Any idea what I'm missing here?
Thanks,
SarahDMO is not supported on SQL2005. You need to use SMO.
Chris Wood
"Sarah" <SarahBram@.HotMail.com> wrote in message
news:%23xZE7FzrFHA.904@.tk2msftngp13.phx.gbl...
>I have an applications that uses DMO to access SQL Server 2000.
> When I tried to run that app against SQL Server 2005 Express CTP,
> I got the below error:
> --
> Error
> --
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> To connect to this server you must use SQL Server Management Studio or SQL
> Server Management Objects (SMO)
> --
> OK
> --
> Any idea what I'm missing here?
> Thanks,
> Sarah|||Hello Chris,
If I complie in SMO will it be backward compatible with SQL 2000 or do I
need to include both in my applications?
Regards,
John
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:OZiB6lzrFHA.248@.TK2MSFTNGP14.phx.gbl...
> DMO is not supported on SQL2005. You need to use SMO.
> Chris Wood
> "Sarah" <SarahBram@.HotMail.com> wrote in message
> news:%23xZE7FzrFHA.904@.tk2msftngp13.phx.gbl...
>>I have an applications that uses DMO to access SQL Server 2000.
>> When I tried to run that app against SQL Server 2005 Express CTP,
>> I got the below error:
>> --
>> Error
>> --
>> [Microsoft][ODBC SQL Server Driver][SQL Server]
>> To connect to this server you must use SQL Server Management Studio or
>> SQL Server Management Objects (SMO)
>> --
>> OK
>> --
>> Any idea what I'm missing here?
>> Thanks,
>> Sarah
>|||Chris Wood wrote:
> DMO is not supported on SQL2005. You need to use SMO.
> Chris Wood
Chris,
There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
Microsoft decided they didn't want to make upgrading DMO apps any more
difficult than they needed to be. The new SQL-DMO is supposed to work
with SQL 2000 and 7. I'm not sure when it will be available for
download if you're not a beta member.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||David,
Hopefully the new version of DMO comes with the September CTP and before the
RTM (Gold) build.
Thanks
Chris
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:Om36c$zrFHA.3596@.TK2MSFTNGP15.phx.gbl...
> Chris Wood wrote:
>> DMO is not supported on SQL2005. You need to use SMO.
>> Chris Wood
> Chris,
> There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
> Microsoft decided they didn't want to make upgrading DMO apps any more
> difficult than they needed to be. The new SQL-DMO is supposed to work with
> SQL 2000 and 7. I'm not sure when it will be available for download if
> you're not a beta member.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||David,
Did this make it with the September CTP?
Chris
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:Om36c$zrFHA.3596@.TK2MSFTNGP15.phx.gbl...
> Chris Wood wrote:
>> DMO is not supported on SQL2005. You need to use SMO.
>> Chris Wood
> Chris,
> There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
> Microsoft decided they didn't want to make upgrading DMO apps any more
> difficult than they needed to be. The new SQL-DMO is supposed to work with
> SQL 2000 and 7. I'm not sure when it will be available for download if
> you're not a beta member.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

DMO doesn't work with SQL Server 2005 (Express)?

I have an applications that uses DMO to access SQL Server 2000.
When I tried to run that app against SQL Server 2005 Express CTP,
I got the below error:
Error
--
[Microsoft][ODBC SQL Server Driver][SQL Server]
To connect to this server you must use SQL Server Management Studio or SQL S
erver Management Objects (SMO)
--
OK
--
Any idea what I'm missing here?
Thanks,
SarahDMO is not supported on SQL2005. You need to use SMO.
Chris Wood
"Sarah" <SarahBram@.HotMail.com> wrote in message
news:%23xZE7FzrFHA.904@.tk2msftngp13.phx.gbl...
>I have an applications that uses DMO to access SQL Server 2000.
> When I tried to run that app against SQL Server 2005 Express CTP,
> I got the below error:
> --
> Error
> --
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> To connect to this server you must use SQL Server Management Studio or SQL
> Server Management Objects (SMO)
> --
> OK
> --
> Any idea what I'm missing here?
> Thanks,
> Sarah|||Hello Chris,
If I complie in SMO will it be backward compatible with SQL 2000 or do I
need to include both in my applications?
Regards,
John
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:OZiB6lzrFHA.248@.TK2MSFTNGP14.phx.gbl...
> DMO is not supported on SQL2005. You need to use SMO.
> Chris Wood
> "Sarah" <SarahBram@.HotMail.com> wrote in message
> news:%23xZE7FzrFHA.904@.tk2msftngp13.phx.gbl...
>|||Chris Wood wrote:
> DMO is not supported on SQL2005. You need to use SMO.
> Chris Wood
Chris,
There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
Microsoft decided they didn't want to make upgrading DMO apps any more
difficult than they needed to be. The new SQL-DMO is supposed to work
with SQL 2000 and 7. I'm not sure when it will be available for
download if you're not a beta member.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||David,
Hopefully the new version of DMO comes with the September CTP and before the
RTM (Gold) build.
Thanks
Chris
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:Om36c$zrFHA.3596@.TK2MSFTNGP15.phx.gbl...
> Chris Wood wrote:
> Chris,
> There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
> Microsoft decided they didn't want to make upgrading DMO apps any more
> difficult than they needed to be. The new SQL-DMO is supposed to work with
> SQL 2000 and 7. I'm not sure when it will be available for download if
> you're not a beta member.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||David,
Did this make it with the September CTP?
Chris
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:Om36c$zrFHA.3596@.TK2MSFTNGP15.phx.gbl...
> Chris Wood wrote:
> Chris,
> There is a SQL Server DMO in Beta now for SQL Server 2005. I'm guessing
> Microsoft decided they didn't want to make upgrading DMO apps any more
> difficult than they needed to be. The new SQL-DMO is supposed to work with
> SQL 2000 and 7. I'm not sure when it will be available for download if
> you're not a beta member.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

DMO Distribution Question

I have a .NET app that uses SQL-DMO. Before I put this app on a users
machine, I need to know what, if any, DMO install files I need to put on the
users machine. I'm already including the Interop.SQLDMO.dll file with my app
but is there anything else I need to install?
Thanks very much."Amos Soma" <amos_j_soma@.yahoo.com> wrote in
news:#KmhN#xgGHA.4368@.TK2MSFTNGP03.phx.gbl:

> I have a .NET app that uses SQL-DMO. Before I put this app on a users
> machine, I need to know what, if any, DMO install files I need to put
> on the users machine. I'm already including the Interop.SQLDMO.dll
> file with my app but is there anything else I need to install?
> Thanks very much.
>
>
Check out the following URLs:
http://support.microsoft.com/defaul...kb;en-us;258157
http://support.microsoft.com/kb/248241/en-us
The first one is geared toward the VB developer. The second is a good
overall rundown of the redistribution process for SQL-DMO.
Good Luck
*~!NumbLock!~*

Distribution licensing

Hi
If I write app with a sql server as backend, what are the licensing
requirements for distribution of the app sql server wise i.e. does the
client need to buy their on sql server ort can I distribute parts of it as
part of my app? I need to use Merge Replication so I doubt I can distribute
the app with sql server express.
Thanks
Regards
If you use SQL Server Express or MSDE you do not need to have licenses on
the subscribers, but you will need to license the publisher for every
connection made to it. So if you have 300 subscribers you will need 300
Calls.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John" <John@.nospam.infovis.co.uk> wrote in message
news:%23GIlwXpKIHA.4752@.TK2MSFTNGP05.phx.gbl...
> Hi
> If I write app with a sql server as backend, what are the licensing
> requirements for distribution of the app sql server wise i.e. does the
> client need to buy their on sql server ort can I distribute parts of it as
> part of my app? I need to use Merge Replication so I doubt I can
> distribute the app with sql server express.
> Thanks
> Regards
>
>
>
>

Distribution licensing

Hi
If I write app with a sql server as backend, what are the licensing
requirements for distribution of the app sql server wise i.e. does the
client need to buy their on sql server ort can I distribute parts of it as
part of my app? I need to use Merge Replication so I doubt I can distribute
the app with sql server express.
Thanks
RegardsIf you use SQL Server Express or MSDE you do not need to have licenses on
the subscribers, but you will need to license the publisher for every
connection made to it. So if you have 300 subscribers you will need 300
Calls.
--
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John" <John@.nospam.infovis.co.uk> wrote in message
news:%23GIlwXpKIHA.4752@.TK2MSFTNGP05.phx.gbl...
> Hi
> If I write app with a sql server as backend, what are the licensing
> requirements for distribution of the app sql server wise i.e. does the
> client need to buy their on sql server ort can I distribute parts of it as
> part of my app? I need to use Merge Replication so I doubt I can
> distribute the app with sql server express.
> Thanks
> Regards
>
>
>
>

Distribution licensing

Hi
If I write app with a sql server as backend, what are the licensing
requirements for distribution of the app sql server wise i.e. does the
client need to buy their on sql server ort can I distribute parts of it as
part of my app? I need to use Merge Replication so I doubt I can distribute
the app with sql server express.
Thanks
RegardsIf you use SQL Server Express or MSDE you do not need to have licenses on
the subscribers, but you will need to license the publisher for every
connection made to it. So if you have 300 subscribers you will need 300
Calls.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John" <John@.nospam.infovis.co.uk> wrote in message
news:%23GIlwXpKIHA.4752@.TK2MSFTNGP05.phx.gbl...
> Hi
> If I write app with a sql server as backend, what are the licensing
> requirements for distribution of the app sql server wise i.e. does the
> client need to buy their on sql server ort can I distribute parts of it as
> part of my app? I need to use Merge Replication so I doubt I can
> distribute the app with sql server express.
> Thanks
> Regards
>
>
>
>

Distribution licensing

Hi
If I write app with a sql server as backend, what are the licensing
requirements for distribution of the app sql server wise i.e. does the
client need to buy their on sql server ort can I distribute parts of it as
part of my app? I need to use Merge Replication so I doubt I can distribute
the app with sql server express.
Thanks
Regards
If you use SQL Server Express or MSDE you do not need to have licenses on
the subscribers, but you will need to license the publisher for every
connection made to it. So if you have 300 subscribers you will need 300
Calls.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John" <John@.nospam.infovis.co.uk> wrote in message
news:%23GIlwXpKIHA.4752@.TK2MSFTNGP05.phx.gbl...
> Hi
> If I write app with a sql server as backend, what are the licensing
> requirements for distribution of the app sql server wise i.e. does the
> client need to buy their on sql server ort can I distribute parts of it as
> part of my app? I need to use Merge Replication so I doubt I can
> distribute the app with sql server express.
> Thanks
> Regards
>
>
>
>

Distributing database with app

Sorry if this something beaten to death already...

What is/should be required for a target client machine to use and connect to a local copy of a SqlExpress database? Can't seem to get a db connection established to a different machine through a VB6 app. Installed the sql native client on the machine, but still can't connect. What am I missing, or do I have to distribute/install the entire SqlExpress client? Working fine from my development machine.

Rick

If you are connecting via TCP/IP you have to enable these protocols. You also have to ensure to enable remote connections.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||I'm not using a remote connection. It's a local copy of the database. What simply does the target deployment machine require or in order for the VB app to connect to the db?

|||The deployment machine needs a Data access components like MDAC or SQL Native Client, both the app machine and the database machine must be able to negotiate to a common protocol like TCP/IP. If that is used you have to allow remote connections on the database server and if you are using another port than 1433 either specify that in your connecting string like MachineName\SQLExpress,Portnumber or start SQL Browser on the database server which will automatically redirect the request to the appropiate port.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||Thanks Jens. I don't quite understand what you're saying with remote connections. There is no database machine. This is all starting to sound like every target machine for my application requires SqlExpress be installed on that machine, or a server that machine is connected to. Is this correct or not?

|||

Do you have SQL Express installed anywhere?

You must have a SQL Server running in order to access your data. There are two basic models to do this:

Local Data Access - SQL Express is installed on the same computer with the application. Each user has thier own copy of the database installed on their computer and data is not shared. This is the configuration for a single user application.|||Mike ... I was speaking of Local access (and think I used the term "local" a few times). All I've been asking is -- must SqlExpress be installed a client machine, be it local or server? Apparently, the answer is yes, which complicates distribution and installation by end-users who won't have a clue. I was under the mistaken impression it was not unlike distributing an Access mdb file. I'm clear on this point now. Thanks.

Now I'm trying to understand more on User Instance usage:

If not specified in the connection string, what is the default, yes or no?
For shared multiuser usage located on a server, should it be enabled or not?

I'm just unclear on when/when not to use it.

TIA ... Rick

|||If you don′t uise the user instance keyword you use SQL Server Exprtess just as a normal database. If you want to attach the database to a SQL Server instance you don′t need to use User instance availbility. Just attach the db to a SQL Servert (Express) and connect via the "normal* connection string to it (without specifying something like user instance)

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||

Hi Rick,

Regarding User Instances:

If you don't specify it in the connection string, User Instances are not used.

Distributing Data with an App

I have developed an application which will be distributed. I know how to
create a SQL script which will create the table structure for the DB. Is
there an easy/recommended way to export the default data from my tables in a
way which will be easy and/or automatic for the installer to load into their
DB after the tables are created?
I could write C# into my app which will notice empty tables and populate
them but this seems tedious. Is there a better way?
thanks
charles
You could BCP or BULK COPY your data or you could create insert statements
with a tool like one of these:
ObjectScripter -- http://www.rac4sql.net/
QALite -- http://www.rac4sql.net/
Lockwood Tech -- http://www.lockwoodtech.com/
Largo SQL Tools -- http://www.largosqltools.com/ (seems to be under
construction at the moment)
Keith
"charles" <spam@.synthigence.com> wrote in message
news:eoeNK4AnEHA.556@.tk2msftngp13.phx.gbl...
> I have developed an application which will be distributed. I know how to
> create a SQL script which will create the table structure for the DB. Is
> there an easy/recommended way to export the default data from my tables in
a
> way which will be easy and/or automatic for the installer to load into
their
> DB after the tables are created?
> I could write C# into my app which will notice empty tables and populate
> them but this seems tedious. Is there a better way?
> thanks
> charles
>
|||Thank you so much... QALite looks like it does exactly what I need,
creating a SQL INSERTs script from my existing data
charles
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:epWH5BBnEHA.3472@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> You could BCP or BULK COPY your data or you could create insert statements
> with a tool like one of these:
> ObjectScripter -- http://www.rac4sql.net/
> QALite -- http://www.rac4sql.net/
> Lockwood Tech -- http://www.lockwoodtech.com/
> Largo SQL Tools -- http://www.largosqltools.com/ (seems to be under
> construction at the moment)
> --
> Keith
>
> "charles" <spam@.synthigence.com> wrote in message
> news:eoeNK4AnEHA.556@.tk2msftngp13.phx.gbl...
to[vbcol=seagreen]
Is[vbcol=seagreen]
in
> a
> their
>

Distributing Data with an App

I have developed an application which will be distributed. I know how to
create a SQL script which will create the table structure for the DB. Is
there an easy/recommended way to export the default data from my tables in a
way which will be easy and/or automatic for the installer to load into their
DB after the tables are created?
I could write C# into my app which will notice empty tables and populate
them but this seems tedious. Is there a better way?
thanks
charlesYou could BCP or BULK COPY your data or you could create insert statements
with a tool like one of these:
ObjectScripter -- http://www.rac4sql.net/
QALite -- http://www.rac4sql.net/
Lockwood Tech -- http://www.lockwoodtech.com/
Largo SQL Tools -- http://www.largosqltools.com/ (seems to be under
construction at the moment)
--
Keith
"charles" <spam@.synthigence.com> wrote in message
news:eoeNK4AnEHA.556@.tk2msftngp13.phx.gbl...
> I have developed an application which will be distributed. I know how to
> create a SQL script which will create the table structure for the DB. Is
> there an easy/recommended way to export the default data from my tables in
a
> way which will be easy and/or automatic for the installer to load into
their
> DB after the tables are created?
> I could write C# into my app which will notice empty tables and populate
> them but this seems tedious. Is there a better way?
> thanks
> charles
>|||Thank you so much... QALite looks like it does exactly what I need,
creating a SQL INSERTs script from my existing data
charles
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:epWH5BBnEHA.3472@.TK2MSFTNGP09.phx.gbl...
> You could BCP or BULK COPY your data or you could create insert statements
> with a tool like one of these:
> ObjectScripter -- http://www.rac4sql.net/
> QALite -- http://www.rac4sql.net/
> Lockwood Tech -- http://www.lockwoodtech.com/
> Largo SQL Tools -- http://www.largosqltools.com/ (seems to be under
> construction at the moment)
> --
> Keith
>
> "charles" <spam@.synthigence.com> wrote in message
> news:eoeNK4AnEHA.556@.tk2msftngp13.phx.gbl...
> > I have developed an application which will be distributed. I know how
to
> > create a SQL script which will create the table structure for the DB.
Is
> > there an easy/recommended way to export the default data from my tables
in
> a
> > way which will be easy and/or automatic for the installer to load into
> their
> > DB after the tables are created?
> >
> > I could write C# into my app which will notice empty tables and populate
> > them but this seems tedious. Is there a better way?
> >
> > thanks
> > charles
> >
> >
>

Distributing Data of MSDE-Apps

Hi there,
I wonder, how to distribute an MSDE-Application with some
default database and data in it.
E.g. i need to ship my app with the database that contains
some tables and some tables may contain initial data.
How can I do that ?
hi Roger,
"Roger" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:744001c494d4$1eb766d0$a501280a@.phx.gbl...
> Hi there,
> I wonder, how to distribute an MSDE-Application with some
> default database and data in it.
> E.g. i need to ship my app with the database that contains
> some tables and some tables may contain initial data.
> How can I do that ?
Microsoft provides a deployment toolkit, in release candidate at the current
time, you can dowload from
http://www.microsoft.com/downloads/d...displaylang=en
I did not installed it, but I think some database deployment feature are
present... and some drawbacks of this toolkit have been posted here... don't
know the current state and/or the final release...
personally I do deploy apps with a companion tool which will read and
execute DDL scripts as long as INSERT INTO scipts, BCP and so on.. other
ways are backup/restore and sp_attach_db
I already disccused these 3 methods in http://tinyurl.com/6ux7p and
http://tinyurl.com/4x8pv ...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Distributed Scenario...

Hi ,
We're building a windows app and using SQL 2005.
The scenario is this.
Our app will be spread across various geographical locations.
The information is more or less location specific i.e. a user in one
loaction will probably not require to see/modify the data in another
location. We are looking at huge volumes of data and the connectivity
could be pretty decent.
Do we
1. Go with one centralised server?
2. Go with a server for each location.
In this scenario what would be the impact on the cost.
3. Go with Point 2 but also have one centralised server which will sink
up data from all locations. Is this suggested? If so does SQL server
have some kind of automatic sync utility or services which can be say
run at a particular time?
4. I do not have much info on Mirroring but will this help if I were to
use a centralised server.?
Thanks in advance
Soni
I cant be certain without having some more info regarding size and req for
your scenario. I would probably use option 3 and yes, you can maintain
centralised server through replication or SSIS or some other feature
depending on your needs.
As for the 4) Mirroring will not be available untill mid 2006 and it could
help, again depending on what would you want to do on the centralised
server...
MC
"hangar18" <soni.somarajan@.wipro.com> wrote in message
news:1133250860.462491.247260@.f14g2000cwb.googlegr oups.com...
> Hi ,
> We're building a windows app and using SQL 2005.
> The scenario is this.
> Our app will be spread across various geographical locations.
> The information is more or less location specific i.e. a user in one
> loaction will probably not require to see/modify the data in another
> location. We are looking at huge volumes of data and the connectivity
> could be pretty decent.
> Do we
> 1. Go with one centralised server?
> 2. Go with a server for each location.
> In this scenario what would be the impact on the cost.
> 3. Go with Point 2 but also have one centralised server which will sink
> up data from all locations. Is this suggested? If so does SQL server
> have some kind of automatic sync utility or services which can be say
> run at a particular time?
> 4. I do not have much info on Mirroring but will this help if I were to
> use a centralised server.?
> Thanks in advance
> Soni
>

Distributed Scenario...

Hi ,
We're building a windows app and using SQL 2005.
The scenario is this.
Our app will be spread across various geographical locations.
The information is more or less location specific i.e. a user in one
loaction will probably not require to see/modify the data in another
location. We are looking at huge volumes of data and the connectivity
could be pretty decent.
Do we
1. Go with one centralised server?
2. Go with a server for each location.
In this scenario what would be the impact on the cost.
3. Go with Point 2 but also have one centralised server which will sink
up data from all locations. Is this suggested? If so does SQL server
have some kind of automatic sync utility or services which can be say
run at a particular time?
4. I do not have much info on Mirroring but will this help if I were to
use a centralised server.?
Thanks in advance
SoniI cant be certain without having some more info regarding size and req for
your scenario. I would probably use option 3 and yes, you can maintain
centralised server through replication or SSIS or some other feature
depending on your needs.
As for the 4) Mirroring will not be available untill mid 2006 and it could
help, again depending on what would you want to do on the centralised
server...
MC
"hangar18" <soni.somarajan@.wipro.com> wrote in message
news:1133250860.462491.247260@.f14g2000cwb.googlegroups.com...
> Hi ,
> We're building a windows app and using SQL 2005.
> The scenario is this.
> Our app will be spread across various geographical locations.
> The information is more or less location specific i.e. a user in one
> loaction will probably not require to see/modify the data in another
> location. We are looking at huge volumes of data and the connectivity
> could be pretty decent.
> Do we
> 1. Go with one centralised server?
> 2. Go with a server for each location.
> In this scenario what would be the impact on the cost.
> 3. Go with Point 2 but also have one centralised server which will sink
> up data from all locations. Is this suggested? If so does SQL server
> have some kind of automatic sync utility or services which can be say
> run at a particular time?
> 4. I do not have much info on Mirroring but will this help if I were to
> use a centralised server.?
> Thanks in advance
> Soni
>

Distributed Scenario...

Hi ,
We're building a windows app and using SQL 2005.
The scenario is this.
Our app will be spread across various geographical locations.
The information is more or less location specific i.e. a user in one
loaction will probably not require to see/modify the data in another
location. We are looking at huge volumes of data and the connectivity
could be pretty decent.
Do we
1. Go with one centralised server?
2. Go with a server for each location.
In this scenario what would be the impact on the cost.
3. Go with Point 2 but also have one centralised server which will sink
up data from all locations. Is this suggested? If so does SQL server
have some kind of automatic sync utility or services which can be say
run at a particular time?
4. I do not have much info on Mirroring but will this help if I were to
use a centralised server.?
Thanks in advance
SoniI cant be certain without having some more info regarding size and req for
your scenario. I would probably use option 3 and yes, you can maintain
centralised server through replication or SSIS or some other feature
depending on your needs.
As for the 4) Mirroring will not be available untill mid 2006 and it could
help, again depending on what would you want to do on the centralised
server...
MC
"hangar18" <soni.somarajan@.wipro.com> wrote in message
news:1133250860.462491.247260@.f14g2000cwb.googlegroups.com...
> Hi ,
> We're building a windows app and using SQL 2005.
> The scenario is this.
> Our app will be spread across various geographical locations.
> The information is more or less location specific i.e. a user in one
> loaction will probably not require to see/modify the data in another
> location. We are looking at huge volumes of data and the connectivity
> could be pretty decent.
> Do we
> 1. Go with one centralised server?
> 2. Go with a server for each location.
> In this scenario what would be the impact on the cost.
> 3. Go with Point 2 but also have one centralised server which will sink
> up data from all locations. Is this suggested? If so does SQL server
> have some kind of automatic sync utility or services which can be say
> run at a particular time?
> 4. I do not have much info on Mirroring but will this help if I were to
> use a centralised server.?
> Thanks in advance
> Soni
>