I want to generate the DB document for all DB objects. please provide the free open source software to create the DB document.
I have used the SQLDBdoc but it's provide the only Tables details.
I am using SQl server 2012 express editions.
SQL Server documentation tools are quite complex to be free and open source and often they lack features. Instead, I suggest trying out some of the commercial tools with free versions, that are available on the market.
For example, I’m using ApexSQL Doc as a documentation tool. The program generates full featured SQL Server database and BI documentations in 5 output formats (including chm) in a few clicks, and lets you pick the database objects to document. It also offers different output style templates for the documentation.
It comes with a 14 days trial period and after that it remains free as a Community edition and lets you document from SQL Server Express and Azure SQL Database in chm format.
Related
We have two SQL Servers: 2008 and 2008R2 which are used in accordance with ArcSDE. SQL Server 2008 database became dissociated by the hands of some people: datatype fields have changed, some column names have changed, some triggers dissapeared. We don't much care about the data itself, b/c SQL Server 2008 is for development and testing and we can always get it back from archives.
Is there a way to analyze the differences (automatically) instead of going manually field by field with our eyes and fixing it on the fly? Does SQL Server Management Studio support this functionality?
Try using the ArcGIS Toolbox tool - Feature Compare.
Use this with the SCHEMA_ONLY option to compare feature classes.
If ArcGIS Desktop is not available but ArcGIS Server or ArcGIS Engine is, the Python option is available. The Python option can also be used to iterate over feature classes or tables.
If none of the ArcGIS products are available, there are a bunch of scripting and GUI options out there.
I've got experience with MySQL, DB2, and Oracle, but aside from writing a few queries, I've never used SQL Server.
My question is a three parter:
1) For a developer, what are some good "free" client tools to look at, and why (by "free" I mean open source, freeware, or the tools that come with SQL Server itself)?
2) I plan to run Developer or Express Edition on my workstation for development, and either Standard or Enterprise Edition in the testing and production environments. What methods exist if any for transferring data between different servers and the different editions?
3) Are there any common pitfalls that someone like me (who is used to the other database systems that I mentioned) might encountered during development?
TIA
SQL Server Express with tools.
All editions have the same SQL language features and code is 100% portable between them. There are 3rd party tools to synch changes, but moving entire DBs is easy using inbuilt tools.
Nah. The problem with databases is SQL and set theory, not the choice of RDBMS. If you understand databases/SQL you'll be OK.
SQL Server Management Studio which comes with SQL Server (any editions), or you can download it separately. SQL Server Profiler which doesn't come with Express.
Management studio has tools for backup/restore database. You can also consider detach/attach method to synchronize db .
It's hard to say. But if you had Mysql experience you will be pleasantly surprised by SQL Server.
UPDATE
There are so many things that each DB vendor implements differently that it's really hard to focus on some of them. One thing I was not used before is that SQL Server doesn't let unique columns to have more than 1 NULL value(there is a workaround though)
We currently use SQL Server 2005 Enterprise for our fairly large application, that has its roots in pre SQL Server 7.0. The tables are normalized and designed mainly for the application. The developers for the most part have the legacy SQL Server mindset. Only using the part of TSQL that existed back in 7.0, not using any of the new features of tsql or that are bundled with 2005.
We're currently trying to build on demand reports using some crappy third party software, and will eventually try to build a data warehouse using more of the same crappy third party software (name removed to protect the guilty, don't ask I will not tell). The rationale for this was that we didn't want to spend more money to buy this additional software from Microsoft (this was not my decision, I had no input, but is my problem now). But from what I can tell is that Enterprise includes all of these tools, or am I missing something?
What comes bundled with SQL Server 2005 Enterprise as far as reporting and data warehousing? Will we need to purchase anything else? is there actually anything else that can be purchased from Microsoft in this regard?
Well, first - I would go with 2008 R2 for that regard, much better for reporting.
DAta warehousing in 2005 is just that. 2008 did introduce optimizatoins for star schemata in the query optimizer.
2005 I think has report services that you can use - though they got a LOT better with 2008 and 2008 R2 (graphs etc.)
Besides that think getting rid of SQL for analysis - the data warehouse should get loaded into cubes in SQL Server Analysis Services and run the reports against those.
All that (reporting services, analysis services) is part of the enterprise edition you use. There is hardly any use for something else unless you have unusual needs.
Enterprise edition contains Reporting Services that you can install that. It is a powerful service for reporting.
If you find you're unhappy with Reporting Services (seems to not work well for about 35% of the people who try it), please take a look at Windward Reports. With that said, I hope it does work well for you as that is your least expensive and quickest route forward.
I am a relative newbie when it comes to SQL Azure!! I was wondering if there was a definitive list somewhere regarding what is and is not supported by SQL Azure in regards to SQL Server 2008? I have had a look through google but I've noticed some of the blog posts are missing things which I have found through my own testing:
For example, quite a lot is summarised in this blog entry http://www.keepitsimpleandfast.com/2009/12/main-differences-between-sql-azure-and.html
Common Language Runtime (CLR)
Database file placement
Database mirroring
Distributed queries
Distributed transactions
Filegroup management
Global temporary tables
Spatial data and indexes
SQL Server configuration options
SQL Server Service Broker
System tables
Trace Flags
which is a repeat of the MSDN page http://msdn.microsoft.com/en-us/library/ff394115.aspx
I've noticed from my own testing that the following seem to have issues when migrating from SQL Server 2008 to the Azure:
XML Types (the msdn does mention large custom types - I guess it may include this?? even if the data schema is really small?)
Multi-part views
I've been using SQL Azure Migration Wizard v3.1.8 to migrate local databases into the cloud.
I was wondering if anyone could point to a list or give me any information till when these features are likely to be included in SQL Azure.
If you can get a hold of the February issue of SQL Server Magazine, there are two articles (I believe) that outline what Azure supports in relation to SQL Server 2008.
I was at an Azure training yesterday where it was confirmed that XML schemas are not supported. You may also find the e-clinic here https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=168190&tab=overview useful.
This document is a little more detailed than the links you listed. It's dated September 2009 but I believe is still mostly accurate.
http://go.microsoft.com/?linkid=9703594
One key paragraph from this document is:
Analysis Services, Replication, Reporting Services, and Service Broker are not currently provided as services on the SQL Azure.
I am using SQL Server 2008 express edition but I want to make my databases still in 2005. How can I set it up to only show features that a 2005 database can use?
Like for instance I don't remember there being a "date" type. I only remember "dateTime".
I don't want to be using features that 2005 can't support and I later on upload my db to the my hosting site that uses 2005 still and find out I am using things not supported by it.
You won't be able to upload the database, just a script of it. Even when in 90 compatibility mode, the physical structure of the database will be the 2008 one and the hosting site won't be able to load it.
Note that the compatibility level does not necessarily mean that the new features of SQL 2008 are not available, but instead it simply means that (some) features that existed in 2005 will work the same way in 2008. The complete list of compatibility mode changes is on MSDN. In particular there is nothing to prevent the usage of a datetime2, date, time or any new time in a database set at compatibility level 90. In fact such would be impossible simply because the the compatibility level can be changed after a table is created.
You are going to either develop against a SQL 2k5 instance, or read the product manual and learn what features are available in what version.