Showing posts with label run. Show all posts
Showing posts with label run. Show all posts

Thursday, March 29, 2012

Database image retrieval causes datasource credential prompt

I have an image stored in a database that I use on a report with other non image data. When I run the report, the non image data is displayed, followed by a prompt for me to enter datasource credentials. None of the images are downloaded until I enter the credentials. If I don't enter the creds, the images aren't downloaded and appear only as the red x, file not found icon. I don't understand why I'm getting the prompt because I've already passed the exact set of credentials that the dialog expects to the web service with my call to the render method. THIS IS SO FRUSTRATING! I am experiencing this on both staging and production servers, but not on my development machine. I'm using reporting services service pack 1 on staging and production.

Thanks in advance for the help,
Kim

I guess the answer depends on what export format you're obtaining from the report server. If you're asking for HTML output, then the Images are not included in the HTML output. When the browser displays the HTML output, it will follow the links to each image and after a successful authentication, it will retrieve the images.

If you use the report viewer controls in your application rather than the SOAP api directly, it will probably alleviate this problem.

-Lukasz

sql

Database image retrieval causes datasource credential prompt

I have an image stored in a database that I use on a report with other non image data. When I run the report, the non image data is displayed, followed by a prompt for me to enter datasource credentials. None of the images are downloaded until I enter the credentials. If I don't enter the creds, the images aren't downloaded and appear only as the red x, file not found icon. I don't understand why I'm getting the prompt because I've already passed the exact set of credentials that the dialog expects to the web service with my call to the render method. THIS IS SO FRUSTRATING! I am experiencing this on both staging and production servers, but not on my development machine. I'm using reporting services service pack 1 on staging and production.

Thanks in advance for the help,
Kim

I guess the answer depends on what export format you're obtaining from the report server. If you're asking for HTML output, then the Images are not included in the HTML output. When the browser displays the HTML output, it will follow the links to each image and after a successful authentication, it will retrieve the images.

If you use the report viewer controls in your application rather than the SOAP api directly, it will probably alleviate this problem.

-Lukasz

Database ID

I am new to DMVs and DMFs. If I run
select * from sys.dm_db_index_usage_stats
How do I know which database relates to the database_Id? likewise the
Object_Id and Index_ID? Is there a lookup table somewhere I could join on?
thanksAdam,
you could use something like this:
use yourdatabasename -- (the database you are interested in examining)
go
select db_name(ius.database_id) as DatabaseName,
object_name(ius.object_id) as ObjectName,
sysind.name as IndexName
from sys.dm_db_index_usage_stats ius
inner join sys.indexes sysind on ius.index_id = sysind.index_id
For the moment it'll work fine, but you must be in the correct database for
the object_name function to return a valid name, hence the USE statement.
After SP2 has been released you'll be able to incorporate the database into
the object_name function to ensure you don't nee a use statement at the top.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Database I/O error

I am using SQL 2000 Dev edition. I create a DB on box
1. I run a simple program that loops through all records
in a table. It works fine. (VBA Code in MS Access
accessing the SQL table via ADO if it matters.) I then
detach the database and copy the file, plus log file, to
Box 2.
I attach the database on Box 2 and run the same code to
loop through all records in the table. It fails with an
I/O error 998 (Invalid access to memory location)
detected during read at offset 0x00000b8f1e0000 in
file 'My DB File'
It does not always stop at the same point. When I check,
it shows EOF to be true - even though a counter shows I
am less than 30% of the way through the file.
Is there some form of utility to check the validity of
the DB? I ran a ShrinkDatabase on box 1. Then copied
the file to box 2 again. Same results.
Known differences:
- Hardware.
- OS. (Can that really matter?)
- Box1 = Win2003 Server.
- Box2 = Win XP Pro SP1
Both boxes are SQL 2000 Developers edition SP3.
I'm pulling my hair out on this. Any help is greatly
appreciated.
Thank you.
Sounds like a hardware issue, I have seen similar problems just prior to a
hard disk crapping out. Have you run any disk checking utilities against
the problem machine? Checked the event viewer for operating system and/or
Disk errors/warnings?
http://www.aspfaq.com/
(Reverse address to reply.)
"DB" <anonymous@.discussions.microsoft.com> wrote in message
news:180801c4d6fc$9cb189c0$a501280a@.phx.gbl...
> I am using SQL 2000 Dev edition. I create a DB on box
> 1. I run a simple program that loops through all records
> in a table. It works fine. (VBA Code in MS Access
> accessing the SQL table via ADO if it matters.) I then
> detach the database and copy the file, plus log file, to
> Box 2.
> I attach the database on Box 2 and run the same code to
> loop through all records in the table. It fails with an
> I/O error 998 (Invalid access to memory location)
> detected during read at offset 0x00000b8f1e0000 in
> file 'My DB File'
> It does not always stop at the same point. When I check,
> it shows EOF to be true - even though a counter shows I
> am less than 30% of the way through the file.
> Is there some form of utility to check the validity of
> the DB? I ran a ShrinkDatabase on box 1. Then copied
> the file to box 2 again. Same results.
> Known differences:
> - Hardware.
> - OS. (Can that really matter?)
> - Box1 = Win2003 Server.
> - Box2 = Win XP Pro SP1
> Both boxes are SQL 2000 Developers edition SP3.
> I'm pulling my hair out on this. Any help is greatly
> appreciated.
> Thank you.
>
sql

Database I/O error

I am using SQL 2000 Dev edition. I create a DB on box
1. I run a simple program that loops through all records
in a table. It works fine. (VBA Code in MS Access
accessing the SQL table via ADO if it matters.) I then
detach the database and copy the file, plus log file, to
Box 2.
I attach the database on Box 2 and run the same code to
loop through all records in the table. It fails with an
I/O error 998 (Invalid access to memory location)
detected during read at offset 0x00000b8f1e0000 in
file 'My DB File'
It does not always stop at the same point. When I check,
it shows EOF to be true - even though a counter shows I
am less than 30% of the way through the file.
Is there some form of utility to check the validity of
the DB? I ran a ShrinkDatabase on box 1. Then copied
the file to box 2 again. Same results.
Known differences:
- Hardware.
- OS. (Can that really matter?)
- Box1 = Win2003 Server.
- Box2 = Win XP Pro SP1
Both boxes are SQL 2000 Developers edition SP3.
I'm pulling my hair out on this. Any help is greatly
appreciated.
Thank you.Sounds like a hardware issue, I have seen similar problems just prior to a
hard disk crapping out. Have you run any disk checking utilities against
the problem machine? Checked the event viewer for operating system and/or
Disk errors/warnings?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"DB" <anonymous@.discussions.microsoft.com> wrote in message
news:180801c4d6fc$9cb189c0$a501280a@.phx.gbl...
> I am using SQL 2000 Dev edition. I create a DB on box
> 1. I run a simple program that loops through all records
> in a table. It works fine. (VBA Code in MS Access
> accessing the SQL table via ADO if it matters.) I then
> detach the database and copy the file, plus log file, to
> Box 2.
> I attach the database on Box 2 and run the same code to
> loop through all records in the table. It fails with an
> I/O error 998 (Invalid access to memory location)
> detected during read at offset 0x00000b8f1e0000 in
> file 'My DB File'
> It does not always stop at the same point. When I check,
> it shows EOF to be true - even though a counter shows I
> am less than 30% of the way through the file.
> Is there some form of utility to check the validity of
> the DB? I ran a ShrinkDatabase on box 1. Then copied
> the file to box 2 again. Same results.
> Known differences:
> - Hardware.
> - OS. (Can that really matter?)
> - Box1 = Win2003 Server.
> - Box2 = Win XP Pro SP1
> Both boxes are SQL 2000 Developers edition SP3.
> I'm pulling my hair out on this. Any help is greatly
> appreciated.
> Thank you.
>

Tuesday, March 27, 2012

Database I/O error

I am using SQL 2000 Dev edition. I create a DB on box
1. I run a simple program that loops through all records
in a table. It works fine. (VBA Code in MS Access
accessing the SQL table via ADO if it matters.) I then
detach the database and copy the file, plus log file, to
Box 2.
I attach the database on Box 2 and run the same code to
loop through all records in the table. It fails with an
I/O error 998 (Invalid access to memory location)
detected during read at offset 0x00000b8f1e0000 in
file 'My DB File'
It does not always stop at the same point. When I check,
it shows EOF to be true - even though a counter shows I
am less than 30% of the way through the file.
Is there some form of utility to check the validity of
the DB? I ran a ShrinkDatabase on box 1. Then copied
the file to box 2 again. Same results.
Known differences:
- Hardware.
- OS. (Can that really matter?)
- Box1 = Win2003 Server.
- Box2 = Win XP Pro SP1
Both boxes are SQL 2000 Developers edition SP3.
I'm pulling my hair out on this. Any help is greatly
appreciated.
Thank you.Sounds like a hardware issue, I have seen similar problems just prior to a
hard disk crapping out. Have you run any disk checking utilities against
the problem machine? Checked the event viewer for operating system and/or
Disk errors/warnings?
http://www.aspfaq.com/
(Reverse address to reply.)
"DB" <anonymous@.discussions.microsoft.com> wrote in message
news:180801c4d6fc$9cb189c0$a501280a@.phx.gbl...
> I am using SQL 2000 Dev edition. I create a DB on box
> 1. I run a simple program that loops through all records
> in a table. It works fine. (VBA Code in MS Access
> accessing the SQL table via ADO if it matters.) I then
> detach the database and copy the file, plus log file, to
> Box 2.
> I attach the database on Box 2 and run the same code to
> loop through all records in the table. It fails with an
> I/O error 998 (Invalid access to memory location)
> detected during read at offset 0x00000b8f1e0000 in
> file 'My DB File'
> It does not always stop at the same point. When I check,
> it shows EOF to be true - even though a counter shows I
> am less than 30% of the way through the file.
> Is there some form of utility to check the validity of
> the DB? I ran a ShrinkDatabase on box 1. Then copied
> the file to box 2 again. Same results.
> Known differences:
> - Hardware.
> - OS. (Can that really matter?)
> - Box1 = Win2003 Server.
> - Box2 = Win XP Pro SP1
> Both boxes are SQL 2000 Developers edition SP3.
> I'm pulling my hair out on this. Any help is greatly
> appreciated.
> Thank you.
>

Database hung after failure of large update query

I tried to run a large update query last night that did not complete.
But now I cannot access that database. In fact, when I click on Databases
in Enterprise Manager, that hangs and shows an hourglass.
I suspect that it failed due to a disc space. When I look at the process
status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
on that database.
I don't really need to complete the update (partial complete would be fine).
I just need to free up the database so I can work on the database.
Any thoughts?
- Jesse
Jesse A wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on
> Databases in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the
> process status, I see a SPID that has a wait type of PAGEIOLatch_EX
> that is 'working' on that database.
> I don't really need to complete the update (partial complete would be
> fine). I just need to free up the database so I can work on the
> database.
> Any thoughts?
There is no such thing as a partial update unless you were using batches
to perform the updates in the first place. What likely happened is that
you ran out of space and SQL Server may be in the process of rolling
back the transaction (which can take just as long as the original update
took).
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||If u dont want any transaction for that particular SPID then u will kill the
particular process by KILL SPID
hope this will help
Herbert
"Jesse A" wrote:

> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on Databases
> in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the process
> status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
> on that database.
> I don't really need to complete the update (partial complete would be fine).
> I just need to free up the database so I can work on the database.
> Any thoughts?
> --
> - Jesse

Database hung after failure of large update query

I tried to run a large update query last night that did not complete.
But now I cannot access that database. In fact, when I click on Databases
in Enterprise Manager, that hangs and shows an hourglass.
I suspect that it failed due to a disc space. When I look at the process
status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
on that database.
I don't really need to complete the update (partial complete would be fine).
I just need to free up the database so I can work on the database.
Any thoughts?
--
- JesseJesse A wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on
> Databases in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the
> process status, I see a SPID that has a wait type of PAGEIOLatch_EX
> that is 'working' on that database.
> I don't really need to complete the update (partial complete would be
> fine). I just need to free up the database so I can work on the
> database.
> Any thoughts?
There is no such thing as a partial update unless you were using batches
to perform the updates in the first place. What likely happened is that
you ran out of space and SQL Server may be in the process of rolling
back the transaction (which can take just as long as the original update
took).
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If u dont want any transaction for that particular SPID then u will kill the
particular process by KILL SPID
hope this will help
--
Herbert
"Jesse A" wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on Databases
> in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the process
> status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
> on that database.
> I don't really need to complete the update (partial complete would be fine).
> I just need to free up the database so I can work on the database.
> Any thoughts?
> --
> - Jesse

Database hung after failure of large update query

I tried to run a large update query last night that did not complete.
But now I cannot access that database. In fact, when I click on Databases
in Enterprise Manager, that hangs and shows an hourglass.
I suspect that it failed due to a disc space. When I look at the process
status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working
'
on that database.
I don't really need to complete the update (partial complete would be fine).
I just need to free up the database so I can work on the database.
Any thoughts?
--
- JesseJesse A wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on
> Databases in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the
> process status, I see a SPID that has a wait type of PAGEIOLatch_EX
> that is 'working' on that database.
> I don't really need to complete the update (partial complete would be
> fine). I just need to free up the database so I can work on the
> database.
> Any thoughts?
There is no such thing as a partial update unless you were using batches
to perform the updates in the first place. What likely happened is that
you ran out of space and SQL Server may be in the process of rolling
back the transaction (which can take just as long as the original update
took).
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If u dont want any transaction for that particular SPID then u will kill the
particular process by KILL SPID
hope this will help
Herbert
"Jesse A" wrote:

> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on Database
s
> in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the process
> status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'worki
ng'
> on that database.
> I don't really need to complete the update (partial complete would be fine
).
> I just need to free up the database so I can work on the database.
> Any thoughts?
> --
> - Jessesql

Database Healthchecks

