Thursday, March 8, 2012
Another example of incomplete support of some legal database names
cannot handle databases which have a period in their name (e.g.
"mydomain.com"). It doesn't show the individual field names.
Today I found a second problem: when scheduling a Job under SQL Server
Agent, in the New Step dialog you are prompted for a database name.
Databases with a period in their name are not listed. Tomorrow I'll
use ISQL to schedule the job in Windows Scheduler.
Hopefully MSFT will add these tests to the test scripts for the next
version and service pack (but don't hold your breath).
PS: I inherited this database name. It's too late (read: expensive)
now to fix it.
-Tom.Many of the tools do not support non-standard object names.
Even though SQL Server lets you create objects with invalid
names they aren't really legal names. You can find the rules
for object names in books online under the topic Using
Identifiers
-Sue
On Tue, 23 Mar 2004 19:39:31 -0700, Tom van Stiphout
<tom7744@.no.spam.cox.net> wrote:
>It has already been reported that the View tool in Enterprise Manager
>cannot handle databases which have a period in their name (e.g.
>"mydomain.com"). It doesn't show the individual field names.
>Today I found a second problem: when scheduling a Job under SQL Server
>Agent, in the New Step dialog you are prompted for a database name.
>Databases with a period in their name are not listed. Tomorrow I'll
>use ISQL to schedule the job in Windows Scheduler.
>Hopefully MSFT will add these tests to the test scripts for the next
>version and service pack (but don't hold your breath).
>PS: I inherited this database name. It's too late (read: expensive)
>now to fix it.
>-Tom.|||On Tue, 23 Mar 2004 19:39:31 -0700, Tom van Stiphout wrote:
>It has already been reported that the View tool in Enterprise Manager
>cannot handle databases which have a period in their name (e.g.
>"mydomain.com"). It doesn't show the individual field names.
>Today I found a second problem: when scheduling a Job under SQL Server
>Agent, in the New Step dialog you are prompted for a database name.
>Databases with a period in their name are not listed. Tomorrow I'll
>use ISQL to schedule the job in Windows Scheduler.
>Hopefully MSFT will add these tests to the test scripts for the next
>version and service pack (but don't hold your breath).
Hopefully not. I would prefer that MSFT removes the ability to call a
database "mydomain.com" or other pathological formats.
>PS: I inherited this database name. It's too late (read: expensive)
>now to fix it.
That's too bad.
I presume that you can still write scripts for all of the things that
you can't accomplish via the GUI? If so, then you have the tradeoff
costs of writing everything in scripts versus changing the name of the
database in the application (and all the associated testing).
--
"There is more to life than simply increasing its speed." - Mahatma Gandhi|||On Tue, 23 Mar 2004 21:32:35 -0700, Sue Hoegemeier
<Sue_H@.nomail.please> wrote:
You are correct. To my horror I found that:
sp_renamedb 'pubs', '123'
works, while BOL clearly has strict rules about the first character of
an identifier.
Would it kill MSFT to implement those rules, and not allow identifiers
that it later can't work with?
-Tom.
>Many of the tools do not support non-standard object names.
>Even though SQL Server lets you create objects with invalid
>names they aren't really legal names. You can find the rules
>for object names in books online under the topic Using
>Identifiers
>-Sue
>On Tue, 23 Mar 2004 19:39:31 -0700, Tom van Stiphout
><tom7744@.no.spam.cox.net> wrote:
>|||You could always send your request for this to
sqlwish@.microsoft.com
-Sue
On Wed, 24 Mar 2004 06:56:01 -0700, Tom van Stiphout
<tom7744@.no.spam.cox.net> wrote:
>On Tue, 23 Mar 2004 21:32:35 -0700, Sue Hoegemeier
><Sue_H@.nomail.please> wrote:
>You are correct. To my horror I found that:
>sp_renamedb 'pubs', '123'
>works, while BOL clearly has strict rules about the first character of
>an identifier.
>Would it kill MSFT to implement those rules, and not allow identifiers
>that it later can't work with?
>-Tom.
>
Saturday, February 25, 2012
Announcing a GUI tool for configuring dialog security and routing
Hi,
I am not
able to get “Service Broker” under my database? Can you tell me what is wrong
with my installation?
Regards,
If you are using SQL Server Management Studio Express, it does not have the functionality to view or create Service Broker objects. The paid version of the same lets you view Service Broker objects but not create them. Unfortunately, the only way to create, alter and use Service Broker objects is via T-SQL commands. Please look at the Service Broker section of Books Online, the SQL Server online documentation on MSDN.
Friday, February 24, 2012
ANN: Multi DBMS tool "Database Workbench" version 2.8.7 released
Upscene Productions is proud to announce the next
version of the popular database development tool:
Database Workbench 2.8.7 has been released today!
Download a trial at: http://www.upscene.com
What's new?: http://www.upscene.com/products/dbw/whatsnew.htm
Full list of features and fixes: http://www.upscene.com/news/20060614.htm
Database Workbench supports:
- Borland InterBase ( 4.x - 7.x )
- Firebird ( 1.x, 2.0 )
- MS SQL Server/MSDE ( v6.5, 7, 2000, 2005, MSDE 1 & 2, SQL Express )
- MySQL 4, 4.1, 5.0
- Oracle Database ( 8i, 9i, 10g )
- NexusDB ( 2.05 )
If you experience any problems with this new version, don't
hestitate and either go to the website and send a support email
or email directly to support@.upscene.com
New/improved
--
- NexusDB 2 support
- Microsoft SQL 2005, Service Pack 1 support
- MySQL 5 support
- Two-way Visual Query Builder
- Increased Oracle support
- New SQL Insight
- Create INSERT script from ODBC datasource
- TIFF support in BLOB Editor
Enhancements and bugfixes related to Import/Export, DataPump,
Code Editors, SQL Insight, NexusDB module performance and much
more.
Thank you for your support,
Martijn Tonies
Database Workbench - the database developer tool for professionals
Upscene Productions
http://www.upscene.comModerator please delete this spam.
"Martijn Tonies" wrote:
> Ladies, gentlemen,
> Upscene Productions is proud to announce the next
> version of the popular database development tool:
> Database Workbench 2.8.7 has been released today!
>
> Download a trial at: http://www.upscene.com
> What's new?: http://www.upscene.com/products/dbw/whatsnew.htm
> Full list of features and fixes: http://www.upscene.com/news/20060614.htm
>
> Database Workbench supports:
> - Borland InterBase ( 4.x - 7.x )
> - Firebird ( 1.x, 2.0 )
> - MS SQL Server/MSDE ( v6.5, 7, 2000, 2005, MSDE 1 & 2, SQL Express )
> - MySQL 4, 4.1, 5.0
> - Oracle Database ( 8i, 9i, 10g )
> - NexusDB ( 2.05 )
> If you experience any problems with this new version, don't
> hestitate and either go to the website and send a support email
> or email directly to support@.upscene.com
> New/improved
> --
> - NexusDB 2 support
> - Microsoft SQL 2005, Service Pack 1 support
> - MySQL 5 support
> - Two-way Visual Query Builder
> - Increased Oracle support
> - New SQL Insight
> - Create INSERT script from ODBC datasource
> - TIFF support in BLOB Editor
>
> Enhancements and bugfixes related to Import/Export, DataPump,
> Code Editors, SQL Insight, NexusDB module performance and much
> more.
>
> Thank you for your support,
> Martijn Tonies
> Database Workbench - the database developer tool for professionals
> Upscene Productions
> http://www.upscene.com
>
>
ANN: Database Workbench 2.8.5 released
Upscene Productions is proud to announce the next
version of the popular database development tool:
Database Workbench 2.8.5 has been released today!
Download a trial at: http://www.upscene.com
What's new?: http://www.upscene.com/products/dbw/whatsnew.htm
Full list of features and fixes: http://www.upscene.com/news/20060327.htm
Database Workbench supports:
- Borland InterBase ( 4.x - 7.x )
- Firebird ( 1.x, 2.0 )
- MS SQL Server/MSDE ( v6.5, 7, 2000, 2005, MSDE 1 & 2, SQL Express )
- MySQL 4, 4.1, 5.0
- Oracle Database ( 8i, 9i, 10g )
- NexusDB ( 2.05 )
If you experience any problems with this new version, don't
hestitate and either go to the website and send a support email
or email directly to support@.upscene.com
New
--
- NexusDB 2 support
- Microsoft SQL 2005 support
- MySQL 5 support
- Two-way Visual Query Builder
- Increased Oracle support
- New SQL Insight
- Create INSERT script from ODBC datasource
- TIFF support in BLOB Editor
Enhancements
--
- Code/SQL Editor enhancements
- More complte Schema Compare/Migration
- Automatic image-type recognition in BLOB Editor
- many user interface improvements
- MySQL "explain" support in SQL Editor
Thank you for your support,
Martijn Tonies
Database Workbench - the database developer tool for professionals
Upscene Productions
http://www.upscene.comModerator please delete this spam.
"Martijn Tonies" wrote:
> Ladies, gentlemen,
> Upscene Productions is proud to announce the next
> version of the popular database development tool:
> Database Workbench 2.8.5 has been released today!
>
> Download a trial at: http://www.upscene.com
> What's new?: http://www.upscene.com/products/dbw/whatsnew.htm
> Full list of features and fixes: http://www.upscene.com/news/20060327.htm
>
> Database Workbench supports:
> - Borland InterBase ( 4.x - 7.x )
> - Firebird ( 1.x, 2.0 )
> - MS SQL Server/MSDE ( v6.5, 7, 2000, 2005, MSDE 1 & 2, SQL Express )
> - MySQL 4, 4.1, 5.0
> - Oracle Database ( 8i, 9i, 10g )
> - NexusDB ( 2.05 )
> If you experience any problems with this new version, don't
> hestitate and either go to the website and send a support email
> or email directly to support@.upscene.com
> New
> --
> - NexusDB 2 support
> - Microsoft SQL 2005 support
> - MySQL 5 support
> - Two-way Visual Query Builder
> - Increased Oracle support
> - New SQL Insight
> - Create INSERT script from ODBC datasource
> - TIFF support in BLOB Editor
>
> Enhancements
> --
> - Code/SQL Editor enhancements
> - More complte Schema Compare/Migration
> - Automatic image-type recognition in BLOB Editor
> - many user interface improvements
> - MySQL "explain" support in SQL Editor
>
> Thank you for your support,
> Martijn Tonies
> Database Workbench - the database developer tool for professionals
> Upscene Productions
> http://www.upscene.com
>
>|||Users,
> Moderator please delete this spam.
Many third party developers post here and those postings, or ours, never
received
any negative comments.
Has the stance on this changed?
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com
> "Martijn Tonies" wrote:
> > Ladies, gentlemen,
> >
> > Upscene Productions is proud to announce the next
> > version of the popular database development tool:
> >
> > Database Workbench 2.8.5 has been released today!
> >
> >
> >
> > Download a trial at: http://www.upscene.com
> > What's new?: http://www.upscene.com/products/dbw/whatsnew.htm
> > Full list of features and fixes:
http://www.upscene.com/news/20060327.htm
> >
> >
> >
> > Database Workbench supports:
> > - Borland InterBase ( 4.x - 7.x )
> > - Firebird ( 1.x, 2.0 )
> > - MS SQL Server/MSDE ( v6.5, 7, 2000, 2005, MSDE 1 & 2, SQL Express )
> > - MySQL 4, 4.1, 5.0
> > - Oracle Database ( 8i, 9i, 10g )
> > - NexusDB ( 2.05 )
> >
> > If you experience any problems with this new version, don't
> > hestitate and either go to the website and send a support email
> > or email directly to support@.upscene.com
> >
> > New
> > --
> > - NexusDB 2 support
> > - Microsoft SQL 2005 support
> > - MySQL 5 support
> > - Two-way Visual Query Builder
> > - Increased Oracle support
> > - New SQL Insight
> > - Create INSERT script from ODBC datasource
> > - TIFF support in BLOB Editor
> >
> >
> > Enhancements
> > --
> > - Code/SQL Editor enhancements
> > - More complte Schema Compare/Migration
> > - Automatic image-type recognition in BLOB Editor
> > - many user interface improvements
> > - MySQL "explain" support in SQL Editor
> >
> >
> > Thank you for your support,
> >
> > Martijn Tonies
> > Database Workbench - the database developer tool for professionals
> > Upscene Productions
> > http://www.upscene.com
> >
> >
> >|||I think not. Remember Forbes:
'We spare our readers unimportant advertisers and we spare our
advertisers unimportant "readers" ' :)
Check out RAC @.:
www.rac4sql.net
"Martijn Tonies" <m.tonies@.upscene.removethis.com> wrote in message
news:%23wIwCMRkGHA.4512@.TK2MSFTNGP04.phx.gbl...
> Users,
>> Moderator please delete this spam.
> Many third party developers post here and those postings, or ours, never
> received
> any negative comments.
> Has the stance on this changed?
Sunday, February 19, 2012
Analyzing sysjobhistory
I am specifically prohibited from using any 3rd-party tools (too expensive per mgmt).
I would be grateful for any input/insight.
Regards,
hmscottIts advised not to query system tables directly when system supplied stored procedures are availble, have you looked into SP_HELP_JOBHISTRY and other corresponding SPs. Refer to books online for more information.|||Satya,
Yes, I had looked at that SP. The basic issue I had with it was that the Date and time stamps are configured as INTs and are not combined into an integrated date/time field.
Your reminder is a good one, however; I am nearly finished with working on a centralized repository for job execution history. I will look again and try to avoid querying the system tables directly.
Regards,
hmscott
Analyzing Stored Procedures - does a tool exist?
I did a search for tools and came across the SPUD tool at http://www.hybridx.com but the only problem with that tool is that i need to modify each stored procedure before it will start logging information on the stored proc.
Does anyone know of or use any tools that generate this sort of information in a non-invasive way? Any help would be greatly appreciated. Thanks.
There really isn't any tool that will do this sort of thing for you other
than running a constant profiler trace with sp_completed and see which ones
are called. Of coarse just because it isn't called for a day or so does not
mean it isn't used but it will give you a start and then you can narrow down
the list.
Andrew J. Kelly SQL MVP
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:6EBFC2B2-6FCC-4826-BCBA-9FFA351F2EF7@.microsoft.com...
> My boss wants me to go through the many stored procedures that are on our
many SQL servers and generate a list of how often they are used, and then
use that info to retire any stored procs that are not being used.
> I did a search for tools and came across the SPUD tool at
http://www.hybridx.com but the only problem with that tool is that i need to
modify each stored procedure before it will start logging information on the
stored proc.
> Does anyone know of or use any tools that generate this sort of
information in a non-invasive way? Any help would be greatly appreciated.
Thanks.
|||<<
> http://www.hybridx.com but the only problem with that tool is that i need
to
> modify each stored procedure before it will start logging information on
the[vbcol=seagreen]
> stored proc.
That sounds like a horrible idea to me. That creates too many opportunites
for thier code to cause problems with your code.
Andrew's suggestion of running Profiler is probably the best thing to do.
Brian
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OGTvDp$cEHA.1764@.TK2MSFTNGP10.phx.gbl...
> There really isn't any tool that will do this sort of thing for you other
> than running a constant profiler trace with sp_completed and see which
ones
> are called. Of coarse just because it isn't called for a day or so does
not
> mean it isn't used but it will give you a start and then you can narrow
down[vbcol=seagreen]
> the list.
> --
> Andrew J. Kelly SQL MVP
>
> "Sam" <Sam@.discussions.microsoft.com> wrote in message
> news:6EBFC2B2-6FCC-4826-BCBA-9FFA351F2EF7@.microsoft.com...
our
> many SQL servers and generate a list of how often they are used, and then
> use that info to retire any stored procs that are not being used.
> http://www.hybridx.com but the only problem with that tool is that i need
to
> modify each stored procedure before it will start logging information on
the
> stored proc.
> information in a non-invasive way? Any help would be greatly appreciated.
> Thanks.
>
Analyzing db Growth per day
Any help would be grately aprreciated.sp_helpdb 'MyDatabaseName'|||The easiest way to do it is to check in Enterprise manager daily to see what the current size is, then keep the daily records in a spreadsheet, or database. If you are looking for a pre-packaged too, I think Quest Software has something for that. I think Microsoft is also getting into the game, as well, with a product I can not remember the name of. Some SQL Server add on.|||Or you could write a job that copies sysobjects and sysindexes into a table that you aggregate on a regualr basis. Swipe code from sp_spaceused to understand how to use that information.
Analyze LDF files MS SQL Server 2000
I mean, a tool that converts a LDF file in a set of SQL transactions?
(similar to dbtran in sybase)
thanks!"Esteban" <ecastillo@.gmail.com> wrote in message
news:8f83567b.0406180752.1b24d5ff@.posting.google.c om...
> Anybody nows a tool to analyze LDF files in MS SQL Server 2000?
> I mean, a tool that converts a LDF file in a set of SQL transactions?
> (similar to dbtran in sybase)
> thanks!
There is nothing in MSSQL itself (except for some undocumented commands),
but there are third-party tools available, such as this one:
http://www.lumigent.com/
If you are trying to achieve something specific, you might want to post more
details of your goal, and someone may be able to suggest something.
Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<40d3fef1_2@.news.bluewin.ch>...
> "Esteban" <ecastillo@.gmail.com> wrote in message
> news:8f83567b.0406180752.1b24d5ff@.posting.google.c om...
> > Anybody nows a tool to analyze LDF files in MS SQL Server 2000?
> > I mean, a tool that converts a LDF file in a set of SQL transactions?
> > (similar to dbtran in sybase)
> > thanks!
> There is nothing in MSSQL itself (except for some undocumented commands),
> but there are third-party tools available, such as this one:
> http://www.lumigent.com/
> If you are trying to achieve something specific, you might want to post more
> details of your goal, and someone may be able to suggest something.
> Simon
Thanks Simon, I was trying this product, but I can't find an option
that shows me a list of SQL transactions made in the database ...
maybe I don't know how to use it.
For example, I want to know if a certain register was deleted from the
database.
thanks.|||Esteban (ecastillo@.gmail.com) writes:
> Thanks Simon, I was trying this product, but I can't find an option
> that shows me a list of SQL transactions made in the database ...
> maybe I don't know how to use it.
> For example, I want to know if a certain register was deleted from the
> database.
In the version I have, there is a "View DDL commands" under Browse, and it
seems to have the information of the kind you are looking for. There is
also a filter function.
Note that for Log Explorer to be really useful, you need to have the
database in FULL or BULK_LOGGED recovery mode.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp