Showing posts with label order. Show all posts
Showing posts with label order. Show all posts

Tuesday, March 27, 2012

Database Snapshots & Reporting

We are looking at mirroring some of our databases to a remote location
and snapshotting those databases in order to report off them.
One of Microsofts recommendations is to add a time suffix to the
snapshotname in order to identify the age of the snapshot.
Any reporting system is going to use a DSN to connect to the snapshot,
we intend to snapshot frequently in order to keep the data as fresh as
possible. Does this not mean that the DSN is going to need to change to
point to the latest snapshot database?
The only alternative I can think of is to sp_renamedb the existing
snapshot 'dbsnap' to 'dbsnap_old' and then create a new snapshot with
the original name.
This is a superb feature and a great selling point for 2005.
Has anyone implemented this ? and if so how did you overcome this
problem.
Kind Regards & Thanks.
An update for anyone else who has this problem, we have found a
possible solution.
If your application uses DSNs
You can create a number of of file DSNs relevant to the snapshot name
e.g.
appdb_1200.dsn
appdb_1800.dsn
appdb_0000.dsn
appdb_0600.dsn
Have your application use a DSN named appdb.dsn, and after creating the
snapshot database, do an xp_cmdshell to copy the relevant file over the
top of the appdb.dsn on the application server.
This allows your application to use a consistent DSN Name, but you are
cycling the DSNs with regards to the snapshot.
You can do the same thing if you use system DSNs as these are stored in
the registry.
Check out the following page
http://www.microsoft.com/technet/scriptcenter/resources/qanda/nov04/hey1110.mspx
If you use a connection string hardcoded into the app, I guess you
could use the system views to determine the latest snapshot, or
populate a 'latest snapshot' table and build your connection string
dynamically based on that.
Hope this helps someone out there.
sqldood@.googlemail.com wrote:
> We are looking at mirroring some of our databases to a remote location
> and snapshotting those databases in order to report off them.
> One of Microsofts recommendations is to add a time suffix to the
> snapshotname in order to identify the age of the snapshot.
> Any reporting system is going to use a DSN to connect to the snapshot,
> we intend to snapshot frequently in order to keep the data as fresh as
> possible. Does this not mean that the DSN is going to need to change to
> point to the latest snapshot database?
> The only alternative I can think of is to sp_renamedb the existing
> snapshot 'dbsnap' to 'dbsnap_old' and then create a new snapshot with
> the original name.
> This is a superb feature and a great selling point for 2005.
> Has anyone implemented this ? and if so how did you overcome this
> problem.
> Kind Regards & Thanks.

Database Snapshots & Reporting

We are looking at mirroring some of our databases to a remote location
and snapshotting those databases in order to report off them.
One of Microsofts recommendations is to add a time suffix to the
snapshotname in order to identify the age of the snapshot.
Any reporting system is going to use a DSN to connect to the snapshot,
we intend to snapshot frequently in order to keep the data as fresh as
possible. Does this not mean that the DSN is going to need to change to
point to the latest snapshot database?
The only alternative I can think of is to sp_renamedb the existing
snapshot 'dbsnap' to 'dbsnap_old' and then create a new snapshot with
the original name.
This is a superb feature and a great selling point for 2005.
Has anyone implemented this ? and if so how did you overcome this
problem.
Kind Regards & Thanks.An update for anyone else who has this problem, we have found a
possible solution.
If your application uses DSNs
You can create a number of of file DSNs relevant to the snapshot name
e.g.
appdb_1200.dsn
appdb_1800.dsn
appdb_0000.dsn
appdb_0600.dsn
Have your application use a DSN named appdb.dsn, and after creating the
snapshot database, do an xp_cmdshell to copy the relevant file over the
top of the appdb.dsn on the application server.
This allows your application to use a consistent DSN Name, but you are
cycling the DSNs with regards to the snapshot.
You can do the same thing if you use system DSNs as these are stored in
the registry.
Check out the following page
http://www.microsoft.com/technet/scriptcenter/resources/qanda/nov04/hey1110.mspx
If you use a connection string hardcoded into the app, I guess you
could use the system views to determine the latest snapshot, or
populate a 'latest snapshot' table and build your connection string
dynamically based on that.
Hope this helps someone out there.
sqldood@.googlemail.com wrote:
> We are looking at mirroring some of our databases to a remote location
> and snapshotting those databases in order to report off them.
> One of Microsofts recommendations is to add a time suffix to the
> snapshotname in order to identify the age of the snapshot.
> Any reporting system is going to use a DSN to connect to the snapshot,
> we intend to snapshot frequently in order to keep the data as fresh as
> possible. Does this not mean that the DSN is going to need to change to
> point to the latest snapshot database?
> The only alternative I can think of is to sp_renamedb the existing
> snapshot 'dbsnap' to 'dbsnap_old' and then create a new snapshot with
> the original name.
> This is a superb feature and a great selling point for 2005.
> Has anyone implemented this ? and if so how did you overcome this
> problem.
> Kind Regards & Thanks.