Hi,
Does anyone have any good suggestions for things to look at/run etc. in a
database healthcheck?
It's purely the database I'm interested in, not the server.
Many thanks.
Hi Chappers
There are a number of things you can do.
Look at the SQL Error logs and Windows Event logs and look for any
unexpected messages.
Run a regular 'DBCC CHECKDB' and check the output.
Look at the various ways you can use profiler and perfmon to get more
information on the health of your database. Here are links to two good
articles.
Perfmon Tips
http://www.sql-server-performance.co...nitor_tips.asp
Profiler Tips
http://www.sql-server-performance.co...filer_tips.asp
Make sure your tables are not getting too fragmented. If your database is
not that large, you can just set up a full maintenence plan (this will do the
dbcc's as well).
If it's too large (ie maint plan takes a couple of hours or more to run).
You can use dbcc showcontig (see BOL) to check table fragmentation and
schedule index rebuilds where applicable.
Hope this helps
John
"Chappers" wrote:

> Hi,
> Does anyone have any good suggestions for things to look at/run etc. in a
> database healthcheck?
> It's purely the database I'm interested in, not the server.
> Many thanks.
|||Thanks John.
I have my own list of stuff to do and deliberately left the question open to
see what other people came up with so I could see what I'd missed.
Many thanks for taking the time to reply.
Paul
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi Chappers
> There are a number of things you can do.
> Look at the SQL Error logs and Windows Event logs and look for any
> unexpected messages.
> Run a regular 'DBCC CHECKDB' and check the output.
> Look at the various ways you can use profiler and perfmon to get more
> information on the health of your database. Here are links to two good
> articles.
> Perfmon Tips
> http://www.sql-server-performance.co...nitor_tips.asp
> Profiler Tips
> http://www.sql-server-performance.co...filer_tips.asp
> Make sure your tables are not getting too fragmented. If your database is
> not that large, you can just set up a full maintenence plan (this will do the
> dbcc's as well).
> If it's too large (ie maint plan takes a couple of hours or more to run).
> You can use dbcc showcontig (see BOL) to check table fragmentation and
> schedule index rebuilds where applicable.
> Hope this helps
> John
> "Chappers" wrote:
|||Regarding index fragmentation - don't just rebuild indexes because they have
fragmentation - whether it will have any effect on performance depends on
the queries you're running. Also, rebuilding an index takes and additional
1.2x the size of the index and makes the index offline for the duration of
the operation - you should consider using DBCC INDEXDEFRAG instead. More
info on all of this can be found in our whitepaper below:
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chappers" <Chappers@.discussions.microsoft.com> wrote in message
news:29D074BE-1443-467A-B2F7-0A28691370DC@.microsoft.com...
> Thanks John.
> I have my own list of stuff to do and deliberately left the question open
to[vbcol=seagreen]
> see what other people came up with so I could see what I'd missed.
> Many thanks for taking the time to reply.
> Paul
> "John Bandettini" wrote:
is[vbcol=seagreen]
do the[vbcol=seagreen]
run).[vbcol=seagreen]
in a[vbcol=seagreen]

Database Healthchecks

Hi,
Does anyone have any good suggestions for things to look at/run etc. in a
database healthcheck?
It's purely the database I'm interested in, not the server.
Many thanks.Hi Chappers
There are a number of things you can do.
Look at the SQL Error logs and Windows Event logs and look for any
unexpected messages.
Run a regular 'DBCC CHECKDB' and check the output.
Look at the various ways you can use profiler and perfmon to get more
information on the health of your database. Here are links to two good
articles.
Perfmon Tips
http://www.sql-server-performance.com/performance_monitor_tips.asp
Profiler Tips
http://www.sql-server-performance.com/sql_server_profiler_tips.asp
Make sure your tables are not getting too fragmented. If your database is
not that large, you can just set up a full maintenence plan (this will do the
dbcc's as well).
If it's too large (ie maint plan takes a couple of hours or more to run).
You can use dbcc showcontig (see BOL) to check table fragmentation and
schedule index rebuilds where applicable.
Hope this helps
John
"Chappers" wrote:
> Hi,
> Does anyone have any good suggestions for things to look at/run etc. in a
> database healthcheck?
> It's purely the database I'm interested in, not the server.
> Many thanks.|||Thanks John.
I have my own list of stuff to do and deliberately left the question open to
see what other people came up with so I could see what I'd missed.
Many thanks for taking the time to reply.
Paul
"John Bandettini" wrote:
> Hi Chappers
> There are a number of things you can do.
> Look at the SQL Error logs and Windows Event logs and look for any
> unexpected messages.
> Run a regular 'DBCC CHECKDB' and check the output.
> Look at the various ways you can use profiler and perfmon to get more
> information on the health of your database. Here are links to two good
> articles.
> Perfmon Tips
> http://www.sql-server-performance.com/performance_monitor_tips.asp
> Profiler Tips
> http://www.sql-server-performance.com/sql_server_profiler_tips.asp
> Make sure your tables are not getting too fragmented. If your database is
> not that large, you can just set up a full maintenence plan (this will do the
> dbcc's as well).
> If it's too large (ie maint plan takes a couple of hours or more to run).
> You can use dbcc showcontig (see BOL) to check table fragmentation and
> schedule index rebuilds where applicable.
> Hope this helps
> John
> "Chappers" wrote:
> > Hi,
> >
> > Does anyone have any good suggestions for things to look at/run etc. in a
> > database healthcheck?
> >
> > It's purely the database I'm interested in, not the server.
> >
> > Many thanks.|||Regarding index fragmentation - don't just rebuild indexes because they have
fragmentation - whether it will have any effect on performance depends on
the queries you're running. Also, rebuilding an index takes and additional
1.2x the size of the index and makes the index offline for the duration of
the operation - you should consider using DBCC INDEXDEFRAG instead. More
info on all of this can be found in our whitepaper below:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chappers" <Chappers@.discussions.microsoft.com> wrote in message
news:29D074BE-1443-467A-B2F7-0A28691370DC@.microsoft.com...
> Thanks John.
> I have my own list of stuff to do and deliberately left the question open
to
> see what other people came up with so I could see what I'd missed.
> Many thanks for taking the time to reply.
> Paul
> "John Bandettini" wrote:
> > Hi Chappers
> >
> > There are a number of things you can do.
> >
> > Look at the SQL Error logs and Windows Event logs and look for any
> > unexpected messages.
> >
> > Run a regular 'DBCC CHECKDB' and check the output.
> >
> > Look at the various ways you can use profiler and perfmon to get more
> > information on the health of your database. Here are links to two good
> > articles.
> >
> > Perfmon Tips
> >
> > http://www.sql-server-performance.com/performance_monitor_tips.asp
> >
> > Profiler Tips
> >
> > http://www.sql-server-performance.com/sql_server_profiler_tips.asp
> >
> > Make sure your tables are not getting too fragmented. If your database
is
> > not that large, you can just set up a full maintenence plan (this will
do the
> > dbcc's as well).
> > If it's too large (ie maint plan takes a couple of hours or more to
run).
> > You can use dbcc showcontig (see BOL) to check table fragmentation and
> > schedule index rebuilds where applicable.
> >
> > Hope this helps
> >
> > John
> >
> > "Chappers" wrote:
> >
> > > Hi,
> > >
> > > Does anyone have any good suggestions for things to look at/run etc.
in a
> > > database healthcheck?
> > >
> > > It's purely the database I'm interested in, not the server.
> > >
> > > Many thanks.

Database Healthchecks

Hi,
Does anyone have any good suggestions for things to look at/run etc. in a
database healthcheck?
It's purely the database I'm interested in, not the server.
Many thanks.Hi Chappers
There are a number of things you can do.
Look at the SQL Error logs and Windows Event logs and look for any
unexpected messages.
Run a regular 'DBCC CHECKDB' and check the output.
Look at the various ways you can use profiler and perfmon to get more
information on the health of your database. Here are links to two good
articles.
Perfmon Tips
http://www.sql-server-performance.c...onitor_tips.asp
Profiler Tips
http://www.sql-server-performance.c...ofiler_tips.asp
Make sure your tables are not getting too fragmented. If your database is
not that large, you can just set up a full maintenence plan (this will do th
e
dbcc's as well).
If it's too large (ie maint plan takes a couple of hours or more to run).
You can use dbcc showcontig (see BOL) to check table fragmentation and
schedule index rebuilds where applicable.
Hope this helps
John
"Chappers" wrote:

> Hi,
> Does anyone have any good suggestions for things to look at/run etc. in a
> database healthcheck?
> It's purely the database I'm interested in, not the server.
> Many thanks.|||Thanks John.
I have my own list of stuff to do and deliberately left the question open to
see what other people came up with so I could see what I'd missed.
Many thanks for taking the time to reply.
Paul
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi Chappers
> There are a number of things you can do.
> Look at the SQL Error logs and Windows Event logs and look for any
> unexpected messages.
> Run a regular 'DBCC CHECKDB' and check the output.
> Look at the various ways you can use profiler and perfmon to get more
> information on the health of your database. Here are links to two good
> articles.
> Perfmon Tips
> http://www.sql-server-performance.c...onitor_tips.asp
> Profiler Tips
> http://www.sql-server-performance.c...ofiler_tips.asp
> Make sure your tables are not getting too fragmented. If your database is
> not that large, you can just set up a full maintenence plan (this will do
the
> dbcc's as well).
> If it's too large (ie maint plan takes a couple of hours or more to run).
> You can use dbcc showcontig (see BOL) to check table fragmentation and
> schedule index rebuilds where applicable.
> Hope this helps
> John
> "Chappers" wrote:
>|||Regarding index fragmentation - don't just rebuild indexes because they have
fragmentation - whether it will have any effect on performance depends on
the queries you're running. Also, rebuilding an index takes and additional
1.2x the size of the index and makes the index offline for the duration of
the operation - you should consider using DBCC INDEXDEFRAG instead. More
info on all of this can be found in our whitepaper below:
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chappers" <Chappers@.discussions.microsoft.com> wrote in message
news:29D074BE-1443-467A-B2F7-0A28691370DC@.microsoft.com...
> Thanks John.
> I have my own list of stuff to do and deliberately left the question open
to[vbcol=seagreen]
> see what other people came up with so I could see what I'd missed.
> Many thanks for taking the time to reply.
> Paul
> "John Bandettini" wrote:
>
is[vbcol=seagreen]
do the[vbcol=seagreen]
run).[vbcol=seagreen]
in a[vbcol=seagreen]

Sunday, March 25, 2012

Database files compatible with Win2K & Win2003

SQL Server 2000/SP3 runs on Win2K.
I've failover clustering server run on Win2003. Are the system database
files compatible on both Win2K & Win003 ? That I can switch the databases on
Win2k to Win2003.
JT
Hi
SQL Server 2000 data files and backups, on 32 or 64 bit, are compatible on
any platform. The base OS does not matter. OS does not play a role here.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny" wrote:

> SQL Server 2000/SP3 runs on Win2K.
> I've failover clustering server run on Win2003. Are the system database
> files compatible on both Win2K & Win003 ? That I can switch the databases on
> Win2k to Win2003.
> JT

Database files compatible with Win2K & Win2003

SQL Server 2000/SP3 runs on Win2K.
I've failover clustering server run on Win2003. Are the system database
files compatible on both Win2K & Win003 ? That I can switch the databases on
Win2k to Win2003.
JTHi
SQL Server 2000 data files and backups, on 32 or 64 bit, are compatible on
any platform. The base OS does not matter. OS does not play a role here.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny" wrote:
> SQL Server 2000/SP3 runs on Win2K.
> I've failover clustering server run on Win2003. Are the system database
> files compatible on both Win2K & Win003 ? That I can switch the databases on
> Win2k to Win2003.
> JT

Database files compatible with Win2K & Win2003

SQL Server 2000/SP3 runs on Win2K.
I've failover clustering server run on Win2003. Are the system database
files compatible on both Win2K & Win003 ? That I can switch the databases on
Win2k to Win2003.
JTHi
SQL Server 2000 data files and backups, on 32 or 64 bit, are compatible on
any platform. The base OS does not matter. OS does not play a role here.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny" wrote:

> SQL Server 2000/SP3 runs on Win2K.
> I've failover clustering server run on Win2003. Are the system database
> files compatible on both Win2K & Win003 ? That I can switch the databases
on
> Win2k to Win2003.
> JTsql

Thursday, March 22, 2012

Database field length problem

Hi everyone
I had an access database running as the source for a website but it
has become too large to run correctly so it has been ported to MS-SQL
the problem is that 4 of the fields were Memo fields in access and as
such are 5000+ characters long each this overflows the allowed size on
the SQL server (8192)

Is there a way round without splitting those 4 fields into seperate
tales?? as this would cause a truly major re-write of the website

Thanks for any help
Further details available if requiredIf you use VarChar can you not set the max field length to 8000 characters?

I can't believe SQL has such limits, surely there's a way to automatically
use two rows for one record, or does this require additional programming in
ASP?

Cheers, Ash

"Peter" <peter@.iib.ws> wrote in message
news:81307dbc.0406250528.ae1d3d@.posting.google.com ...
> Hi everyone
> I had an access database running as the source for a website but it
> has become too large to run correctly so it has been ported to MS-SQL
> the problem is that 4 of the fields were Memo fields in access and as
> such are 5000+ characters long each this overflows the allowed size on
> the SQL server (8192)
> Is there a way round without splitting those 4 fields into seperate
> tales?? as this would cause a truly major re-write of the website
> Thanks for any help
> Further details available if required|||Hi there
When i try to import a flat text file where i have used the transform
tool to delare field sizes of 6000 for the four fields i get the
following error if they are varchar

cannot create a row of size 8366 which is greater than the allowable
maximum of 8060

If i map them as ntext i dont get an error but the data is truncated

Any ideas
Peter

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Peter Winning (peter@.iib.ws) writes:
> When i try to import a flat text file where i have used the transform
> tool to delare field sizes of 6000 for the four fields i get the
> following error if they are varchar
> cannot create a row of size 8366 which is greater than the allowable
> maximum of 8060
> If i map them as ntext i dont get an error but the data is truncated

ntext is probably the way to go, since that is the only way to have
more than 8060 bytes of data on one row.

Why your ntext data is truncated I don't know, but then again I don't
know how import the data. A CREATE TABLE definition and a sample data
file could help. (You would have to pack the data file into a zip
file, since it surely would be wrecked by news transport, if you
posted it as text.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Hi
I am using the enterprise manager to upload the database and so far all
attempts no matter how the fields are transformed are still failing
I have tried mapping the fields as vchar, nvchar and ntext with the same
results in every case ie failure to complete or data truncation this has
also been attempted on the server itself
The upsizing wizard in access also failed to do the job

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Peter Winning (peter@.iib.ws) writes:
> I am using the enterprise manager to upload the database and so far all
> attempts no matter how the fields are transformed are still failing
> I have tried mapping the fields as vchar, nvchar and ntext with the same
> results in every case ie failure to complete or data truncation this has
> also been attempted on the server itself
> The upsizing wizard in access also failed to do the job

I have no idea what Enterprise Manager is up to when it imports data;
I didn't even know that it had a function for it, and even less have I
used it.

My general experience of EM, though, is that it tends to occlude some
syntax in order to be helpful, when things go over its head, it leaves
you alone in the dark.

I would try to import the file with BCP, but since I don't know how your
text file looks like, I cannot suggest the exact command line. I repeat
from my previous posting:

A CREATE TABLE definition and a sample data file could help. (You would
have to pack the data file into a zip file, since it surely would be
wrecked by news transport, if you posted it as text.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thank you
I have to confess that i am a complete novice with sql what is "BCP" and
where would i find some help in how to use it.
The database is a flat field one with about 30 fields 4 of which are
memo fields with very large amounts of data in each

Regards
Peter

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Peter Winning (peter@.iib.ws) writes:
> I have to confess that i am a complete novice with sql what is "BCP" and
> where would i find some help in how to use it.

BCP is a command line tool that permits you to load large amount of
data from files. The files can be text files or binary. BCP is a bit
restricted in that the file has to be fairly square. That is, it not able
to sort out headers, unless you can find a square hole to put them in.

You can read more about BCP in Books Online.

Another alternative is DTS (Data Transformation Service), which is a more
versatile load tool, which I have never used my self though.

> The database is a flat field one with about 30 fields 4 of which are
> memo fields with very large amounts of data in each

Well, it is up to you. If you don't want to post a CREATE TABLE statement
for your table and a sample data file, you don't have to. But then you will
have to find out how to load your file with BCP on your own, because I
don't really feel like guessing your table and data.

If you look in the SQL Server Program group, there is "Import and
Export Data". This takes you to the DTS wizard, which may be able to
guide all the way. But as I said, I have not used DTS. Then again,
there are some nice people in microsoft.public.sqlserver.dts who might
be able to help you if you go that way. But they, too, might want the
table definition and sample data.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Hi

I don't think the DTS Import wizard will truncate the data if you import it
from an Access database! It could be that you are selecting the data in
Query Analyser which has a configurable value (Tools/Options/Results/Maximum
characters per column).

If you have a table such as

CREATE TABLE MyAccessTable ( id int, Memo1 ntext, Memo2 ntext, Memo3 ntext,
Memo4 ntext )

The you can see the number of characters using:
SELECT id,
datalength(memo1)/2,datalength(memo2)/2,datalength(memo3)/2,datalength(memo4
)/2 FROM MyAccessTable

John

"Peter Winning" <peter@.iib.ws> wrote in message
news:40dc5ecd$0$16435$c397aba@.news.newsgroups.ws.. .
> Hi there
> When i try to import a flat text file where i have used the transform
> tool to delare field sizes of 6000 for the four fields i get the
> following error if they are varchar
> cannot create a row of size 8366 which is greater than the allowable
> maximum of 8060
> If i map them as ntext i dont get an error but the data is truncated
> Any ideas
> Peter
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||I've just looked at our WebMail application we're using, it uses a SQL
database to store the messages which generally are over 8000 characters - it
uses NTEXT as the datatype, with a length of '16', how on EARTH does that
relate to a VARCHAR field that has to be set to 8000??

"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9514A53A31CFFYazorman@.127.0.0.1...
> Peter Winning (peter@.iib.ws) writes:
> > When i try to import a flat text file where i have used the transform
> > tool to delare field sizes of 6000 for the four fields i get the
> > following error if they are varchar
> > cannot create a row of size 8366 which is greater than the allowable
> > maximum of 8060
> > If i map them as ntext i dont get an error but the data is truncated
> ntext is probably the way to go, since that is the only way to have
> more than 8060 bytes of data on one row.
> Why your ntext data is truncated I don't know, but then again I don't
> know how import the data. A CREATE TABLE definition and a sample data
> file could help. (You would have to pack the data file into a zip
> file, since it surely would be wrecked by news transport, if you
> posted it as text.)
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||J. Hall (remove_this_ash@.a-hall.com) writes:
> I've just looked at our WebMail application we're using, it uses a SQL
> database to store the messages which generally are over 8000 characters
> - it uses NTEXT as the datatype, with a length of '16', how on EARTH
> does that relate to a VARCHAR field that has to be set to 8000??

16 is the length of the pointer that is stored within the row. The data
itself is stored on separate pages. A varchar value on the other hand is
stored within the row, and since a row can not host more than 8060 bytes
of data, there is an upper limit.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Excellent thanks for clearing that up.

Many thanks,

"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9517834BC4F9AYazorman@.127.0.0.1...
> J. Hall (remove_this_ash@.a-hall.com) writes:
> > I've just looked at our WebMail application we're using, it uses a SQL
> > database to store the messages which generally are over 8000 characters
> > - it uses NTEXT as the datatype, with a length of '16', how on EARTH
> > does that relate to a VARCHAR field that has to be set to 8000??
> 16 is the length of the pointer that is stored within the row. The data
> itself is stored on separate pages. A varchar value on the other hand is
> stored within the row, and since a row can not host more than 8060 bytes
> of data, there is an upper limit.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp

Wednesday, March 21, 2012

Database Engine Tuning Advisor gives non existent errors in SQL 2005

Hello,

I am sure you have heard of Community server - if not you are just using it ;)

I decided to try to optimise the performance of my site, run a trace and then DETA.

And I am getting errors like these:


E000 exec dbo.cs_user_Get @.UserName=N'jded',@.UserID=0,@.IsOnline=0,@.LastAction=N'',@.SettingsID=1000 122 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_user_Get'.
exec dbo.cs_thread_IsTracked @.ThreadID=5969,@.UserID=28236,@.SettingsID=1000,@.IsTracked=@.p4 output
select @.p4 1 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_thread_IsTracked'.
E000 declare @.p4 bit
set @.p4=0
exec dbo.cs_thread_IsTracked @.ThreadID=414,@.UserID=1001,@.SettingsID=1000,@.IsTracked=@.p4 output
select @.p4 1 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_thread_IsTracked'.
E000 exec dbo.cs_Section_GetSectionIDByPostID @.SettingsID=1000,@.PostID=44641 1 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_Section_GetSectionIDByPostID'.


The "trouble" is that those sprocs do exist and that the site apparently is working fine. But not for DETA. As far as DETA is concerned... 54% of my processing power is used to serve syntax errors!

A couple of hints.
The database was an upgrade from 2000.:
- I changed the compatibility level to 2005 but no luck there. I tried with a brand new database, and the errors keep cropping up.
B. The errors were observed in a kit that comprises of a 32bit IIS and 64bit SQL2005 and thought that it had to do with the connectivity of those two.
- I run the traces in one (32bit) server that hosts both IIS and SQL and I am getting the same errors.

Any help will be greatly appreciated.

Thank you.

Which catelog are these stored proc resides? What is the catalog that you are using?|||

Hi!

The database name is CommunityServer - the sprocs reside in it.

It is referenced like this in the web.config:
<add key="SiteSqlServer" value="uid=userXXX;server=SUXXX;pwd=XXXXX;database=CommunityServer;Min Pool Size=5;Max Pool Size=5000;Connect Timeout=20;" />

Does this help you to help me?

Thank you,

Dimitris

|||

The issue has to do with the fact that we use ADO.NET to access the data whereas the tuning advisor uses SQL Native Client and thus it compares the actions to SQLNCLI's syntax.

The team of the tuning advisor should something about it.

|||

Can you please use the -d option (dta.exe) or "Database for Workload Analysis" option in UI to set the database context to the database that contains the stored procedures.

Thanks

Sanjay

|||What if the "Database for Workload Analysis" dropdown is way way way too small to see the entire database name? If I have 50 databases there and they all begin with the same first 20 characters, that's all I can see. How could I possible choose the correct database name in the dropdown?

Database Engine Tuning Advisor gives non existent errors in SQL 2005

Hello,

I am sure you have heard of Community server - if not you are just using it ;)

I decided to try to optimise the performance of my site, run a trace and then DETA.

And I am getting errors like these:


E000 exec dbo.cs_user_Get @.UserName=N'jded',@.UserID=0,@.IsOnline=0,@.LastAction=N'',@.SettingsID=1000 122 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_user_Get'.
exec dbo.cs_thread_IsTracked @.ThreadID=5969,@.UserID=28236,@.SettingsID=1000,@.IsTracked=@.p4 output
select @.p4 1 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_thread_IsTracked'.
E000 declare @.p4 bit
set @.p4=0
exec dbo.cs_thread_IsTracked @.ThreadID=414,@.UserID=1001,@.SettingsID=1000,@.IsTracked=@.p4 output
select @.p4 1 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_thread_IsTracked'.
E000 exec dbo.cs_Section_GetSectionIDByPostID @.SettingsID=1000,@.PostID=44641 1 [Microsoft][SQL Native Client][SQL Server]Could not find stored procedure 'dbo.cs_Section_GetSectionIDByPostID'.


The "trouble" is that those sprocs do exist and that the site apparently is working fine. But not for DETA. As far as DETA is concerned... 54% of my processing power is used to serve syntax errors!

A couple of hints.
The database was an upgrade from 2000.:
- I changed the compatibility level to 2005 but no luck there. I tried with a brand new database, and the errors keep cropping up.
B. The errors were observed in a kit that comprises of a 32bit IIS and 64bit SQL2005 and thought that it had to do with the connectivity of those two.
- I run the traces in one (32bit) server that hosts both IIS and SQL and I am getting the same errors.

Any help will be greatly appreciated.

Thank you.

Which catelog are these stored proc resides? What is the catalog that you are using?|||

Hi!

The database name is CommunityServer - the sprocs reside in it.

It is referenced like this in the web.config:
<add key="SiteSqlServer" value="uid=userXXX;server=SUXXX;pwd=XXXXX;database=CommunityServer;Min Pool Size=5;Max Pool Size=5000;Connect Timeout=20;" />

Does this help you to help me?

Thank you,

Dimitris

|||

The issue has to do with the fact that we use ADO.NET to access the data whereas the tuning advisor uses SQL Native Client and thus it compares the actions to SQLNCLI's syntax.

The team of the tuning advisor should something about it.

|||

Can you please use the -d option (dta.exe) or "Database for Workload Analysis" option in UI to set the database context to the database that contains the stored procedures.

Thanks

Sanjay

|||What if the "Database for Workload Analysis" dropdown is way way way too small to see the entire database name? If I have 50 databases there and they all begin with the same first 20 characters, that's all I can see. How could I possible choose the correct database name in the dropdown?

Sunday, March 11, 2012

Database Diff?

I was just looking at my database backups and i noticed there was about a
100MB difference in the backup files. We run optimization plans but those
are done on the weekend and this happened in the middle of the week.
Some people are a little curious as to why the database backup would shrink
so much. I was thinking of trying to do a DB diff between the two but wasnt
sure how to do this. Looked around a little and saw a few tools but i was
looking for a free solution.
Anyone know why this might have shrunk or a tool that i could use to do a
diff?
Thanks
Justin
You could restore a backup before the change, and a backup after the change,
and then use a trial copy of red-gate SQL Compare (or trial versions of
other tools), I guess. Tools like this pay for themselves in the long run,
unless this is the only time you will ever use it (which you can't possibly
know right now).
Aaron Bertrand
SQL Server MVP
"Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>I was just looking at my database backups and i noticed there was about a
>100MB difference in the backup files. We run optimization plans but those
>are done on the weekend and this happened in the middle of the week.
> Some people are a little curious as to why the database backup would
> shrink so much. I was thinking of trying to do a DB diff between the two
> but wasnt sure how to do this. Looked around a little and saw a few tools
> but i was looking for a free solution.
> Anyone know why this might have shrunk or a tool that i could use to do a
> diff?
>
> Thanks
> Justin
>
|||You can start by checking all the table sizes ;)
Maybe somebody/changed to diffirential backup ?
Cheers,
Harry
|||Yeah you are right, i dont know if i'll need it again but a trial would be a
great start. I'll look in to that product.
Thanks
Justin
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23YHa4cSzHHA.4476@.TK2MSFTNGP06.phx.gbl...
> You could restore a backup before the change, and a backup after the
> change, and then use a trial copy of red-gate SQL Compare (or trial
> versions of other tools), I guess. Tools like this pay for themselves in
> the long run, unless this is the only time you will ever use it (which you
> can't possibly know right now).
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
> news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>
|||Yeah i guess i didnt really think about that. its really not too hard to run
a script to give some basic statistics about tables. More just a resource
problem but i have some spare servers i can run this on.
Thanks!
Justin
"Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote in
message news:CABE43A2-BD14-4E93-89FA-D5D5C8E12393@.microsoft.com...
> You can start by checking all the table sizes ;)
> Maybe somebody/changed to diffirential backup ?
> Cheers,
> Harry
>

Database Diff?

I was just looking at my database backups and i noticed there was about a
100MB difference in the backup files. We run optimization plans but those
are done on the weekend and this happened in the middle of the week.
Some people are a little curious as to why the database backup would shrink
so much. I was thinking of trying to do a DB diff between the two but wasnt
sure how to do this. Looked around a little and saw a few tools but i was
looking for a free solution.
Anyone know why this might have shrunk or a tool that i could use to do a
diff?
Thanks
JustinYou could restore a backup before the change, and a backup after the change,
and then use a trial copy of red-gate SQL Compare (or trial versions of
other tools), I guess. Tools like this pay for themselves in the long run,
unless this is the only time you will ever use it (which you can't possibly
know right now).
Aaron Bertrand
SQL Server MVP
"Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>I was just looking at my database backups and i noticed there was about a
>100MB difference in the backup files. We run optimization plans but those
>are done on the weekend and this happened in the middle of the week.
> Some people are a little curious as to why the database backup would
> shrink so much. I was thinking of trying to do a DB diff between the two
> but wasnt sure how to do this. Looked around a little and saw a few tools
> but i was looking for a free solution.
> Anyone know why this might have shrunk or a tool that i could use to do a
> diff?
>
> Thanks
> Justin
>|||You can start by checking all the table sizes ;)
Maybe somebody/changed to diffirential backup ?
Cheers,
Harry|||Yeah you are right, i dont know if i'll need it again but a trial would be a
great start. I'll look in to that product.
Thanks
Justin
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:%23YHa4cSzHHA.4476@.TK2MSFTNGP06.phx.gbl...
> You could restore a backup before the change, and a backup after the
> change, and then use a trial copy of red-gate SQL Compare (or trial
> versions of other tools), I guess. Tools like this pay for themselves in
> the long run, unless this is the only time you will ever use it (which you
> can't possibly know right now).
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
> news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>|||Yeah i guess i didnt really think about that. its really not too hard to run
a script to give some basic statistics about tables. More just a resource
problem but i have some spare servers i can run this on.
Thanks!
Justin
"Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote in
message news:CABE43A2-BD14-4E93-89FA-D5D5C8E12393@.microsoft.com...
> You can start by checking all the table sizes ;)
> Maybe somebody/changed to diffirential backup ?
> Cheers,
> Harry
>