How to insert record to SQL server which is on the other machine from client computer?

I want to write simple sql database project that that works in the network. and i need to insert record from a client to a server that is on the other machine.

This is a pretty broad question. I suggest you do some additional research online or via any one of a number of excellent books, articles or whitepapers.

This will require that you (at least)

Install and configure the SQL Server on the remote system.

How to improve the query performance on cubes?

Hi,all experts here,

How could we effectively improve the query performance on cubes from a client? Can we create indexes on them? Or if not, what else can we try?

Thanks a lot and I am looking forward to hearing from you shortly.

With best regards,

Yours sincerely,

There are a lot of things to try - partitioning, aggregations.... too much to discuss in a forums answer. Your best bet is to read the AS performance guide:

http://www.microsoft.com/technet/prodtechnol/sql/2005/ssas2005perfguide.mspx

Chris

|||

Thanks a lot.

Best regards,

sql

How to import a database structure only from SQL Server 2000

Hi

I have to work offsite from the client offices and their main database requires restructuring e.g. they currently have over 10 indexes on most tables and up to 38 on some (ouch)

Could someone recommend the tools to enable me to download the database structure (no data transfer) and the relationship between the tables to help me restructure the database?

Thanks in advance

Hi,

You have several options to accomplish this task. You can use SSIS to copy database objects, create a database script through the EM or SSMS, or use the Database Publishing wizard from http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Database%20Publishing%20Wizard&referringTitle=Home

Regards,

Janos

How To Implement sql server database on the client's computer?

Hello,
I finished my vb.net application, the application uses sql server and run pretty well on my pc. Now I want to install this application on the customer's computer, and the issue I'm not sure about is, what do I need to install on the client's computer concerning the database?
Do I install SQL Server and restore the database there? how to secure the database and make sure nobody will be able to edit the data from Enterprise Manager. What if someone uninstalled SQL Server?

Please I need help in this issue since I'm a beginner.

Thanks.

Quote:

Originally Posted by Tea Maker

Hello,
I finished my vb.net application, the application uses sql server and run pretty well on my pc. Now I want to install this application on the customer's computer, and the issue I'm not sure about is, what do I need to install on the client's computer concerning the database?
Do I install SQL Server and restore the database there? how to secure the database and make sure nobody will be able to edit the data from Enterprise Manager. What if someone uninstalled SQL Server?

Please I need help in this issue since I'm a beginner.

Thanks.

You will need to install SQL Server on your customer's server (or just his/her computer if they're the only person that will be using it). As for security, you'll need to set up database users and set their permissions accordingly. Obviously you'll need to change your app to reflect the change of database location.|||

Quote:

Originally Posted by DonlonP

You will need to install SQL Server on your customer's server (or just his/her computer if they're the only person that will be using it). As for security, you'll need to set up database users and set their permissions accordingly. Obviously you'll need to change your app to reflect the change of database location.

If I set users permissions then nobody will be able to open the database? because I've tried this before, but anyone can access the database through Enterprise Manager without username and password? And what about if someone uninstalled sql server?
I'll be thanksfull if you provide me some links where I can read articles about this issue because I couldn't find any related articles.

Thanks|||

Quote:

Originally Posted by Tea Maker

If I set users permissions then nobody will be able to open the database? because I've tried this before, but anyone can access the database through Enterprise Manager without username and password? And what about if someone uninstalled sql server?
I'll be thanksfull if you provide me some links where I can read articles about this issue because I couldn't find any related articles.

Thanks

On second thoughts you don't even need to set user permissions if you install SQL Server 2000 desktop edition (which is free!) this doesn't come with enterprise manager anyway. Download from:
http://www.microsoft.com/downloads/...&displaylang=en
Obviously if someone uninstalled SQL Server then you wouldn't have a database and your app wouldn't work, and the person who uninstalled it would be a complete muppet!|||

Quote:

Originally Posted by DonlonP

On second thoughts you don't even need to set user permissions if you install SQL Server 2000 desktop edition (which is free!) this doesn't come with enterprise manager anyway. Download from:
http://www.microsoft.com/downloads/...&displaylang=en
Obviously if someone uninstalled SQL Server then you wouldn't have a database and your app wouldn't work, and the person who uninstalled it would be a complete muppet!

Wow, Thanks alot that helped me out so much.
Just one more question, How can I transfer the database from my computer to the other, do I create a backup and restore it there? and where do I place my databases.

How to implement Database Mirroring with SQL2000