Database Snapshots & Reporting

We are looking at mirroring some of our databases to a remote location
and snapshotting those databases in order to report off them.
One of Microsofts recommendations is to add a time suffix to the
snapshotname in order to identify the age of the snapshot.
Any reporting system is going to use a DSN to connect to the snapshot,
we intend to snapshot frequently in order to keep the data as fresh as
possible. Does this not mean that the DSN is going to need to change to
point to the latest snapshot database?
The only alternative I can think of is to sp_renamedb the existing
snapshot 'dbsnap' to 'dbsnap_old' and then create a new snapshot with
the original name.
This is a superb feature and a great selling point for 2005.
Has anyone implemented this ? and if so how did you overcome this
problem.
Kind Regards & Thanks.An update for anyone else who has this problem, we have found a
possible solution.
If your application uses DSNs
You can create a number of of file DSNs relevant to the snapshot name
e.g.
appdb_1200.dsn
appdb_1800.dsn
appdb_0000.dsn
appdb_0600.dsn
Have your application use a DSN named appdb.dsn, and after creating the
snapshot database, do an xp_cmdshell to copy the relevant file over the
top of the appdb.dsn on the application server.
This allows your application to use a consistent DSN Name, but you are
cycling the DSNs with regards to the snapshot.
You can do the same thing if you use system DSNs as these are stored in
the registry.
Check out the following page
[url]http://www.microsoft.com/technet/scriptcenter/resources/qanda/nov04/hey1110.mspx[/
url]
If you use a connection string hardcoded into the app, I guess you
could use the system views to determine the latest snapshot, or
populate a 'latest snapshot' table and build your connection string
dynamically based on that.
Hope this helps someone out there.
sqldood@.googlemail.com wrote:
> We are looking at mirroring some of our databases to a remote location
> and snapshotting those databases in order to report off them.
> One of Microsofts recommendations is to add a time suffix to the
> snapshotname in order to identify the age of the snapshot.
> Any reporting system is going to use a DSN to connect to the snapshot,
> we intend to snapshot frequently in order to keep the data as fresh as
> possible. Does this not mean that the DSN is going to need to change to
> point to the latest snapshot database?
> The only alternative I can think of is to sp_renamedb the existing
> snapshot 'dbsnap' to 'dbsnap_old' and then create a new snapshot with
> the original name.
> This is a superb feature and a great selling point for 2005.
> Has anyone implemented this ? and if so how did you overcome this
> problem.
> Kind Regards & Thanks.sql

Wednesday, March 7, 2012

database restore error

Hello
when i try to restore the wss database in sql, i am getting following error.
any idea?
Warning: The join order has been enforced because a local join hint is used
Using STSADM
regards
Gopi
Hi
This looks like there are Hash//Merge join hints are being used as described
in
http://msdn.microsoft.com/library/de...fa-fz_4ox9.asp
The warning is for information.
John
"Gopi" <gopigopi@.hotmail.com> wrote in message
news:uNlysBnHGHA.2704@.TK2MSFTNGP15.phx.gbl...
> Hello
> when i try to restore the wss database in sql, i am getting following
> error. any idea?
>
> Warning: The join order has been enforced because a local join hint is
> used
> Using STSADM
>
> regards
> Gopi
>

database restore error

Hello
when i try to restore the wss database in sql, i am getting following error.
any idea?
Warning: The join order has been enforced because a local join hint is used
Using STSADM
regards
GopiHi
This looks like there are Hash//Merge join hints are being used as described
in
4ox9.asp" target="_blank">http://msdn.microsoft.com/library/d...br />
4ox9.asp
The warning is for information.
John
"Gopi" <gopigopi@.hotmail.com> wrote in message
news:uNlysBnHGHA.2704@.TK2MSFTNGP15.phx.gbl...
> Hello
> when i try to restore the wss database in sql, i am getting following
> error. any idea?
>
> Warning: The join order has been enforced because a local join hint is
> used
> Using STSADM
>
> regards
> Gopi
>

