How outdated is SQL Server 7? Will it run on a Windows 2000 Server?
--
Thank you for your time and have a great day,
Carroll P. MacDonaldAbout 5 years.
Yes, it will.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Carroll P. MacDonald" <!0000@.!00.000> wrote in message
news:OTIs$o1%23DHA.3284@.TK2MSFTNGP09.phx.gbl...
> How outdated is SQL Server 7? Will it run on a Windows 2000 Server?
> --
>
> Thank you for your time and have a great day,
> Carroll P. MacDonald
>
Showing posts with label time. Show all posts
Showing posts with label time. Show all posts
Thursday, March 29, 2012
How outdated is..
How outdated is SQL Server 7? Will it run on a Windows 2000 Server?
Thank you for your time and have a great day,
Carroll P. MacDonaldAbout 5 years.
Yes, it will.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Carroll P. MacDonald" <!0000@.!00.000> wrote in message
news:OTIs$o1%23DHA.3284@.TK2MSFTNGP09.phx.gbl...
> How outdated is SQL Server 7? Will it run on a Windows 2000 Server?
> --
>
> Thank you for your time and have a great day,
> Carroll P. MacDonald
>
Thank you for your time and have a great day,
Carroll P. MacDonaldAbout 5 years.
Yes, it will.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Carroll P. MacDonald" <!0000@.!00.000> wrote in message
news:OTIs$o1%23DHA.3284@.TK2MSFTNGP09.phx.gbl...
> How outdated is SQL Server 7? Will it run on a Windows 2000 Server?
> --
>
> Thank you for your time and have a great day,
> Carroll P. MacDonald
>
Wednesday, March 28, 2012
How often should I schedule a reboot of SQL Server 2005?
How many times per year should we schedule time to reboot a SQL Server 2005 Cluster?We want to do this to defrag the memory.What I am looking for is a document from Microsoft or a consulting firm that has a good reputation that I can show my manager.
Hi
I don't think you need to scdedule a restart for SQL 2005 cluster. SQL Server 2005 is very efficient at managing the memory dynamically.
Jag
|||There is no need to restart SQL Server on a regular basis. As SQL doesn't need memory it will release it. SQL Server 2005 is very good at managing it's memory.
If you want to clear it's cache you can use DBCC FREESYSTEMCACHE to free all the cache pools.
|||Unless you do not want to loose cached data and query plans, you should not do this :-)Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||You don't need to do it -- this product is designed to stay up ad infinitum (well apart from if you patch it or the OS requiring a reboot).|||
If I am running SQL Server 2005 in a clustered environment, what is the safest way to restart the SQL server agent? It is currently running but I need to restart it for maintenance purposes.
Is the safeway way to restart is to login to the SQL Server Management Studio as the system administrator, select the SQL Server Agent object, right-mouse click and select "Restart?"
|||That should work fine.How often should I schedule a reboot of SQL Server 2005?
How many times per year should we schedule time to reboot a SQL Server 2005 Cluster?We want to do this to defrag the memory.What I am looking for is a document from Microsoft or a consulting firm that has a good reputation that I can show my manager.
Hi
I don't think you need to scdedule a restart for SQL 2005 cluster. SQL Server 2005 is very efficient at managing the memory dynamically.
Jag
|||There is no need to restart SQL Server on a regular basis. As SQL doesn't need memory it will release it. SQL Server 2005 is very good at managing it's memory.
If you want to clear it's cache you can use DBCC FREESYSTEMCACHE to free all the cache pools.
|||Unless you do not want to loose cached data and query plans, you should not do this :-)Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||You don't need to do it -- this product is designed to stay up ad infinitum (well apart from if you patch it or the OS requiring a reboot).|||
If I am running SQL Server 2005 in a clustered environment, what is the safest way to restart the SQL server agent? It is currently running but I need to restart it for maintenance purposes.
Is the safeway way to restart is to login to the SQL Server Management Studio as the system administrator, select the SQL Server Agent object, right-mouse click and select "Restart?"
|||That should work fine.How often should I schedule a reboot of SQL Server 2005?
How many times per year should we schedule time to reboot a SQL Server 2005 Cluster?We want to do this to defrag the memory.What I am looking for is a document from Microsoft or a consulting firm that has a good reputation that I can show my manager.
Hi
I don't think you need to scdedule a restart for SQL 2005 cluster. SQL Server 2005 is very efficient at managing the memory dynamically.
Jag
|||There is no need to restart SQL Server on a regular basis. As SQL doesn't need memory it will release it. SQL Server 2005 is very good at managing it's memory.
If you want to clear it's cache you can use DBCC FREESYSTEMCACHE to free all the cache pools.
|||Unless you do not want to loose cached data and query plans, you should not do this :-)Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||You don't need to do it -- this product is designed to stay up ad infinitum (well apart from if you patch it or the OS requiring a reboot).|||
If I am running SQL Server 2005 in a clustered environment, what is the safest way to restart the SQL server agent? It is currently running but I need to restart it for maintenance purposes.
Is the safeway way to restart is to login to the SQL Server Management Studio as the system administrator, select the SQL Server Agent object, right-mouse click and select "Restart?"
|||That should work fine.How often and when should the sp_recompile procedure be used
We are at our slowest this time of year... Having never set the sp_recompile
directive for our procedures, would now be a good time to tell the server to
recompile all the stored procedures? I believe we have added perhaps 30 or
40 indexes since October.
Is this an appropriate method to activate the recompile?
DECLARE @.procname varchar(150)
DECLARE proc_recompile cursor for select name from sysobjects where xtype='P'
OPEN proc_recompile
FETCH NEXT FROM proc_recompile INTO @.procname
WHILE @.@.FETCH_STATUS = 0
BEGIN
EXEC sp_recompile @.procname
FETCH NEXT FROM proc_recompile INTO @.procname
END
CLOSE proc_recompile
DEALLOCATE proc_recompile
--
Regards,
Jamie
Is the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
database restore?
If not......
SQL recompiles stored procedures for you so....
Just update youre statistics an you wil be fine
Just my 2 cents
Greetz.
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"thejamie" wrote:
> We are at our slowest this time of year... Having never set the sp_recompile
> directive for our procedures, would now be a good time to tell the server to
> recompile all the stored procedures? I believe we have added perhaps 30 or
> 40 indexes since October.
> Is this an appropriate method to activate the recompile?
> --
> DECLARE @.procname varchar(150)
> DECLARE proc_recompile cursor for select name from sysobjects where xtype='P'
> OPEN proc_recompile
> FETCH NEXT FROM proc_recompile INTO @.procname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> EXEC sp_recompile @.procname
> FETCH NEXT FROM proc_recompile INTO @.procname
> END
> CLOSE proc_recompile
> DEALLOCATE proc_recompile
> --
> --
> Regards,
> Jamie
|||I made the mistake of reading the book. It is an optimization technique.
The impression I get from the book is that this should be done fairly
regularly.
The statistics are updated each week after the indexes are rebuilt. I've
added some new indexes and thought perhaps the query plan may find a better
index for a given stored procedure, use it, and thus, get better results.
To find indexes, I ran the profiler and analyzed the results. The profiler
gave me good suggestions for indexes to add.
Slow time of the year is what I mean - a chance to tweak things without the
system toppling over.
Regards,
Jamie
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> Is the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
> database restore?
> If not......
> SQL recompiles stored procedures for you so....
> Just update youre statistics an you wil be fine
> Just my 2 cents
> Greetz.
> --
> I drank alot of beer and ended up in the police department database.
> Drank more beer and learned SQL in the dark hours.
> DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
> I love SQL
>
>
> "thejamie" wrote:
|||If you or youre company developed the database\application i would say be my
guest and optimize\tune the database.
If not, be carefull adding indexes based on traces and adding 2 much indexes.
Greetz,
Flying Dutch men.
|||Hi Jamie
> Slow time of the year is what I mean - a chance to tweak things without the
> system toppling over.
> --
Be careful that your changes are not because of un-representative activity
as this could cause more problems rather than solve any. You should really
test any changes using representative workloads before implementing them.
John
directive for our procedures, would now be a good time to tell the server to
recompile all the stored procedures? I believe we have added perhaps 30 or
40 indexes since October.
Is this an appropriate method to activate the recompile?
DECLARE @.procname varchar(150)
DECLARE proc_recompile cursor for select name from sysobjects where xtype='P'
OPEN proc_recompile
FETCH NEXT FROM proc_recompile INTO @.procname
WHILE @.@.FETCH_STATUS = 0
BEGIN
EXEC sp_recompile @.procname
FETCH NEXT FROM proc_recompile INTO @.procname
END
CLOSE proc_recompile
DEALLOCATE proc_recompile
--
Regards,
Jamie
Is the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
database restore?
If not......
SQL recompiles stored procedures for you so....
Just update youre statistics an you wil be fine
Just my 2 cents
Greetz.
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"thejamie" wrote:
> We are at our slowest this time of year... Having never set the sp_recompile
> directive for our procedures, would now be a good time to tell the server to
> recompile all the stored procedures? I believe we have added perhaps 30 or
> 40 indexes since October.
> Is this an appropriate method to activate the recompile?
> --
> DECLARE @.procname varchar(150)
> DECLARE proc_recompile cursor for select name from sysobjects where xtype='P'
> OPEN proc_recompile
> FETCH NEXT FROM proc_recompile INTO @.procname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> EXEC sp_recompile @.procname
> FETCH NEXT FROM proc_recompile INTO @.procname
> END
> CLOSE proc_recompile
> DEALLOCATE proc_recompile
> --
> --
> Regards,
> Jamie
|||I made the mistake of reading the book. It is an optimization technique.
The impression I get from the book is that this should be done fairly
regularly.
The statistics are updated each week after the indexes are rebuilt. I've
added some new indexes and thought perhaps the query plan may find a better
index for a given stored procedure, use it, and thus, get better results.
To find indexes, I ran the profiler and analyzed the results. The profiler
gave me good suggestions for indexes to add.
Slow time of the year is what I mean - a chance to tweak things without the
system toppling over.
Regards,
Jamie
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> Is the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
> database restore?
> If not......
> SQL recompiles stored procedures for you so....
> Just update youre statistics an you wil be fine
> Just my 2 cents
> Greetz.
> --
> I drank alot of beer and ended up in the police department database.
> Drank more beer and learned SQL in the dark hours.
> DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
> I love SQL
>
>
> "thejamie" wrote:
|||If you or youre company developed the database\application i would say be my
guest and optimize\tune the database.
If not, be carefull adding indexes based on traces and adding 2 much indexes.
Greetz,
Flying Dutch men.
|||Hi Jamie
> Slow time of the year is what I mean - a chance to tweak things without the
> system toppling over.
> --
Be careful that your changes are not because of un-representative activity
as this could cause more problems rather than solve any. You should really
test any changes using representative workloads before implementing them.
John
How often and when should the sp_recompile procedure be used
We are at our slowest this time of year... Having never set the sp_recompil
e
directive for our procedures, would now be a good time to tell the server to
recompile all the stored procedures? I believe we have added perhaps 30 or
40 indexes since October.
Is this an appropriate method to activate the recompile?
--
DECLARE @.procname varchar(150)
DECLARE proc_recompile cursor for select name from sysobjects where xtype='P
'
OPEN proc_recompile
FETCH NEXT FROM proc_recompile INTO @.procname
WHILE @.@.FETCH_STATUS = 0
BEGIN
EXEC sp_recompile @.procname
FETCH NEXT FROM proc_recompile INTO @.procname
END
CLOSE proc_recompile
DEALLOCATE proc_recompile
--
--
Regards,
JamieIs the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
database restore?
If not......
SQL recompiles stored procedures for you so....
Just update youre statistics an you wil be fine
Just my 2 cents
Greetz.
--
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"thejamie" wrote:
> We are at our slowest this time of year... Having never set the sp_recomp
ile
> directive for our procedures, would now be a good time to tell the server
to
> recompile all the stored procedures? I believe we have added perhaps 30 o
r
> 40 indexes since October.
> Is this an appropriate method to activate the recompile?
> --
> DECLARE @.procname varchar(150)
> DECLARE proc_recompile cursor for select name from sysobjects where xtype=
'P'
> OPEN proc_recompile
> FETCH NEXT FROM proc_recompile INTO @.procname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> EXEC sp_recompile @.procname
> FETCH NEXT FROM proc_recompile INTO @.procname
> END
> CLOSE proc_recompile
> DEALLOCATE proc_recompile
> --
> --
> Regards,
> Jamie|||I made the mistake of reading the book. It is an optimization technique.
The impression I get from the book is that this should be done fairly
regularly.
The statistics are updated each week after the indexes are rebuilt. I've
added some new indexes and thought perhaps the query plan may find a better
index for a given stored procedure, use it, and thus, get better results.
To find indexes, I ran the profiler and analyzed the results. The profiler
gave me good suggestions for indexes to add.
Slow time of the year is what I mean - a chance to tweak things without the
system toppling over.
--
Regards,
Jamie
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> Is the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
> database restore?
> If not......
> SQL recompiles stored procedures for you so....
> Just update youre statistics an you wil be fine
> Just my 2 cents
> Greetz.
> --
> I drank alot of beer and ended up in the police department database.
> Drank more beer and learned SQL in the dark hours.
> DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
> I love SQL
>
>
> "thejamie" wrote:
>|||If you or youre company developed the database\application i would say be my
guest and optimize\tune the database.
If not, be carefull adding indexes based on traces and adding 2 much indexes
.
Greetz,
Flying Dutch men.|||Hi Jamie
> Slow time of the year is what I mean - a chance to tweak things without th
e
> system toppling over.
> --
Be careful that your changes are not because of un-representative activity
as this could cause more problems rather than solve any. You should really
test any changes using representative workloads before implementing them.
Johnsql
e
directive for our procedures, would now be a good time to tell the server to
recompile all the stored procedures? I believe we have added perhaps 30 or
40 indexes since October.
Is this an appropriate method to activate the recompile?
--
DECLARE @.procname varchar(150)
DECLARE proc_recompile cursor for select name from sysobjects where xtype='P
'
OPEN proc_recompile
FETCH NEXT FROM proc_recompile INTO @.procname
WHILE @.@.FETCH_STATUS = 0
BEGIN
EXEC sp_recompile @.procname
FETCH NEXT FROM proc_recompile INTO @.procname
END
CLOSE proc_recompile
DEALLOCATE proc_recompile
--
--
Regards,
JamieIs the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
database restore?
If not......
SQL recompiles stored procedures for you so....
Just update youre statistics an you wil be fine
Just my 2 cents
Greetz.
--
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"thejamie" wrote:
> We are at our slowest this time of year... Having never set the sp_recomp
ile
> directive for our procedures, would now be a good time to tell the server
to
> recompile all the stored procedures? I believe we have added perhaps 30 o
r
> 40 indexes since October.
> Is this an appropriate method to activate the recompile?
> --
> DECLARE @.procname varchar(150)
> DECLARE proc_recompile cursor for select name from sysobjects where xtype=
'P'
> OPEN proc_recompile
> FETCH NEXT FROM proc_recompile INTO @.procname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> EXEC sp_recompile @.procname
> FETCH NEXT FROM proc_recompile INTO @.procname
> END
> CLOSE proc_recompile
> DEALLOCATE proc_recompile
> --
> --
> Regards,
> Jamie|||I made the mistake of reading the book. It is an optimization technique.
The impression I get from the book is that this should be done fairly
regularly.
The statistics are updated each week after the indexes are rebuilt. I've
added some new indexes and thought perhaps the query plan may find a better
index for a given stored procedure, use it, and thus, get better results.
To find indexes, I ran the profiler and analyzed the results. The profiler
gave me good suggestions for indexes to add.
Slow time of the year is what I mean - a chance to tweak things without the
system toppling over.
--
Regards,
Jamie
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> Is the system slow? Blocking problems? Did you upgrade to sql 2005?Do a
> database restore?
> If not......
> SQL recompiles stored procedures for you so....
> Just update youre statistics an you wil be fine
> Just my 2 cents
> Greetz.
> --
> I drank alot of beer and ended up in the police department database.
> Drank more beer and learned SQL in the dark hours.
> DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
> I love SQL
>
>
> "thejamie" wrote:
>|||If you or youre company developed the database\application i would say be my
guest and optimize\tune the database.
If not, be carefull adding indexes based on traces and adding 2 much indexes
.
Greetz,
Flying Dutch men.|||Hi Jamie
> Slow time of the year is what I mean - a chance to tweak things without th
e
> system toppling over.
> --
Be careful that your changes are not because of un-representative activity
as this could cause more problems rather than solve any. You should really
test any changes using representative workloads before implementing them.
Johnsql
how much time to set up replication
Does anyone know how much time (approximate) I should allocate to set up
Transactional Replication on a SQL database that is 20 gig in size?
Your question is a bit vague. What specifically do you mean by "setup"? Just
the configurations? The initial snapshot and population? Also how fast are
the boxes?
"Patrick K" <PatrickK@.discussions.microsoft.com> wrote in message
news:A254BEB1-FE2A-4C65-8466-55696C37E2A4@.microsoft.com...
> Does anyone know how much time (approximate) I should allocate to set up
> Transactional Replication on a SQL database that is 20 gig in size?
>
Transactional Replication on a SQL database that is 20 gig in size?
Your question is a bit vague. What specifically do you mean by "setup"? Just
the configurations? The initial snapshot and population? Also how fast are
the boxes?
"Patrick K" <PatrickK@.discussions.microsoft.com> wrote in message
news:A254BEB1-FE2A-4C65-8466-55696C37E2A4@.microsoft.com...
> Does anyone know how much time (approximate) I should allocate to set up
> Transactional Replication on a SQL database that is 20 gig in size?
>
How much time it usually takes to create a DR plan?
Hi,
In your opinion, how much time would be a reasonable amount of time for a
DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
databases (OSes, and so on...) - one production and one standby, without
using replication, log shipping, or cluster, but only SAN storage block level
synchronization?
-- Hoping this makes any sense Oskar.You omitted almost all DR elements from the list :)
It depends on your environment. You just did not add your list Database
Mirroring however this is not applicable in SQL Server 2000 already.
So, what kind of a DR is this? A Cold-Standby? Like Backup\Restore or
Attach\Detach?
--
Ekrem Ã?nsoy
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:D6ECA2B1-D6DE-4FD4-A983-2971115693F1@.microsoft.com...
> Hi,
> In your opinion, how much time would be a reasonable amount of time for a
> DBA to spend on the creation of a DR plan for a set of two MS SQL Server
> 2000
> databases (OSes, and so on...) - one production and one standby, without
> using replication, log shipping, or cluster, but only SAN storage block
> level
> synchronization?
> -- Hoping this makes any sense Oskar.
>|||If you are doing this from scratch, the up-front time into the project can be
substantial to ensure the whole thing works with rigorous tests and to
document the procedures.
Once this is established, ongoing maintenance should be minimal.
Linchi
"Oskar" wrote:
> Hi,
> In your opinion, how much time would be a reasonable amount of time for a
> DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
> databases (OSes, and so on...) - one production and one standby, without
> using replication, log shipping, or cluster, but only SAN storage block level
> synchronization?
> -- Hoping this makes any sense Oskar.
>|||If something goes wrong i.e. either one "processing unit", one "storage
unit", or both of them go bust I switch to the remaining "processing unit"
and "storage unit". If that doesn't work (e.g. because of some kind of
"logical", "non-storage-level" fault that couldn't be detected) I recover
from the last full DB backup + the chain of transaction log backups up to the
point of corruption for affected areas.
"Ekrem Ã?nsoy" wrote:
> You omitted almost all DR elements from the list :)
> It depends on your environment. You just did not add your list Database
> Mirroring however this is not applicable in SQL Server 2000 already.
> So, what kind of a DR is this? A Cold-Standby? Like Backup\Restore or
> Attach\Detach?
> --
> Ekrem Ã?nsoy
>
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:D6ECA2B1-D6DE-4FD4-A983-2971115693F1@.microsoft.com...
> > Hi,
> > In your opinion, how much time would be a reasonable amount of time for a
> > DBA to spend on the creation of a DR plan for a set of two MS SQL Server
> > 2000
> > databases (OSes, and so on...) - one production and one standby, without
> > using replication, log shipping, or cluster, but only SAN storage block
> > level
> > synchronization?
> >
> > -- Hoping this makes any sense Oskar.
> >
>|||I'm not counting the time for testing, just the "paperwork". When you write
"substantial", do you mean weeks or months?
"Linchi Shea" wrote:
> If you are doing this from scratch, the up-front time into the project can be
> substantial to ensure the whole thing works with rigorous tests and to
> document the procedures.
> Once this is established, ongoing maintenance should be minimal.
> Linchi
> "Oskar" wrote:
> > Hi,
> > In your opinion, how much time would be a reasonable amount of time for a
> > DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
> > databases (OSes, and so on...) - one production and one standby, without
> > using replication, log shipping, or cluster, but only SAN storage block level
> > synchronization?
> >
> > -- Hoping this makes any sense Oskar.
> >|||It's hard to separate 'the paper work' from tests since you need to have
performed the tests to have the info for your paper work. If you are just
talking about creating a plan for doing the DR tests, we are talking about
hours or at most days.
Linchi
"Oskar" wrote:
> I'm not counting the time for testing, just the "paperwork". When you write
> "substantial", do you mean weeks or months?
> "Linchi Shea" wrote:
> > If you are doing this from scratch, the up-front time into the project can be
> > substantial to ensure the whole thing works with rigorous tests and to
> > document the procedures.
> >
> > Once this is established, ongoing maintenance should be minimal.
> >
> > Linchi
> >
> > "Oskar" wrote:
> >
> > > Hi,
> > > In your opinion, how much time would be a reasonable amount of time for a
> > > DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
> > > databases (OSes, and so on...) - one production and one standby, without
> > > using replication, log shipping, or cluster, but only SAN storage block level
> > > synchronization?
> > >
> > > -- Hoping this makes any sense Oskar.
> > >|||One week should be sufficient.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:48706660-18A6-4DB2-98F3-5F36D7A9A7BC@.microsoft.com...
> I'm not counting the time for testing, just the "paperwork". When you
> write
> "substantial", do you mean weeks or months?
> "Linchi Shea" wrote:
>> If you are doing this from scratch, the up-front time into the project
>> can be
>> substantial to ensure the whole thing works with rigorous tests and to
>> document the procedures.
>> Once this is established, ongoing maintenance should be minimal.
>> Linchi
>> "Oskar" wrote:
>> > Hi,
>> > In your opinion, how much time would be a reasonable amount of time for
>> > a
>> > DBA to spend on the creation of a DR plan for a set of two MS SQL
>> > Server 2000
>> > databases (OSes, and so on...) - one production and one standby,
>> > without
>> > using replication, log shipping, or cluster, but only SAN storage block
>> > level
>> > synchronization?
>> >
>> > -- Hoping this makes any sense Oskar.
>> >
In your opinion, how much time would be a reasonable amount of time for a
DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
databases (OSes, and so on...) - one production and one standby, without
using replication, log shipping, or cluster, but only SAN storage block level
synchronization?
-- Hoping this makes any sense Oskar.You omitted almost all DR elements from the list :)
It depends on your environment. You just did not add your list Database
Mirroring however this is not applicable in SQL Server 2000 already.
So, what kind of a DR is this? A Cold-Standby? Like Backup\Restore or
Attach\Detach?
--
Ekrem Ã?nsoy
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:D6ECA2B1-D6DE-4FD4-A983-2971115693F1@.microsoft.com...
> Hi,
> In your opinion, how much time would be a reasonable amount of time for a
> DBA to spend on the creation of a DR plan for a set of two MS SQL Server
> 2000
> databases (OSes, and so on...) - one production and one standby, without
> using replication, log shipping, or cluster, but only SAN storage block
> level
> synchronization?
> -- Hoping this makes any sense Oskar.
>|||If you are doing this from scratch, the up-front time into the project can be
substantial to ensure the whole thing works with rigorous tests and to
document the procedures.
Once this is established, ongoing maintenance should be minimal.
Linchi
"Oskar" wrote:
> Hi,
> In your opinion, how much time would be a reasonable amount of time for a
> DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
> databases (OSes, and so on...) - one production and one standby, without
> using replication, log shipping, or cluster, but only SAN storage block level
> synchronization?
> -- Hoping this makes any sense Oskar.
>|||If something goes wrong i.e. either one "processing unit", one "storage
unit", or both of them go bust I switch to the remaining "processing unit"
and "storage unit". If that doesn't work (e.g. because of some kind of
"logical", "non-storage-level" fault that couldn't be detected) I recover
from the last full DB backup + the chain of transaction log backups up to the
point of corruption for affected areas.
"Ekrem Ã?nsoy" wrote:
> You omitted almost all DR elements from the list :)
> It depends on your environment. You just did not add your list Database
> Mirroring however this is not applicable in SQL Server 2000 already.
> So, what kind of a DR is this? A Cold-Standby? Like Backup\Restore or
> Attach\Detach?
> --
> Ekrem Ã?nsoy
>
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:D6ECA2B1-D6DE-4FD4-A983-2971115693F1@.microsoft.com...
> > Hi,
> > In your opinion, how much time would be a reasonable amount of time for a
> > DBA to spend on the creation of a DR plan for a set of two MS SQL Server
> > 2000
> > databases (OSes, and so on...) - one production and one standby, without
> > using replication, log shipping, or cluster, but only SAN storage block
> > level
> > synchronization?
> >
> > -- Hoping this makes any sense Oskar.
> >
>|||I'm not counting the time for testing, just the "paperwork". When you write
"substantial", do you mean weeks or months?
"Linchi Shea" wrote:
> If you are doing this from scratch, the up-front time into the project can be
> substantial to ensure the whole thing works with rigorous tests and to
> document the procedures.
> Once this is established, ongoing maintenance should be minimal.
> Linchi
> "Oskar" wrote:
> > Hi,
> > In your opinion, how much time would be a reasonable amount of time for a
> > DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
> > databases (OSes, and so on...) - one production and one standby, without
> > using replication, log shipping, or cluster, but only SAN storage block level
> > synchronization?
> >
> > -- Hoping this makes any sense Oskar.
> >|||It's hard to separate 'the paper work' from tests since you need to have
performed the tests to have the info for your paper work. If you are just
talking about creating a plan for doing the DR tests, we are talking about
hours or at most days.
Linchi
"Oskar" wrote:
> I'm not counting the time for testing, just the "paperwork". When you write
> "substantial", do you mean weeks or months?
> "Linchi Shea" wrote:
> > If you are doing this from scratch, the up-front time into the project can be
> > substantial to ensure the whole thing works with rigorous tests and to
> > document the procedures.
> >
> > Once this is established, ongoing maintenance should be minimal.
> >
> > Linchi
> >
> > "Oskar" wrote:
> >
> > > Hi,
> > > In your opinion, how much time would be a reasonable amount of time for a
> > > DBA to spend on the creation of a DR plan for a set of two MS SQL Server 2000
> > > databases (OSes, and so on...) - one production and one standby, without
> > > using replication, log shipping, or cluster, but only SAN storage block level
> > > synchronization?
> > >
> > > -- Hoping this makes any sense Oskar.
> > >|||One week should be sufficient.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:48706660-18A6-4DB2-98F3-5F36D7A9A7BC@.microsoft.com...
> I'm not counting the time for testing, just the "paperwork". When you
> write
> "substantial", do you mean weeks or months?
> "Linchi Shea" wrote:
>> If you are doing this from scratch, the up-front time into the project
>> can be
>> substantial to ensure the whole thing works with rigorous tests and to
>> document the procedures.
>> Once this is established, ongoing maintenance should be minimal.
>> Linchi
>> "Oskar" wrote:
>> > Hi,
>> > In your opinion, how much time would be a reasonable amount of time for
>> > a
>> > DBA to spend on the creation of a DR plan for a set of two MS SQL
>> > Server 2000
>> > databases (OSes, and so on...) - one production and one standby,
>> > without
>> > using replication, log shipping, or cluster, but only SAN storage block
>> > level
>> > synchronization?
>> >
>> > -- Hoping this makes any sense Oskar.
>> >
How much time does it take to replicate a 40M of data
Hi.
Based from experience, how much time does it take to replicate a 40M of data?
Database: SQL Server 2000
Replication Type: Merge
That's a function of the hardware on the publisher and subscriber. It should
take on first class servers under 10 minutes.
Hilary Cotter
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
"NS" <NS@.discussions.microsoft.com> wrote in message
news:DE536B15-1212-427E-A535-0B67E7F10D4B@.microsoft.com...
> Hi.
> Based from experience, how much time does it take to replicate a 40M of
data?
> Database: SQL Server 2000
> Replication Type: Merge
>
Based from experience, how much time does it take to replicate a 40M of data?
Database: SQL Server 2000
Replication Type: Merge
That's a function of the hardware on the publisher and subscriber. It should
take on first class servers under 10 minutes.
Hilary Cotter
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
"NS" <NS@.discussions.microsoft.com> wrote in message
news:DE536B15-1212-427E-A535-0B67E7F10D4B@.microsoft.com...
> Hi.
> Based from experience, how much time does it take to replicate a 40M of
data?
> Database: SQL Server 2000
> Replication Type: Merge
>
How much time does exist a temporary table?
How much time does exist a temporary table?
Thanks,
--
Vilmar Brazo de OliveiraFor a local temp table, as long as the session that created it is still
connected... Or, when it's dropped.
For a global temp table, as long as any session that has accessed it is
still connected... Or, when it's dropped.
"Vilmar" <xx1122@.x1212x.com.jc> wrote in message
news:#xBi1AlIEHA.2876@.TK2MSFTNGP09.phx.gbl...
> How much time does exist a temporary table?
> Thanks,
> --
>
> Vilmar Brazo de Oliveira
>
Thanks,
--
Vilmar Brazo de OliveiraFor a local temp table, as long as the session that created it is still
connected... Or, when it's dropped.
For a global temp table, as long as any session that has accessed it is
still connected... Or, when it's dropped.
"Vilmar" <xx1122@.x1212x.com.jc> wrote in message
news:#xBi1AlIEHA.2876@.TK2MSFTNGP09.phx.gbl...
> How much time does exist a temporary table?
> Thanks,
> --
>
> Vilmar Brazo de Oliveira
>
How much time does exist a temporary table?
How much time does exist a temporary table?
Thanks,
Vilmar Brazo de Oliveira
For a local temp table, as long as the session that created it is still
connected... Or, when it's dropped.
For a global temp table, as long as any session that has accessed it is
still connected... Or, when it's dropped.
"Vilmar" <xx1122@.x1212x.com.jc> wrote in message
news:#xBi1AlIEHA.2876@.TK2MSFTNGP09.phx.gbl...
> How much time does exist a temporary table?
> Thanks,
> --
>
> Vilmar Brazo de Oliveira
>
sql
Thanks,
Vilmar Brazo de Oliveira
For a local temp table, as long as the session that created it is still
connected... Or, when it's dropped.
For a global temp table, as long as any session that has accessed it is
still connected... Or, when it's dropped.
"Vilmar" <xx1122@.x1212x.com.jc> wrote in message
news:#xBi1AlIEHA.2876@.TK2MSFTNGP09.phx.gbl...
> How much time does exist a temporary table?
> Thanks,
> --
>
> Vilmar Brazo de Oliveira
>
sql
How much time does exist a temporary table?
How much time does exist a temporary table?
Thanks,
--
Vilmar Brazão de OliveiraFor a local temp table, as long as the session that created it is still
connected... Or, when it's dropped.
For a global temp table, as long as any session that has accessed it is
still connected... Or, when it's dropped.
"Vilmar" <xx1122@.x1212x.com.jc> wrote in message
news:#xBi1AlIEHA.2876@.TK2MSFTNGP09.phx.gbl...
> How much time does exist a temporary table?
> Thanks,
> --
>
> Vilmar Brazão de Oliveira
>
Thanks,
--
Vilmar Brazão de OliveiraFor a local temp table, as long as the session that created it is still
connected... Or, when it's dropped.
For a global temp table, as long as any session that has accessed it is
still connected... Or, when it's dropped.
"Vilmar" <xx1122@.x1212x.com.jc> wrote in message
news:#xBi1AlIEHA.2876@.TK2MSFTNGP09.phx.gbl...
> How much time does exist a temporary table?
> Thanks,
> --
>
> Vilmar Brazão de Oliveira
>
How much time does a query take?
Hello!
First of all, please excuse my (probably) bad english! :-/
My question is, how much time goes by until a query to a database is
finished? Is it fast enough for a query every 0.5 second?
In my application it's not usual that every 0.5 to 1 second a query is sent,
but it can happen.
I hope you can understand my concern and maybe can help me!
Greetings,
Christian
Am Fri, 10 Mar 2006 09:07:51 +0100 schrieb chris.lo:
> Hello!
> First of all, please excuse my (probably) bad english! :-/
> My question is, how much time goes by until a query to a database is
> finished? Is it fast enough for a query every 0.5 second?
> In my application it's not usual that every 0.5 to 1 second a query is sent,
> but it can happen.
> I hope you can understand my concern and maybe can help me!
> Greetings,
> Christian
Do you know what you want to ask? We have no information about the hardware
you use, how many users at the same time, how much data you have, what
queries are executed against the database, which funktions, triggers,
stored procedures are involved ...
So i can only say: if you use the same hardware as i and the same queries,
then it is fast enough :-)
bye, Helmut
|||Hello Helmut!
Of course you are right! I can't expect accurate answers without accurate
details!
So, here we are:
The MSDE is running on a P4 with 1.6 GHz and 512 MB Ram. On this PC there's
not only the MSDE running, but also a visualisation for a part of a
production plant. We plan to install a extra PC only for the MSDE, but that
depends on our customer...
At the moment there can be 10 users max "online". The amount of data depends
on the different Views which the user can select. I can't tell you that
amount in detail...
> which funktions, triggers, stored procedures are involved ...
I'm not THAT experienced in databases, but I can tell you that we didn't use
that things. (maybe the system uses that automatically?!)
Well, alltogether I can't make a proper description of what is happening in
detail. Maybe I tell you what I'm planning to do and maybe then you can tell
me whether is it possible or not:
Our application receives Messages from several PLCs. This messages tell our
app some info about the plant the PLC is controlling. Mostly the messages
tell our app when a fault (in the plant) occured und when it went away. Also
with this messages the app can count the produced parts (parts of a car) and
how long every single part took to be finished.
The message is represented by a 32-Bit number, an additional timestamp a
some flags. This numbers are not very informative, of course. So our
application has to lookup this number in a list and pick out the appropriate
description. This description can be seen by the user.
So far, so good. This mechanism is allready implemented in our application,
but I don't like it because it's extremely inflexible. So I plan to do it a
different way. I wanted to create the list with the numbers and description
as a table in the database. And every time a message was received from a
PLC, the app would execute a query against the database to retrieve the
description.
Like I wrote in my first question, in that way there can be a query every
0.5 second. And now I wonder whether this method is practicable or not. I
have concerns that this way will maybe slow down the whole application...
What do you thing? Should I do this? Maybe you wonder why I don't change the
mechanism in our app itself. Well, that belongs to internal functionality,
to which I don't have access.
I'm looking forward to some helpfull informations or opinions.
Greatings,
Chris
"helmut woess" <hw@.iis.at> schrieb im Newsbeitrag
news:byh92sdxklyh$.bcfu0dq0a5y9$.dlg@.40tude.net...
> Am Fri, 10 Mar 2006 09:07:51 +0100 schrieb chris.lo:
>
> Do you know what you want to ask? We have no information about the
> hardware
> you use, how many users at the same time, how much data you have, what
> queries are executed against the database, which funktions, triggers,
> stored procedures are involved ...
> So i can only say: if you use the same hardware as i and the same queries,
> then it is fast enough :-)
> bye, Helmut
|||hi,
chris.lo wrote:
> The message is represented by a 32-Bit number, an additional
> timestamp a some flags. This numbers are not very informative, of
> course. So our application has to lookup this number in a list and
> pick out the appropriate description. This description can be seen by
> the user.
> So far, so good. This mechanism is allready implemented in our
> application, but I don't like it because it's extremely inflexible.
> So I plan to do it a different way. I wanted to create the list with
> the numbers and description as a table in the database. And every
> time a message was received from a PLC, the app would execute a query
> against the database to retrieve the description.
> Like I wrote in my first question, in that way there can be a query
> every 0.5 second. And now I wonder whether this method is practicable or
> not. I have concerns that this way will maybe slow down the whole
> application...
I do not know your actual schema, but your words seems to tell you actually
have a normalized one...
personally I'd not make a lookup every time a message is received, as you
probably already have all needed pieces of information to lookup only at
"reporting time" whenever it is performed/needed.. without that lookup you
preserve your schema in a better normalized manner and you preserve system
resources..
when reports are needed, you can perform your join and present data in the
human readeble way as all encoded values will be there resolved to their
human "descriprions"...
if you keep your batch operations as little as possible, you should decrease
possibility to hit the internal MSDE limit of 8 (5 + 3 system batches)
concurrent workloads, but, more important, you keep a normalized schema
where your foreign key constraints are resolved only on a "when needed"
basis..
obviously, IMHO
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello Chris,
there are still many dark horses and i think it is not possible to give you
a warranty that this will work or will surely not work.
A dangerous part is MSDE and 10 concurrent users. You can have 10
concurrent users, but if some requests arrives nearly at the same time,
then MSDE starts to insert wait cycles and then it comes very fast to a
bigger delay.
This has gone with SQLExpress, so if you have only MSDE and no real
SQL-Server then it would be better to use SQLExpress.
And because visualisation can be very ressource intensive, i would not do
both on the same machine.
My suggestion: a new PC with 1 Gb Memory and a fast harddrive, Windows 2K
as OS and SQLExpress. Under normal circumstances this should be enough.
bye,
Helmut
|||Hello!
Thank you both for your answers und opinions! I think I simply will test it,
and then I can decide whether I will do it that way or not...
Greetings,
Christian
First of all, please excuse my (probably) bad english! :-/
My question is, how much time goes by until a query to a database is
finished? Is it fast enough for a query every 0.5 second?
In my application it's not usual that every 0.5 to 1 second a query is sent,
but it can happen.
I hope you can understand my concern and maybe can help me!
Greetings,
Christian
Am Fri, 10 Mar 2006 09:07:51 +0100 schrieb chris.lo:
> Hello!
> First of all, please excuse my (probably) bad english! :-/
> My question is, how much time goes by until a query to a database is
> finished? Is it fast enough for a query every 0.5 second?
> In my application it's not usual that every 0.5 to 1 second a query is sent,
> but it can happen.
> I hope you can understand my concern and maybe can help me!
> Greetings,
> Christian
Do you know what you want to ask? We have no information about the hardware
you use, how many users at the same time, how much data you have, what
queries are executed against the database, which funktions, triggers,
stored procedures are involved ...
So i can only say: if you use the same hardware as i and the same queries,
then it is fast enough :-)
bye, Helmut
|||Hello Helmut!
Of course you are right! I can't expect accurate answers without accurate
details!
So, here we are:
The MSDE is running on a P4 with 1.6 GHz and 512 MB Ram. On this PC there's
not only the MSDE running, but also a visualisation for a part of a
production plant. We plan to install a extra PC only for the MSDE, but that
depends on our customer...
At the moment there can be 10 users max "online". The amount of data depends
on the different Views which the user can select. I can't tell you that
amount in detail...
> which funktions, triggers, stored procedures are involved ...
I'm not THAT experienced in databases, but I can tell you that we didn't use
that things. (maybe the system uses that automatically?!)
Well, alltogether I can't make a proper description of what is happening in
detail. Maybe I tell you what I'm planning to do and maybe then you can tell
me whether is it possible or not:
Our application receives Messages from several PLCs. This messages tell our
app some info about the plant the PLC is controlling. Mostly the messages
tell our app when a fault (in the plant) occured und when it went away. Also
with this messages the app can count the produced parts (parts of a car) and
how long every single part took to be finished.
The message is represented by a 32-Bit number, an additional timestamp a
some flags. This numbers are not very informative, of course. So our
application has to lookup this number in a list and pick out the appropriate
description. This description can be seen by the user.
So far, so good. This mechanism is allready implemented in our application,
but I don't like it because it's extremely inflexible. So I plan to do it a
different way. I wanted to create the list with the numbers and description
as a table in the database. And every time a message was received from a
PLC, the app would execute a query against the database to retrieve the
description.
Like I wrote in my first question, in that way there can be a query every
0.5 second. And now I wonder whether this method is practicable or not. I
have concerns that this way will maybe slow down the whole application...
What do you thing? Should I do this? Maybe you wonder why I don't change the
mechanism in our app itself. Well, that belongs to internal functionality,
to which I don't have access.
I'm looking forward to some helpfull informations or opinions.
Greatings,
Chris
"helmut woess" <hw@.iis.at> schrieb im Newsbeitrag
news:byh92sdxklyh$.bcfu0dq0a5y9$.dlg@.40tude.net...
> Am Fri, 10 Mar 2006 09:07:51 +0100 schrieb chris.lo:
>
> Do you know what you want to ask? We have no information about the
> hardware
> you use, how many users at the same time, how much data you have, what
> queries are executed against the database, which funktions, triggers,
> stored procedures are involved ...
> So i can only say: if you use the same hardware as i and the same queries,
> then it is fast enough :-)
> bye, Helmut
|||hi,
chris.lo wrote:
> The message is represented by a 32-Bit number, an additional
> timestamp a some flags. This numbers are not very informative, of
> course. So our application has to lookup this number in a list and
> pick out the appropriate description. This description can be seen by
> the user.
> So far, so good. This mechanism is allready implemented in our
> application, but I don't like it because it's extremely inflexible.
> So I plan to do it a different way. I wanted to create the list with
> the numbers and description as a table in the database. And every
> time a message was received from a PLC, the app would execute a query
> against the database to retrieve the description.
> Like I wrote in my first question, in that way there can be a query
> every 0.5 second. And now I wonder whether this method is practicable or
> not. I have concerns that this way will maybe slow down the whole
> application...
I do not know your actual schema, but your words seems to tell you actually
have a normalized one...
personally I'd not make a lookup every time a message is received, as you
probably already have all needed pieces of information to lookup only at
"reporting time" whenever it is performed/needed.. without that lookup you
preserve your schema in a better normalized manner and you preserve system
resources..
when reports are needed, you can perform your join and present data in the
human readeble way as all encoded values will be there resolved to their
human "descriprions"...
if you keep your batch operations as little as possible, you should decrease
possibility to hit the internal MSDE limit of 8 (5 + 3 system batches)
concurrent workloads, but, more important, you keep a normalized schema
where your foreign key constraints are resolved only on a "when needed"
basis..
obviously, IMHO
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello Chris,
there are still many dark horses and i think it is not possible to give you
a warranty that this will work or will surely not work.
A dangerous part is MSDE and 10 concurrent users. You can have 10
concurrent users, but if some requests arrives nearly at the same time,
then MSDE starts to insert wait cycles and then it comes very fast to a
bigger delay.
This has gone with SQLExpress, so if you have only MSDE and no real
SQL-Server then it would be better to use SQLExpress.
And because visualisation can be very ressource intensive, i would not do
both on the same machine.
My suggestion: a new PC with 1 Gb Memory and a fast harddrive, Windows 2K
as OS and SQLExpress. Under normal circumstances this should be enough.
bye,
Helmut
|||Hello!
Thank you both for your answers und opinions! I think I simply will test it,
and then I can decide whether I will do it that way or not...
Greetings,
Christian
Friday, March 23, 2012
How many time dimensions can be created for a cube? And can different cubes share one time dimen
Hi, all experts here,
Thank you very much for your kind attention.
I have encountered some problems while creating time dimensions of cubes. I am wondering: Dose SQL Server 2005 Analysis Services allow to create more than one time dimension within a cube? and can different cubes share a time dimension?
Please could any experts here shed me any light on that and I am looking forward to hearing from you shortly and Thanks a lot in advance for your help.
With best regards,
Yours sincerely,
Helen999888 wrote:
Dose SQL Server 2005 Analysis Services allow to create more than one time dimension within a cube?
Yes, but a common practice is to define a single time dimension and give it aliases through the dimension relationship tab in the cube editor. Why do you need multiple time dimensions?
and can different cubes share a time dimension?
Yes.
|||Yes - both are possible. In the Adventure Works sample, there are 3 different Time dimensions in the same cube (they are role playing dimensions, but don't have to be, although it usually does make sense to make all time dimensions role playing).|||AS 2005 allows more than one Time dimension in a cube and Time dimensions can be shared.|||Hi, All,
Thank you so much indeed for your kind advices. It's been very helpful.
With best regards,
Yours sincerely,
how many tables a dataset can store at a time?
hello friend,
how many tables a dataset can store at a time? can u tell me.
There is no restriction for normal usage, because you'll encounter OutOfMemoryException before reaching actual limit, which is 2^30 datatablessql
how many tables a dataset can store at a time? can u tell me.
Quote:
Originally Posted by mcasaurabhsumit
hello friend,
how many tables a dataset can store at a time? can u tell me.
There is no restriction for normal usage, because you'll encounter OutOfMemoryException before reaching actual limit, which is 2^30 datatablessql
How many SSRS reports the execution option can be set to run at the same time?
Hi
There shall be atleast 1000 reports that could be created and the execution option can be set for daily and at 00:00 hrs. So my question is how many reports can get refreshed at the same time?
Thanking you in advance
regards
Sai
There is no theoretical limit to the number of reports that can be scheduled for the same time. I would set them up to run off of a shared schedule. When the schedule fires the report executions will be queued up to run. The Report Server will attempt to run as many as possible without consuming to many resources. As it works through the reports, it will bring in more to process. This means that some reports will be run at 12, but others will run later as they are taken from the queue. It will depend on the type of reports and the speed of the machines to determine how long it will take.
If the reports take to long you can always add additional machines to the configuration to allow for more throughput.
How many rows...?
I'm developing an app that will allow a user to track clicks and sales by date/time. However, I was wondering with the potential for a TON of clicks, is it feasable to track individual clicks in a SQL Server 2000 or 2005 database? I'm talking potentially 50,000 products receiving thousands of clicks per day, coud the db handle that kind of traffic? Or should I stick with a running total of clicks per product, and forget about the ability to see a breakdown of clicks per day, etc?That data is going to get out of control rather fast. However you can keep a running total by day.|||How many rows can a typical table handle? 1 million? 500 million? 1 billion? More? That will help me figure out if I can track clicks daily, or if I have to track weekly or monthly.|||The only limitation of rows per table in SQL is the storage available, see 'Maximum Capacity Specifications' topic in SQL Books Online
Wednesday, March 21, 2012
How many result-rows does mssql return should be used asynchronous method to use mssql cur
How many result-rows does mssql return should be used asynchronous method to use mssql cursor, can get the best performance in any time in any result offset?
i want to make the cursor fast in any time whatever how many results returnedi didnt understand what xactly you meant by your first line but for this
>>i want to make the cursor fast in any time whatever how many results returned
there some optional parameters when you declare a cursor..for xample :
BOL has a good reference about it..look under 'DECLARE CURSOR'
Transact-SQL Extended Syntax
DECLARE cursor_name CURSOR
[ LOCAL | GLOBAL ]
[ FORWARD_ONLY | SCROLL ]
[ STATIC | KEYSET | DYNAMIC | FAST_FORWARD ]
[ READ_ONLY | SCROLL_LOCKS | OPTIMISTIC ]
[ TYPE_WARNING ]
FOR select_statement
[ FOR UPDATE [ OF column_name [ ,...n ] ] ]
you can use LOCAL, FORWARD_ONLY, READ_ONLY etc options to make it faster..
hth|||nono, i means the command like this:
sp_configure 'cursor threshold', xxx( a number, -1 = all synchronous, 0 = all asynchronous)
How many recordset open ?
Hello,
I use VisualBasic 6, MSDE and ADO2.8.
I seek to know how many recordsets are open at the same time.
How much CPU (or memory) use they?
My goal is to know if all my recordset is well closed.
Thank you.
hi Sylvain,
Sylvain Aufrre wrote:
> Hello,
> I use VisualBasic 6, MSDE and ADO2.8.
> I seek to know how many recordsets are open at the same time.
> How much CPU (or memory) use they?
> My goal is to know if all my recordset is well closed.
> Thank you.
I do not know counters for such questions...
you can see active connections to the SQL Server instance, but not
recordsets, as they are part of the ADO design (better, the ADO counterpart
of OLE DB Rowsets)
and I do not think you should inspect for memory allocation/requirements in
order to check your clean-up code... you just have to review it and verify
you properly close and release objects as it should be
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you Andrea,
Ok, there is nothing to see open recordsets.
But, which tools allows seeing the application activity on MSDE data base ?
Which tables is opened? read? written? Who? When?
My goal is to know if my development team correctly releases the data base
objects.
I seek a "systematic" method to check that.
Thank-you to reply to these newbies questions !
"Andrea Montanari" wrote:
> hi Sylvain,
> Sylvain Aufrère wrote:
> I do not know counters for such questions...
> you can see active connections to the SQL Server instance, but not
> recordsets, as they are part of the ADO design (better, the ADO counterpart
> of OLE DB Rowsets)
> and I do not think you should inspect for memory allocation/requirements in
> order to check your clean-up code... you just have to review it and verify
> you properly close and release objects as it should be
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Sylvain,
Sylvain Aufrre wrote:
> Thank you Andrea,
> Ok, there is nothing to see open recordsets.
> But, which tools allows seeing the application activity on MSDE data
> base ? Which tables is opened? read? written? Who? When?
you can perhaps monitor active connections both via Enterprise Manager or by
executing sp_who filtering out for you required database...
actually read write operations depend on user's activity... if your user
form is simple waiting for user input you'll see no db activity at all...
tables are not opened... they are read and eventually written... they can
even bre read from cache as SQL Server try to keep them alive on cache once
read... writing conditions depends on database recovery model too, as dirty
pages can be flushed to the transaction log and stay there untill a backup
log or, with simple recovery model, be flushed to data pages at recurring
checkpoints...
> My goal is to know if my development team correctly releases the data
> base objects.
> I seek a "systematic" method to check that.
you can perhaps use the SQL Server Profiler running traces, and/or ad a
specific SQL Server counter on the System Monitor...
have a look at
http://msdn.microsoft.com/library/de..._perf_76cm.asp
for further info... and all counters are successively exploded..
but I do think the best check is code review...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql
I use VisualBasic 6, MSDE and ADO2.8.
I seek to know how many recordsets are open at the same time.
How much CPU (or memory) use they?
My goal is to know if all my recordset is well closed.
Thank you.
hi Sylvain,
Sylvain Aufrre wrote:
> Hello,
> I use VisualBasic 6, MSDE and ADO2.8.
> I seek to know how many recordsets are open at the same time.
> How much CPU (or memory) use they?
> My goal is to know if all my recordset is well closed.
> Thank you.
I do not know counters for such questions...
you can see active connections to the SQL Server instance, but not
recordsets, as they are part of the ADO design (better, the ADO counterpart
of OLE DB Rowsets)
and I do not think you should inspect for memory allocation/requirements in
order to check your clean-up code... you just have to review it and verify
you properly close and release objects as it should be
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you Andrea,
Ok, there is nothing to see open recordsets.
But, which tools allows seeing the application activity on MSDE data base ?
Which tables is opened? read? written? Who? When?
My goal is to know if my development team correctly releases the data base
objects.
I seek a "systematic" method to check that.
Thank-you to reply to these newbies questions !
"Andrea Montanari" wrote:
> hi Sylvain,
> Sylvain Aufrère wrote:
> I do not know counters for such questions...
> you can see active connections to the SQL Server instance, but not
> recordsets, as they are part of the ADO design (better, the ADO counterpart
> of OLE DB Rowsets)
> and I do not think you should inspect for memory allocation/requirements in
> order to check your clean-up code... you just have to review it and verify
> you properly close and release objects as it should be
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Sylvain,
Sylvain Aufrre wrote:
> Thank you Andrea,
> Ok, there is nothing to see open recordsets.
> But, which tools allows seeing the application activity on MSDE data
> base ? Which tables is opened? read? written? Who? When?
you can perhaps monitor active connections both via Enterprise Manager or by
executing sp_who filtering out for you required database...
actually read write operations depend on user's activity... if your user
form is simple waiting for user input you'll see no db activity at all...
tables are not opened... they are read and eventually written... they can
even bre read from cache as SQL Server try to keep them alive on cache once
read... writing conditions depends on database recovery model too, as dirty
pages can be flushed to the transaction log and stay there untill a backup
log or, with simple recovery model, be flushed to data pages at recurring
checkpoints...
> My goal is to know if my development team correctly releases the data
> base objects.
> I seek a "systematic" method to check that.
you can perhaps use the SQL Server Profiler running traces, and/or ad a
specific SQL Server counter on the System Monitor...
have a look at
http://msdn.microsoft.com/library/de..._perf_76cm.asp
for further info... and all counters are successively exploded..
but I do think the best check is code review...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql
Subscribe to:
Posts (Atom)