Hi,
Our client is located in Europe region. Our application was a web based
application using SQL Server 2000 database as the back-end, where this server
was located in Europe region. All the users will visit this site through out
the world.
Now the client was observing some performance problems in their offices in
Asia region. The reason seems to be a relatively bad connection between
Europe and Asia. The available bandwidth should be by far sufficient (10
Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client is
checking with other providers, but they may have similar problems. The effect
is that the measured response times in their Asian office are too long
(typically 3 – 5 seconds). Their target is to get response times below 2
seconds to make sure that the users can work efficiently.
One possible solution which has been suggested to us was that to install the
web based application also on a server in the Asian office. There would be 2
mirrored databases with the same data. The users in Asia would access this
server, whereas the users in Europe and America would access the server in
Europe. Probably it would be sufficient to update the data once a day or even
less frequently.
Does SQL Server 2000 support such a solution? Do you think this would be a
feasible solution? If this solution should be implemented, how should we
proceed?
Or else Can you suggest any other solution?
Thanks and Regards
ourspt
ourspt
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
Yes it does. It could be SNAPSHOT Replication to update tthe database or
just simple BACKUP and RESTORE database
But regarding to where the server should be located it is your decision and
do some testing
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"ourspt" <ourspt@.discussions.microsoft.com> wrote in message
news:BAA5A573-735B-449F-90BD-9DB6A54D3D10@.microsoft.com...
> Hi,
> Our client is located in Europe region. Our application was a web based
> application using SQL Server 2000 database as the back-end, where this
> server
> was located in Europe region. All the users will visit this site through
> out
> the world.
> Now the client was observing some performance problems in their offices in
> Asia region. The reason seems to be a relatively bad connection between
> Europe and Asia. The available bandwidth should be by far sufficient (10
> Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client
> is
> checking with other providers, but they may have similar problems. The
> effect
> is that the measured response times in their Asian office are too long
> (typically 3 5 seconds). Their target is to get response times below 2
> seconds to make sure that the users can work efficiently.
> One possible solution which has been suggested to us was that to install
> the
> web based application also on a server in the Asian office. There would be
> 2
> mirrored databases with the same data. The users in Asia would access this
> server, whereas the users in Europe and America would access the server in
> Europe. Probably it would be sufficient to update the data once a day or
> even
> less frequently.
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
> Or else Can you suggest any other solution?
> Thanks and Regards
> --
> ourspt

How to implement Database Mirroring with SQL2000

Hi,
Our client is located in Europe region. Our application was a web based
application using SQL Server 2000 database as the back-end, where this serve
r
was located in Europe region. All the users will visit this site through out
the world.
Now the client was observing some performance problems in their offices in
Asia region. The reason seems to be a relatively bad connection between
Europe and Asia. The available bandwidth should be by far sufficient (10
Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client i
s
checking with other providers, but they may have similar problems. The effec
t
is that the measured response times in their Asian office are too long
(typically 3 – 5 seconds). Their target is to get response times below 2
seconds to make sure that the users can work efficiently.
One possible solution which has been suggested to us was that to install the
web based application also on a server in the Asian office. There would be 2
mirrored databases with the same data. The users in Asia would access this
server, whereas the users in Europe and America would access the server in
Europe. Probably it would be sufficient to update the data once a day or eve
n
less frequently.
Does SQL Server 2000 support such a solution? Do you think this would be a
feasible solution? If this solution should be implemented, how should we
proceed?
Or else Can you suggest any other solution?
Thanks and Regards
--
oursptourspt
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
Yes it does. It could be SNAPSHOT Replication to update tthe database or
just simple BACKUP and RESTORE database
But regarding to where the server should be located it is your decision and
do some testing
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"ourspt" <ourspt@.discussions.microsoft.com> wrote in message
news:BAA5A573-735B-449F-90BD-9DB6A54D3D10@.microsoft.com...
> Hi,
> Our client is located in Europe region. Our application was a web based
> application using SQL Server 2000 database as the back-end, where this
> server
> was located in Europe region. All the users will visit this site through
> out
> the world.
> Now the client was observing some performance problems in their offices in
> Asia region. The reason seems to be a relatively bad connection between
> Europe and Asia. The available bandwidth should be by far sufficient (10
> Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client
> is
> checking with other providers, but they may have similar problems. The
> effect
> is that the measured response times in their Asian office are too long
> (typically 3 5 seconds). Their target is to get response times below 2
> seconds to make sure that the users can work efficiently.
> One possible solution which has been suggested to us was that to install
> the
> web based application also on a server in the Asian office. There would be
> 2
> mirrored databases with the same data. The users in Asia would access this
> server, whereas the users in Europe and America would access the server in
> Europe. Probably it would be sufficient to update the data once a day or
> even
> less frequently.
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
> Or else Can you suggest any other solution?
> Thanks and Regards
> --
> ourspt

How to implement Database Mirroring with SQL2000

Hi,
Our client is located in Europe region. Our application was a web based
application using SQL Server 2000 database as the back-end, where this server
was located in Europe region. All the users will visit this site through out
the world.
Now the client was observing some performance problems in their offices in
Asia region. The reason seems to be a relatively bad connection between
Europe and Asia. The available bandwidth should be by far sufficient (10
Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client is
checking with other providers, but they may have similar problems. The effect
is that the measured response times in their Asian office are too long
(typically 3 â' 5 seconds). Their target is to get response times below 2
seconds to make sure that the users can work efficiently.
One possible solution which has been suggested to us was that to install the
web based application also on a server in the Asian office. There would be 2
mirrored databases with the same data. The users in Asia would access this
server, whereas the users in Europe and America would access the server in
Europe. Probably it would be sufficient to update the data once a day or even
less frequently.
Does SQL Server 2000 support such a solution? Do you think this would be a
feasible solution? If this solution should be implemented, how should we
proceed?
Or else Can you suggest any other solution?
Thanks and Regards
--
oursptourspt
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
Yes it does. It could be SNAPSHOT Replication to update tthe database or
just simple BACKUP and RESTORE database
But regarding to where the server should be located it is your decision and
do some testing
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"ourspt" <ourspt@.discussions.microsoft.com> wrote in message
news:BAA5A573-735B-449F-90BD-9DB6A54D3D10@.microsoft.com...
> Hi,
> Our client is located in Europe region. Our application was a web based
> application using SQL Server 2000 database as the back-end, where this
> server
> was located in Europe region. All the users will visit this site through
> out
> the world.
> Now the client was observing some performance problems in their offices in
> Asia region. The reason seems to be a relatively bad connection between
> Europe and Asia. The available bandwidth should be by far sufficient (10
> Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client
> is
> checking with other providers, but they may have similar problems. The
> effect
> is that the measured response times in their Asian office are too long
> (typically 3 ? 5 seconds). Their target is to get response times below 2
> seconds to make sure that the users can work efficiently.
> One possible solution which has been suggested to us was that to install
> the
> web based application also on a server in the Asian office. There would be
> 2
> mirrored databases with the same data. The users in Asia would access this
> server, whereas the users in Europe and America would access the server in
> Europe. Probably it would be sufficient to update the data once a day or
> even
> less frequently.
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
> Or else Can you suggest any other solution?
> Thanks and Regards
> --
> ourspt

How to identify unused databases

Hi Folks,
client company has around 25 sql servers .
Each server has got 5 to 10 databases.
Some of the databases are old.
We don't know whether any applications using old databases or not.
Is there any way we can find the unused databases in past 3 months or past 1
year
using some Lastupdatedatetime or last action on sql server system tables
using T-SQL scripts.
If no application is accessing the database and no actions performed on
that database from past 1 year then we need to delete that databases.
How to identify unused databases?
Any kind of help is greatly appreciated.
Thanks
KumarKumar wrote:
> Hi Folks,
> client company has around 25 sql servers .
> Each server has got 5 to 10 databases.
> Some of the databases are old.
> We don't know whether any applications using old databases or not.
> Is there any way we can find the unused databases in past 3 months or
> past 1 year
> using some Lastupdatedatetime or last action on sql server system
> tables using T-SQL scripts.
> If no application is accessing the database and no actions performed
> on that database from past 1 year then we need to delete that
> databases.
> How to identify unused databases?
> Any kind of help is greatly appreciated.
> Thanks
> Kumar
You can create a trace on the server. Include only the SQL:StmtStarting
and RPC:Starting events. Include only the minimum number of columns:
EventClass, SPID, DatabaseID. You could exclude system databases like
master, msdb, and tempdb.
To cut down the rows a little, you could use SQL:BatchStarting, but if a
batch has "USE" statements and accesses more than one database, the
DatabaseID will only refer to the database that was used at execution
time.
If you let the trace run for a couple of hours (or a day or two), you
should have a pretty good picture of what databases were accessed on
each server.
Best to do this using a server-side trace which you can script from
Profiler using the File - Script Trace menu option and stopping manually
using sp_trace_setstatus.
David Gugick
Quest Software
www.imceda.com
www.quest.com