Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts

Wednesday, March 28, 2012

Help on sql server 2005 express

I'm using sql server 2005 express edition on a HP Pavillon machine with windows vista

when I conect the computer to a network the database engine spends about 30 minutes in a query an when is not conected it takes only one second.

What mast i do to correct this problem ?

Thanks

Max.

SQL Server 2005 Express is designed for local connection. For remote connection, you need to purchase SQL Server 2005.

Wednesday, March 7, 2012

Help Needed - How Can I Set Up a Backup SQL Server Machine as an Exact Copy of My Producti

Any help would be greatly appreciated.

My problem is that I need to set up a backup SQL Server 2000 machine
which can be used in case of a failure to my primary. All databases
(30 as of now) must be an up to the minute exact copy of production
and include most recent changes in data as well as any structure
changes (Tables, Views, SP's, Triggers, Users . . etc).

When I tried this using Transactional Replication, the replication
process gets fouled up once I introduce any kind of structure changes
to the DB. I've considered the idea of doing periodic backups and
restoring it to my backup SQL server, but this does not give me the
concurrency needed with 0 latency.

I've seen articles that recommend using Transaction Replication with
'Scheduled Table Refresh', and also doing database dumps to restore on
the backup machine, but I have not been able to find any documentation
regarding this to try out. How can I implement this type of backup
strategy in SQL 2000?"Michael Orlando" <mjorlando@.campsystems.com> wrote in message
news:354e82fa.0310301256.12671603@.posting.google.c om...
> Any help would be greatly appreciated.
> My problem is that I need to set up a backup SQL Server 2000 machine
> which can be used in case of a failure to my primary. All databases
> (30 as of now) must be an up to the minute exact copy of production
> and include most recent changes in data as well as any structure
> changes (Tables, Views, SP's, Triggers, Users . . etc).

Clustering.

Though technically that's not a copy.

> When I tried this using Transactional Replication, the replication
> process gets fouled up once I introduce any kind of structure changes
> to the DB. I've considered the idea of doing periodic backups and
> restoring it to my backup SQL server, but this does not give me the
> concurrency needed with 0 latency.

If you use transactional replication you have to use sp_repladdcolumn and
sp_repldropcolumn for adding dropping columns. All other schema changes
generally have to be run against both copies.

Note also there's no guarantee as to the latency that Transactional
replication will introduce.

Log shipping will allow exact copies, but again with a built in latency.

I'd recommend picking up "SQL Server 2000 High Availability " from MS Press
and reading that.

> I've seen articles that recommend using Transaction Replication with
> 'Scheduled Table Refresh', and also doing database dumps to restore on
> the backup machine, but I have not been able to find any documentation
> regarding this to try out. How can I implement this type of backup
> strategy in SQL 2000?|||mjorlando@.campsystems.com (Michael Orlando) wrote in message news:<354e82fa.0310301256.12671603@.posting.google.com>...
> Any help would be greatly appreciated.
> My problem is that I need to set up a backup SQL Server 2000 machine
> which can be used in case of a failure to my primary. All databases
> (30 as of now) must be an up to the minute exact copy of production
> and include most recent changes in data as well as any structure
> changes (Tables, Views, SP's, Triggers, Users . . etc).
> When I tried this using Transactional Replication, the replication
> process gets fouled up once I introduce any kind of structure changes
> to the DB. I've considered the idea of doing periodic backups and
> restoring it to my backup SQL server, but this does not give me the
> concurrency needed with 0 latency.
> I've seen articles that recommend using Transaction Replication with
> 'Scheduled Table Refresh', and also doing database dumps to restore on
> the backup machine, but I have not been able to find any documentation
> regarding this to try out. How can I implement this type of backup
> strategy in SQL 2000?

What exactly do you mean by 'up to the minute'? The only other
'instant' alternative to transactional replication is clustering,
which would also avoid your schema change issues.

I don't know much about replication myself, so you might want to post
to microsoft.public.sqlserver.replication with your backup question.
Also, have a look at the October 2003 issue of SQL Server Magazine,
which had a number of articles on various high-availability solutions.

Simon

Friday, February 24, 2012

help me Please!

Hi There!!

I have a code that runs from a different machine and a different site and i am facing a problem that i can not log in to the database.I installed SQL Server on my machine and I created a user "fadila" and SQL Server Authentication and the password is "fadil1977" and the database is "otters" and it is installed as tables and stored procedures but there is not data on these tables.

I used the method provided in the code so, i only change the "connStr" in one place rather than in 20 places and my code is as below. Can you please Help me to connect to the database. I Really..Really appreciate it if you help me to solve it as it causeing me a big head-ache and still get the error message "SQL Server does not exist or access denied" .. please help!!!!


Friend Shared ReadOnly Property connStr() As String

Get
Return String.Format( _

"Data Source={0};Initial Catalog=Otters;User ID=fadila;Password=fadil1977", _

DatabaseMachine)

End Get
End Property


your help is appreciated!!!!!!Sure you can connect to the sql server?

Possible reasons:

* Firewall in between.
* Stupid admin. One who did not read that syou need a special service pack (SP3?) to run on 2003, and Winwodows Server 2003 actively blocks SQL Server ports unless this sp is installewd (at least).
* Bad setup for the network, not allowing name resolution.
* Bad database machine name?

Do you homework - there is nothing we can do here to help you, simply because we have no clue what the error is, simply because you do not provide enough info.|||Hi Thona!!

Thank you very much for your help and answering my question. You just said there is no enough information provided, can you please tell me what information is needed so i can post up for you. I just want to make one point, I used before in the previous project the dataset and connect to the database without any problem so, is that what you told me, it does not apply to the dataset and SqlAdaptor as it is a different way toconnect so, i will not have this problem.

I will speak to the IT admin about the you told me and get back to you so, please keep looking to this thread until you solve it for me or you get fed up :)

Thanks again