database restore error

Hello
when i try to restore the wss database in sql, i am getting following error.
any idea?
Warning: The join order has been enforced because a local join hint is used
Using STSADM
regards
GopiHi
This looks like there are Hash//Merge join hints are being used as described
in
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_fa-fz_4ox9.asp
The warning is for information.
John
"Gopi" <gopigopi@.hotmail.com> wrote in message
news:uNlysBnHGHA.2704@.TK2MSFTNGP15.phx.gbl...
> Hello
> when i try to restore the wss database in sql, i am getting following
> error. any idea?
>
> Warning: The join order has been enforced because a local join hint is
> used
> Using STSADM
>
> regards
> Gopi
>

database restore - msdb

Hi, In the event of a system crash, whereby the whole server had to be
re-built, how would I best restore the msdb database, in order to restore
all DTS's which I had?Hi Ben,
Please read the following article and you will find answers
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
HTH
Andreas
"Ben Rum" wrote:
> Hi, In the event of a system crash, whereby the whole server had to be
> re-built, how would I best restore the msdb database, in order to restore
> all DTS's which I had?
>
>|||Ben:
You can simply restore msdb from a backup that you have made as long as no
one is using it. That really means to just stop the SQL Server Agent
process and restore the database and then start the Agent back up. Works
like a champ (I actually had to do it this weekend due to a server failure).
One issue though is to remember to press your F5 key to refresh your view in
EM or you may end up giving yourself an unnecessary heart attack.
See the following if you want/need it straight from Microsoft:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
Scott
"Ben Rum" <bundyrum75@.yahoo.com> wrote in message
news:u6NVFYJiFHA.2472@.TK2MSFTNGP15.phx.gbl...
> Hi, In the event of a system crash, whereby the whole server had to be
> re-built, how would I best restore the msdb database, in order to restore
> all DTS's which I had?
>

database restore - msdb

Hi, In the event of a system crash, whereby the whole server had to be
re-built, how would I best restore the msdb database, in order to restore
all DTS's which I had?
Hi Ben,
Please read the following article and you will find answers
http://support.microsoft.com/default...b;en-us;224071
HTH
Andreas
"Ben Rum" wrote:

> Hi, In the event of a system crash, whereby the whole server had to be
> re-built, how would I best restore the msdb database, in order to restore
> all DTS's which I had?
>
>
|||Ben:
You can simply restore msdb from a backup that you have made as long as no
one is using it. That really means to just stop the SQL Server Agent
process and restore the database and then start the Agent back up. Works
like a champ (I actually had to do it this weekend due to a server failure).
One issue though is to remember to press your F5 key to refresh your view in
EM or you may end up giving yourself an unnecessary heart attack.
See the following if you want/need it straight from Microsoft:
http://msdn.microsoft.com/library/de...kprst_2w1f.asp
Scott
"Ben Rum" <bundyrum75@.yahoo.com> wrote in message
news:u6NVFYJiFHA.2472@.TK2MSFTNGP15.phx.gbl...
> Hi, In the event of a system crash, whereby the whole server had to be
> re-built, how would I best restore the msdb database, in order to restore
> all DTS's which I had?
>

database restore - msdb

Hi, In the event of a system crash, whereby the whole server had to be
re-built, how would I best restore the msdb database, in order to restore
all DTS's which I had?Hi Ben,
Please read the following article and you will find answers
http://support.microsoft.com/defaul...kb;en-us;224071
HTH
Andreas
"Ben Rum" wrote:

> Hi, In the event of a system crash, whereby the whole server had to be
> re-built, how would I best restore the msdb database, in order to restore
> all DTS's which I had?
>
>|||Ben:
You can simply restore msdb from a backup that you have made as long as no
one is using it. That really means to just stop the SQL Server Agent
process and restore the database and then start the Agent back up. Works
like a champ (I actually had to do it this weekend due to a server failure).
One issue though is to remember to press your F5 key to refresh your view in
EM or you may end up giving yourself an unnecessary heart attack.
See the following if you want/need it straight from Microsoft:
http://msdn.microsoft.com/library/d... />
t_2w1f.asp
Scott
"Ben Rum" <bundyrum75@.yahoo.com> wrote in message
news:u6NVFYJiFHA.2472@.TK2MSFTNGP15.phx.gbl...
> Hi, In the event of a system crash, whereby the whole server had to be
> re-built, how would I best restore the msdb database, in order to restore
> all DTS's which I had?
>

Friday, February 24, 2012

Database question...

I have a database that was on a SQL Server that failed. The data file is
intact
but I need to bring it up. What steps do I need to do in order to attach
this to
another SQL Server with the plan of maving it back to the original server
once we
get the server rebuilt.
Any help would be greatly appreciated.You might be able to use sp_attach_db of you have all the files that constitutes the database. A
database backup file is better (RESTORE DATABASE). You also need to make sure that login exists at
the new server (and other stuff needed in the system databases) and then handle login to use mapping
(sp_change_users_login).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:EA95EEE6-1FD6-41E8-A65E-7F8A647A7D55@.microsoft.com...
>I have a database that was on a SQL Server that failed. The data file is
> intact
> but I need to bring it up. What steps do I need to do in order to attach
> this to
> another SQL Server with the plan of maving it back to the original server
> once we
> get the server rebuilt.
> Any help would be greatly appreciated.|||If your data file is intact, you can try sp_attach_single_file_db too...
"Joe" wrote:
> I have a database that was on a SQL Server that failed. The data file is
> intact
> but I need to bring it up. What steps do I need to do in order to attach
> this to
> another SQL Server with the plan of maving it back to the original server
> once we
> get the server rebuilt.
> Any help would be greatly appreciated.

Database question...

I have a database that was on a SQL Server that failed. The data file is
intact
but I need to bring it up. What steps do I need to do in order to attach
this to
another SQL Server with the plan of maving it back to the original server
once we
get the server rebuilt.
Any help would be greatly appreciated.
If your data file is intact, you can try sp_attach_single_file_db too...
"Joe" wrote:

> I have a database that was on a SQL Server that failed. The data file is
> intact
> but I need to bring it up. What steps do I need to do in order to attach
> this to
> another SQL Server with the plan of maving it back to the original server
> once we
> get the server rebuilt.
> Any help would be greatly appreciated.

Database question...

I have a database that was on a SQL Server that failed. The data file is
intact
but I need to bring it up. What steps do I need to do in order to attach
this to
another SQL Server with the plan of maving it back to the original server
once we
get the server rebuilt.
Any help would be greatly appreciated.You might be able to use sp_attach_db of you have all the files that constit
utes the database. A
database backup file is better (RESTORE DATABASE). You also need to make sur
e that login exists at
the new server (and other stuff needed in the system databases) and then han
dle login to use mapping
(sp_change_users_login).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:EA95EEE6-1FD6-41E8-A65E-7F8A647A7D55@.microsoft.com...
>I have a database that was on a SQL Server that failed. The data file is
> intact
> but I need to bring it up. What steps do I need to do in order to attach
> this to
> another SQL Server with the plan of maving it back to the original server
> once we
> get the server rebuilt.
> Any help would be greatly appreciated.|||If your data file is intact, you can try sp_attach_single_file_db too...
"Joe" wrote:

> I have a database that was on a SQL Server that failed. The data file is
> intact
> but I need to bring it up. What steps do I need to do in order to attach
> this to
> another SQL Server with the plan of maving it back to the original server
> once we
> get the server rebuilt.
> Any help would be greatly appreciated.

Sunday, February 19, 2012

Database Problem related Clusterd data

Hello sir
We have a very huge database its around 6 lakh records
are being stored in it.
records are not being a sorted order so we checked all
record field through clustering option in Sql server.when we used
clustering records are showing in sorted order but speed of database is
very slow .
i want to know with clustering is there any implecation in database
regading performance od data.Can any one give his views to solve this
problem?and increase the performance of our database.
thanks a lot
vibha wrote:
> Hello sir
> We have a very huge database its around 6 lakh records
^^^^^^
What kind of multiplier is this? --+

> are being stored in it.
> records are not being a sorted order so we checked all
> record field through clustering option in Sql server.when we used
> clustering records are showing in sorted order but speed of database
> is very slow .
> i want to know with clustering is there any implecation in database
> regading performance od data.Can any one give his views to solve this
> problem?and increase the performance of our database.
> thanks a lot
Using a clustered index just because you want to get sorted results is not
a good idea. Now, first you need to determine why it's slow. Then you
can take countermeasures. Have a look around
http://www.sql-server-performance.com/default.asp
and especially
http://www.sql-server-performance.co...ering_2000.asp
Kind regards
robert